Bridge ships an MCP server. Claude, Cursor, or your own agent can search, log, remind, and even trade contacts — with safety rails built in.
Six tools today, more on the way. Each one is a single call your agent can make against your Bridge — with the audit trail to prove it.
Your agent hands off a warm intro to someone else's agent. Their agent decides whether to accept. The two of you only see it after both sides say yes.
bridge_contacts_transferNatural-language queries across every person, note, and meeting Bridge has on file. Returns the few that matter, not 400 rows of CSV.
bridge_contacts_searchDrop a voice memo or a Slack snippet into the chat and the agent writes the activity entry, attaches it to the right contact, and tags the deal.
bridge_activity_logTell the agent to nudge you about the founder you met at dinner in three weeks. It schedules, you forget, Bridge remembers.
bridge_reminders_createNew email, new fund, new title — the agent patches the record in place. Old values stay in the activity log so you can see what changed and when.
bridge_contacts_updateStage changes are destructive, so the agent always asks before it moves money. You confirm in chat, Bridge records who and when.
bridge_deals_move_stageBridge speaks MCP and HTTP directly. If your agent can read JSON, it can work with Bridge.
Open your Bridge settings and create an MCP token. Pick exactly which capabilities the agent gets — read-only, write, or specific actions like reminders.
Drop the URL into Claude Desktop, Cursor, or any MCP host. Bridge sits at api.bridge.app/api/v1/mcp. No SDK to install, no boilerplate to maintain.
The agent discovers what Bridge can do via JSON-RPC, then starts working — searching, logging, drafting, reminding. You stay in the loop, never in the way.
Four guarantees that turn "AI on top of my CRM" from a scary idea into an honest workflow.
Tokens scoped to non-PII access get emails, phone numbers, and notes stripped before the agent ever sees them. The agent works with handles, not addresses.
Anything the agent writes returns an undo token. One call to bridge_undo and the change disappears — no support ticket, no migration script.
Stage changes, deletes, and transfers come wrapped in a confirm envelope. The agent must explicitly say yes; you can cancel from chat with bridge_cancel.
Each token carries an allowlist. Wildcards stay scoped to what you picked — a read token can never quietly grow into a write token while you sleep.
We'll tell you what's real today and what isn't. No vaporware on the roadmap page.
Free to start. Bring your own agent. Bridge handles the memory, the audit trail, and the safety rails.