Skip to main content
External MCP (Model Context Protocol) servers give Loop context and tools from other services. Depending on the server, Loop can:
  • Match recurring failures to known issues in your issue tracker.
  • Consult internal documentation to understand expected behavior.
  • Create follow-up tasks with supporting traces, without leaving the investigation.
Connections belong to a project and share the account’s or key’s permissions, including access to write tools the server exposes.
External MCP connections in Loop are in public preview and can change before reaching general availability.
To give Claude Code, Cursor, or another AI coding agent access to Braintrust data, use the Braintrust MCP server.

Connect a server

You need a remote MCP server that supports Streamable HTTP, its URL, and an OAuth account or bearer API key.
1

Add the server

Ask Loop to connect an MCP server to open project settings in the workspace, or go to Settings > MCP, add a new server, and enter its Name and URL.
2

Authenticate

Project members can use these connections with the shared credentials’ access. Scheduled Loop runs, including pattern rules, can invoke all tools those credentials allow without interactive approval. Use an account or key limited to the access you intend to share with the project.
In Credentials, choose an authentication method:
  • OAuth: Click Connect with OAuth, sign in, then click Save. Closing without saving discards the connection.
    Ask its administrator to approve https://www.braintrust.dev/redirects/mcp-client before connecting. Providers that allow clients to register themselves need no setup: Braintrust registers the URL automatically.
  • API key: Enter the server’s bearer token in API key, then click Save. Do not include the Bearer prefix.
    Don’t paste API keys into Loop messages or save them in sandbox files, where they become part of the conversation or sandbox contents instead of the project’s encrypted credential store.
3

Test and use the connection

Open the saved server and click Test connection. A successful test reports how many tools the server exposes.Send your next message in the same Loop thread. Loop picks up saved connection changes on that message, so you don’t need to start a new thread.For example, if you connected a Linear MCP server, ask:

Access and security

Project MCP credentials are encrypted and stored on your data plane. Loop and prompts using project MCP servers can use these credentials to authenticate requests. Calls using saved credentials have the shared account’s or API key’s permissions, rather than each project member’s individual permissions on the external service. Loop’s MCP calls run outside the sandbox.

Manage connections

Open a server in project MCP settings to manage its credentials.
  • OAuth: Access tokens refresh automatically while the provider’s refresh token remains valid. If authorization expires or is revoked, or if you change the server URL, click > Reconnect, complete the sign-in flow, then click Save.
  • API key: Click Replace, enter the new key, then click Save.
  • Authentication method: In the other method’s tab, connect with OAuth or enter an API key, then click Save.
Replacing credentials or switching authentication methods changes the external account or key used by everyone sharing the connection, including scheduled automations and prompts that use saved project credentials.
For OAuth credentials, click > Remove. For an API key, click . Then click Save. To cancel the removal before saving, click Undo.
Removing credentials removes the project’s stored authentication for that server. The change takes effect on the next Loop turn, including in scheduled automations. Prompts that rely on these credentials can no longer authenticate with the server.
When Loop can’t reach a configured server, it explains why:
  • Missing or rejected credentials: Reconnect with OAuth or replace the API key.
  • Timeout or connection failure: Check that the server is reachable with Test connection.
  • Unsupported protocol version: Contact Braintrust support. Reconnecting does not fix a protocol mismatch.
  • Redirect URI error: For redirect_uri_mismatch or invalid redirect_uri, ask the provider’s administrator to approve https://www.braintrust.dev/redirects/mcp-client.
  • Test succeeds but tools are missing: Send another Loop message to load the saved connection.
Opening the settings panel or saving a server without credentials does not authenticate it.

Limitations

  • Remote servers only. Connections require a remote MCP server that supports Streamable HTTP and authenticates with OAuth or a bearer API key.
  • Shared credentials. Everyone using the project’s connection acts with the shared account’s or key’s permissions on the external service, rather than their own account’s permissions.
  • External writes depend on the server. An MCP connection can expose tools that change external data. Braintrust’s Write tool permissions do not restrict these tools. Limit access through the external account or key.
  • No interactive approval in scheduled runs. Loop automations and Patterns can invoke all tools the shared credentials allow without interactive approval.
  • On BYOC, connections come from your data plane. Loop connects to MCP servers from the Loop runtime in your BYOC deployment, so the servers must be reachable from it. Deployments without the runtime can’t use external MCP servers. See BYOC Loop availability.

Next steps