Skip to main content

MCP Server

Connect Claude or Cursor to Bryn and ask questions in plain language: "which accounts hit pricing this week?", "what did Bryn run yesterday?", with no API code required. Whatever the Control Plane API exposes, an MCP client can use as tools.

Bryn exposes a Model Context Protocol server for this. It speaks streamable HTTP and is secured with Civic Auth over OAuth.

Endpoint​

https://bryn.civic.com/mcp

That is the whole address. Bryn works out which workspace you belong to from your Civic Auth sign-in, so there is nothing to fill in. You can also copy it from the Bryn dashboard under Integrations → MCP.

note

Opening the URL in a browser shows an error page. It is an MCP endpoint for your client to connect to, not a page to visit.

More than one workspace​

If you belong to several Bryn workspaces, the plain URL connects to one of them by default: the workspace you own, or the most recent one. To connect to a specific workspace, add its ID as a tenant query parameter:

https://bryn.civic.com/mcp?tenant=<tenantId>

Integrations → MCP shows the URL for the workspace you are currently viewing, so switch workspace in the dashboard to get the URL for another one. Clients that can send custom headers may pass X-Bryn-Tenant: <tenantId> instead of the query parameter.

No workspace yet​

If you sign in and have no Bryn workspace, connecting creates one for you and the agent walks you through onboarding inside the chat. You do not need to visit the dashboard first.

Authentication​

The server is secured with Civic Auth over OAuth. Clients that support OAuth will open the Bryn login page in your browser the first time you connect: sign in there, and the client is authorized automatically. There's no token or API key to copy.

Access is governed by your Civic Auth membership, the same way the REST API resolves it: the workspace is always taken from one of your own memberships. A tenant selector, if you give one, is validated against them, and naming a workspace you don't belong to is rejected with 403 tenant_forbidden.

Connecting​

Clients that don't yet support remote MCP servers with OAuth can bridge through mcp-remote, which handles the OAuth flow locally.

The snippets below use the plain URL. If you belong to several workspaces and want a specific one, append ?tenant=<tenantId> as described above.

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "bryn": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://bryn.civic.com/mcp"]
    }
  }
}

Restart Claude Desktop, then complete the Civic Auth sign-in when prompted.

note

Once connected, your client lists the tools Bryn provides; this page intentionally doesn't catalogue them. Discover the current set directly in your MCP client.