Setup MCP Connection¶

Connect an MCP client to Bifrost MCP and verify it is live. Once it is, work through the quickstart.

What you need¶

A Bifrost account with access to the platform. If you can sign in to the web app, you can connect.
An MCP client that supports remote servers over HTTP with OAuth, for example Claude Code, Claude Desktop, or Claude on the web.
The endpoint:
```
https://api.app.bifrost.ai/mcp
```
That single URL is all a client needs, since authorization is discovered from it automatically.

Connecting¶

Claude on the web or Claude Desktop¶

Open Settings and then Connectors.
Choose Add custom connector.
Give it a name (for example, Bifrost) and paste the endpoint URL above.
Save, then click Connect on the new connector and sign in with your Bifrost credentials.
Approve the requested access. The connector’s tools then appear in your conversations.

Claude Code¶

Add the server once, then authenticate:

claude mcp add --transport http bifrost https://api.app.bifrost.ai/mcp

Start Claude Code and run /mcp. Select the bifrost server, choose to authenticate, and complete the sign-in in your browser. The tools stay available in later sessions; /mcp shows the connection status at any time.

Another MCP client¶

Point the client at the same URL and let it run the standard remote-server flow:

Transport: streamable HTTP (POST and GET on /mcp). The server is stateless, so every request carries its own credentials.
Authorization: OAuth 2.1. An unauthenticated request is answered with 401 and a WWW-Authenticate challenge pointing at https://api.app.bifrost.ai/.well-known/oauth-protected-resource/mcp, which names the authorization server to use. Access tokens are sent as Authorization: Bearer <token> and are bound to this endpoint as their audience, so a token issued for anything else is rejected.

Verify the connection¶

Ask the assistant something only the connector can answer:

Who am I signed in as on Bifrost?

It should call get_my_profile and come back with the email on your Bifrost account. If it answers without calling the tool, or cannot answer at all, the connection is not live: re-check the steps above, then see the troubleshooting table in the quickstart.