This connects your assistant to Bridge documentation. It does not connect it to your workspace or give it permission to create Contacts or send messages. Your integration uses the separate REST API credentials, or the public Custom Connections setup. The documentation server also exposes an optional feedback tool that sends documentation comments to Bridge.
Choose your coding assistant
Codex
CLI and local IDE configuration.
Claude Code
One command, then check the connection.
Cursor
Add the server to your project’s MCP file.
GitHub Copilot
Guided setup in VS Code or portable project configuration.
Codex
Before you start: have Codex CLI or the Codex IDE extension installed. For the CLI, add the server in your terminal:bridgeDocs with the Bridge documentation URL. Listing it confirms configuration; use the connection check below to confirm that it can actually read documentation.
If you prefer editing configuration, add this entry to ~/.codex/config.toml. Keep your other settings and server entries:
/mcp shows active servers. Local Codex clients can share configuration on the same host; remote environments can have separate configuration and policy.
Example prompt:
Use bridgeDocs to read the Bridge REST contract and the first-conversation guide. Prepare a Node.js integration that creates a Contact, starts a Conversation and creates a Message. List the required identifiers and configuration first. Keep every API field and type unchanged, cite your sources, and do not make live API requests.Official Codex MCP guidance.
Claude Code
Before you start: have Claude Code installed. Add the server to your personal configuration so it is available across projects:--scope project rather than --scope user. Review the resulting project configuration before committing it.
Start Claude Code and use /mcp to inspect bridgeDocs. Then run the connection check below. The Bridge documentation endpoint does not need a Bridge API Key or an OAuth login.
Example prompt:
Use bridgeDocs to read the current Bridge webhook verification and receiver guides. Implement a Python receiver with the documented HMAC representation and durable acceptance before acknowledgement. Add offline tests using the published signature vector. Explain the timestamp limitation and duplicate handling, and cite the pages you used.Official Claude Code MCP guidance.
Cursor
Before you start: open your integration project in Cursor. Create or update.cursor/mcp.json in that project. Merge the entry with any existing servers:
~/.cursor/mcp.json instead. In Cursor’s Customize sidebar, check that the server is enabled. Open an Agent conversation and run the connection check below; relevant MCP tools appear under Available Tools. Review tool requests when Cursor asks.
Example prompt:
Use bridgeDocs to find the complete PDF attachment workflow. Implement a server-side upload that hashes the exact file bytes as Base64 SHA-256, requests a presigned upload, sends the required PUT and creates a Message with the returned mediaId. Preserve the documented fields and explain each stage’s failure handling. Do not send a Bridge API Key to the upload URL.Official Cursor MCP guidance.
GitHub Copilot
Before you start: enable GitHub Copilot in VS Code and open your project folder. Select Copilot as the session target.- Open the Command Palette with Command + Shift + P on macOS, or Ctrl + Shift + P on Windows/Linux.
- Run MCP: Add Server and choose HTTP (HTTP or Server-Sent Events).
- Enter
https://docs.bridge.new/mcpand name the serverbridgeDocs. - Choose Global → Copilot Global for your personal configuration, when available. Review the destination shown by your VS Code version and any server trust request.
- Open a Copilot conversation, enable the Bridge documentation tools for that session, and run the connection check below.
.mcp.json at the workspace root:
.vscode/mcp.json, which uses a servers object. Use the file for the connection you selected; do not mix the two shapes. If the portable destination is unavailable in your version, use the guided setup and its selected configuration file.
Example prompt:
Use bridgeDocs to read the Custom Connections guide and its separate OpenAPI contract. Prepare a landing-page form that records consent, obtains a new CAPTCHA token for each attempt and shows a 202 as accepted with its requestId. Keep captureKey, request fields and the configured CAPTCHA action unchanged. Do not use a REST API Key in the page.Official VS Code setup · Copilot configuration reference.
Check the connection
Ask this after configuring any of the four clients:Use the Bridge documentation MCP server to search for creating a Message. Read the MessageRequest schema from the published REST OpenAPI. Which three fields are required, and does a successful 201 prove WhatsApp delivery? Cite the exact Bridge source you read. Do not call the business API.A successful check uses a documentation tool and cites a Bridge page or schema. It should identify
conversationId, messageBody and enableExternalBroadcast as required. It should distinguish a created Message from a provider delivery receipt. A plausible answer without a tool call or source is not a connection test.
Read with any AI tool, without MCP
No MCP connection is required to read Bridge documentation. Give an assistant that can fetch URLs the trilingual documentation index, then choose the sources for your task and language:
The index points to individual
.md pages and the exact OpenAPI files. The combined collection includes all three languages; a language-specific collection is smaller. Collected endpoint descriptions do not replace the complete schemas in OpenAPI.
The language-specific files use JSON: the index lists page URLs, and each collection provides the page text as Markdown in its contentMarkdown field. The general llms.txt and llms-full.txt remain plain Markdown.
Example prompt:
Read https://docs.bridge.new/llms.txt and select the English sources for sending a PDF. Read the full attachment guide and the linked REST OpenAPI before writing code. Explain the upload sequence, required fields and delivery limitations. Preserve the published API signatures and cite the URLs you read. Prepare code only; do not make live requests.If you use MCP search, specify
language: "en", language: "es" or language: "pt-BR" to retrieve the requested language. HTTP exports use .md; MCP filesystem page reads use .mdx. For a concise capability and source guide, read Bridge integration guidance.
Build with the right contract
The server provides documentation search, complete page/schema reading in a virtual documentation filesystem, and optional documentation feedback. The filesystem tool does not run commands on your computer. Feedback is separate from searching and reading; use it only when you intend to send a documentation comment. Give your assistant the task and relevant workflow:- First conversation: Contact → Conversation → Message.
- Attachments: file bytes → checksum → presigned PUT → Message.
- Templates: discover variables before sending.
- Agent outbound: select an Agent and understand
forceSend, reuse and recovery. - Webhook receiver: verify, persist, acknowledge and process.
If the server does not appear
Client interfaces change over time. Setup options can differ by version and organization policy; use the linked provider documentation if your menus differ. Provider instructions last checked: November 14, 2026.

