Bridge MCP Server
Find the Bridge MCP endpoint and understand how MCP clients access workspace data and actions through OAuth 2.0 and workspace-scoped permissions.
Connect an MCP client to Bridge
The Bridge MCP server lets an authorized MCP client access data and actions within your Bridge workspace. The server uses Streamable HTTP and OAuth 2.0, with permissions controlled by read and write scopes.
Connection URL
https://api.meetonbridge.com/mcp
| Property | Value |
|---|---|
| Transport | Streamable HTTP |
| Authentication | OAuth 2.0 |
| Scopes | read, write |
| Access boundary | Your Bridge workspace |
Understand access and authentication
OAuth access is scoped to the user's Bridge workspace. The read scope allows an MCP client to retrieve meeting and related workspace context. The write scope allows the client to perform authorized actions in Bridge, such as booking, inviting, or updating meetings and running agents.
Bridge MCP authorization is unavailable on Starter and Trial plans. Existing connections remain read-only until you reconnect them with write access.
OAuth clients can discover the protected-resource metadata for the server at:
https://api.meetonbridge.com/.well-known/oauth-protected-resource
Discover the available context
Call get_bridge_context before using other Bridge capabilities. The response helps an MCP client understand the current authorization context and choose actions that match the user's workspace.
The capability returns:
- User identity and timezone
- Bridge workspace
- Current plan
- Connected apps
- Granted permissions
- Available tools
Use this context to determine which data the client may read, which actions it may perform, and which tools are available for the current workspace.