# Intros Public API > Programmatic access to Bridge introductions, contacts, and CC inbox threads on intros.brdg.app for scripts and agents. Auth: send `Authorization: Bearer `. Generate a key at [brdg.app](https://brdg.app) settings. The API acts as the key owner — permissions match the web UI exactly. ## MCP server AI apps (Claude, ChatGPT, Cursor, Claude Code, Grok) can connect without an API key: add the remote MCP server `https://intros.brdg.app/mcp` and approve in the browser (OAuth 2.1 with PKCE). Scopes: `intros:read` (default) and optional `intros:write`. Tools cover the to-do queue, intro search, contacts, read-only CC inbox threads and the intro lifecycle; changes need the user to allow them at approval. `log_historical_intro` records intros that happened outside Bridge, so agents can fill gaps from email, calendars or chats. Tools that send email take `dry_run: true` to preview the exact email first. Call `get_intros_guide` for roles, statuses, flows and count buckets. Manage connections in Inbox → Settings → AI apps. ### Connecting (if your user asked you to connect) If you can add an MCP server yourself, add the remote server `https://intros.brdg.app/mcp` (Streamable HTTP) and send the user the sign-in link it returns. If you can't, tell the user the steps for their app: - Claude (claude.ai or desktop; it then works on mobile): Settings → Connectors → Add custom connector, paste the URL, then Connect and sign in. On Team and Enterprise an owner adds it first. Start a new chat afterwards. - ChatGPT: Settings → Apps → Advanced → turn on Developer mode, then Create, paste the URL and sign in. Workspace plans may need an admin to allow it. - Grok Bot: ask it in chat to add the MCP server at the URL; it shows a card to sign in. - Claude Code: `claude mcp add --transport http intros https://intros.brdg.app/mcp` - Any other app that supports remote MCP: add a custom connector or remote MCP server with the URL and sign in when asked. Alternatively send `Authorization: Bearer ` on MCP requests (full read + write tool access, no OAuth). ## Reference - [Full API reference (markdown)](https://intros.brdg.app/llms-full.txt): every endpoint with request/response schemas and examples. - [OpenAPI 3.1 spec (YAML)](https://intros.brdg.app/api/v1/openapi.yaml) - [Interactive developer docs](https://intros.brdg.app/developers/api) ## Endpoints (summary) - `GET /v1/me`: verify a Bridge API key. - Intros: list (with filters) / get / counts / create / forward / forward with template / publish / accept / decline / cancel / request changes. - Contacts: list / get / create / update. ## Deep links Open Make intro in the user's browser, prefilled: `https://intros.brdg.app/inbox?makeIntro=1&n1=&n1_name=&flow=opt_in`. Optional `n1_title`, `n1_company`, `n1_linkedin` (and `n2_*`) fill gaps on the contact without overwriting. A name without an email searches the user's contacts. Details in the full reference under "Deep links". ## Concepts - Roles: requester (n1, `from_*`), target (n2, `to_*`), connector (broker). - Lifecycle: initialized → requester opts in → confirmed → connector forwards → published → target accepts (accepted) or declines (rejected). - Creatable flows: `opt_in` (double opt-in), `single_opt_in`, `fast` (no opt-in), plus CC intros. Full tables in the reference. - `since` filters by last update. Pages start at 0. Send endpoints take `dry_run: true`. - Inbox threads: list / get (read-only). ## Base URL `https://intros.brdg.app/api/v1`