Skip to main content
Applies to:
  • Plan - Enterprise
  • Deployment - Self-hosted
Summary When your organization uses a dedicated or hybrid data plane (for example, a CloudFront-based endpoint), configure your MCP client to use the MCP URL from Settings > Data plane instead of the default SaaS endpoint.

​
Problem

MCP clients configured with the default SaaS endpoint (https://api.braintrust.dev/mcp) cannot read logs from orgs on a dedicated data plane. Symptoms include a data plane mismatch error, or sql_query returning empty results for projects that show data in the UI.

​
Configuration Steps

​
Step 1: Find your MCP URL

Go to Settings > Data plane and copy the value in the MCP URL card. This is your data plane’s API URL with the /mcp path appended.

​
Step 2: Configure MCP server with your MCP URL

Remove existing Braintrust MCP configuration, then add it with your MCP URL:
OAuth: If your client supports OAuth (Claude Code, Cursor, and most interactive MCP clients), omit the API key. Your client opens a browser login where you sign in to Braintrust, using your organization’s SSO if configured, then stores tokens automatically.
API key: Pass a Braintrust API key as a bearer token when your client does not support OAuth or cannot complete a browser login.

​
Step 3: Verify configuration

Restart your client and test the MCP connection. Log queries for projects on your dedicated data plane should return the same data visible in the UI.

​
Known Limitations

The Braintrust Claude Code plugin does not support custom data plane URLs. Use direct MCP setup as shown above instead of the plugin for hybrid deployments. If you need access to both a dedicated data plane and a SaaS org, add a second MCP connection for the SaaS endpoint.