Skip to content

Braintrust MCP connector

The Braintrust connector lets Claude, ChatGPT, Cursor, Microsoft Copilot and other MCP clients work with experiments, traces and monitoring views in Braintrust as the signed-in person, with every action recorded in an audit log.

  • Connects over OAuth
  • Free 14-day trial
  • No credit card

Regions: US and EU. Elaichi supports all of them; you pick your region when you connect.

ChatGPT Elaichi connected

Summarize the latest experiment in the checkout project

Working in Braintrust with Elaichi

  • SQL query
  • List recent objects
  • Get trace work items
Ask anything…
Governance / Audit log Last 24 hours
Braintrust Get trace work items Emily Carter · ChatGPT · 9:41 AM Done
Braintrust List recent objects Emily Carter · ChatGPT · 9:41 AM Done
Braintrust SQL query Emily Carter · ChatGPT · 9:41 AM Done
Braintrust Infer schema Megan Brooks · Claude · 9:38 AM Done
Braintrust Summarize experiment Ryan Hayes · Cursor · 9:35 AM Done

How to connect Braintrust to Claude, ChatGPT, Cursor or Microsoft Copilot

Step by step, for each AI app

Braintrust MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Braintrust MCP connector for Claude Code

  1. 1

    In a terminal, run claude mcp add with the endpoint.

    https://api.elaichi.ai/mcp
  2. 2

    Start Claude Code and run /mcp.

  3. 3

    Pick elaichi, then sign in and approve in the browser.

Terminal

$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp

Use --scope project instead to share it with the repository through .mcp.json.

Braintrust MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

Braintrust MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

Braintrust MCP connector for Microsoft Copilot

  1. 1

    In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.

  2. 2

    Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.

    https://api.elaichi.ai/mcp
  3. 3

    Create a new connection, sign in and approve, then press Add to agent.

  4. 4

    Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Server URL
https://api.elaichi.ai/mcp
Authentication
OAuth 2.0
Type
Dynamic discovery

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

Connect Braintrust to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

What teams do with Braintrust through Elaichi

Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Braintrust is logged.

  • AI Engineering

    Summarize an experiment after an eval run

    Ask for the headline scores and the biggest regressions in the latest Braintrust experiment, then get a permalink to share with the team.

  • Product

    Find out what users are asking about

    Turn on topics automation for a project and ask which topics grew this week in Braintrust logs, without opening a dashboard.

  • Quality

    Catch a recurring failure before it spreads

    Search the existing patterns in Braintrust, add a new one for the failure you just saw, and test a facet against a real trace.

  • Data

    Answer a question with a SQL query

    Ask how many traces scored below threshold last week and let the agent infer the schema and run the query in Braintrust.

  • Platform

    Keep an eye on production monitors

    List the monitoring views in Braintrust, pull a chart for latency or cost, and create a new view when a project needs its own.

  • Support

    Work through flagged traces as a queue

    Pull the trace work items assigned to you, review each one, and update the work report in Braintrust as you go.

Try asking

  • “Summarize the latest experiment in the checkout project”
  • “Which topics grew the most in support bot logs this week?”
  • “Create a pattern for the hallucinated refund policy failure”

See all 43 Braintrust tools →

What connecting Braintrust gets you

6 screens from Elaichi, each doing one job for your Braintrust account.

Elaichi Agent

Ask Elaichi to work across your apps.

Summarize the latest experiment in the checkout project

Which topics grew the most in support bot logs this week?

Create a pattern for the hallucinated refund policy failure

Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot

The agent

Ask about Braintrust experiments in plain language.

Summarize an experiment, run a query over traces, and get a permalink back.

ElaichiAI apps
Claude ChatGPT Cursor Microsoft Copilot

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

AI apps

One endpoint brings Braintrust to every client.

Claude, ChatGPT, Cursor and Microsoft Copilot connect over OAuth, with no SDK and no shared API key.

ElaichiTools
Tool Action Description
SQL query Search Query experiments, datasets, and logs using SQL. Supports SELECT, FROM, WHERE, GROUP BY, ORDER BY, and LIMIT.
Infer schema Action Discover the available fields, data types, and most common values in experiments, datasets, or logs.
Summarize experiment Action Get aggregated performance metrics for an experiment, optionally compared to a baseline.
List recent objects List List recently created projects, experiments, datasets, prompts, or functions you have access to.
Resolve object Action Convert names to IDs or vice versa, and parse Braintrust URLs. For pattern, prompt, and scorer URLs, returns the containing project as object_id and the resource as row_id. App URLs retain their organization scope. Supply org_name to disambiguate name lookups. Ambiguous names…

Tool catalog

43 Braintrust tools, ready without any code.

Experiments, traces, patterns, facets and monitoring views, covered without writing a line of custom code.

ElaichiToolboxes
Name Source template Tools Created

AI Engineering toolbox

Braintrust · experiments and traces

Braintrust starter 18 Mar 4, 2026

Product toolbox

Braintrust · topics and usage

— 9 Mar 2, 2026

Quality toolbox

Braintrust · patterns and facets

— 24 Feb 27, 2026

Data toolbox

Braintrust · SQL queries and schemas

Braintrust starter 6 Feb 19, 2026

Platform toolbox

Braintrust · monitoring views and charts

— 31 Jan 30, 2026

Support toolbox

Braintrust · trace work items

— 12 Jan 22, 2026

Toolboxes

Each team gets its own Braintrust toolbox.

Scope what AI engineering, product and support can reach in Braintrust, team by team.

ElaichiConnections
Connection Scope Status Access
BR

Braintrust (AI Engineering)

Connected by Emily Carter

Personal • Active 1 team · 6 members
BR

Braintrust (Product)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
BR

Braintrust (Quality)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
BR

Braintrust (Data)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
BR

Braintrust (Platform)

Connected by Ryan Hayes

Personal • Active Not shared
BR

Braintrust (Support Triage)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Shared connections

Share one Braintrust connection, never a credential.

Teammates query traces and experiments through a shared connection without seeing a secret.

ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

[email protected]

Braintrust Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

Braintrust Experiments Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

Braintrust Experiments List Toolbox

Audit log

Every Braintrust call answers who did what.

When, who, what happened and which trace or pattern, in an append-only log.

From answering questions to doing the work

A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.

Braintrust digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch experiments

    Braintrust

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Jake Morgan

    Approve
  6. Post the digest

    Braintrust

    Queued

Workflows

A schedule drafts the Braintrust digest itself.

Experiments are fetched, grouped and summarized, a person approves, then it posts back to Braintrust.

Braintrust health

Refreshed 4 minutes ago · every 15 minutes · from the experiments collection

Live

Experiments

1,284 ↓ 12%

Traces

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Experiments created

Last 14 days

By team

Share of activity

AI Engineering 34%

Product 27%

Quality 21%

Data 18%

Collections and dashboards

Braintrust health numbers arrive without being asked.

Four metrics, 14 days of experiments created and a team breakdown, refreshed on schedule.

Why connect Braintrust's MCP server through Elaichi

Braintrust builds and runs this MCP server. Elaichi sits in front of it, so Braintrust's tools follow the same sign-in, access rules and audit log as every other connector your organization uses. Calls an AI client makes to Braintrust's server directly, outside Elaichi, get none of this.

  • One address for every AI client

    Claude, ChatGPT, Cursor and Microsoft Copilot reach Braintrust's tools at the same Elaichi address as every other connected app. Nobody adds Braintrust's server to each client one by one.

  • Each person signs in as themselves

    Each person signs in to Elaichi as themselves. Members connect with their own Braintrust sign-in, and a connection someone shares runs on its owner's account. The credential stays in Elaichi's separate credential service, and the AI client holds only its Elaichi sign-in.

  • Rules checked before a call leaves

    Restrictions on a role or a person, for the whole connector or a single tool, are checked before a call reaches Braintrust's server. By default, a tool Braintrust does not mark read-only or non-destructive counts as destructive, and over MCP it still runs under the "Use your connected apps" consent.

  • One audit log for every app

    Each call that runs is recorded with the person, the tool, the connection and the AI client that made it, in the same audit log as every other app.

  • Tool issues go to Braintrust

    Braintrust builds and runs these tools, and Elaichi staff do not curate them, so a report about how a tool behaves goes to the Braintrust team.

    www.braintrust.dev/contact

Why run a vendor's MCP server through Elaichi →

For IT and engineering

Elaichi vs Zapier MCP vs Composio for Braintrust

All three can connect Braintrust to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for Braintrust, by what to check
What to check Elaichi Zapier MCP Composio
Where the AI connects One address for the whole organization. https://api.elaichi.ai/mcp A server per member, created at sign-in. An MCP endpoint per team, or an SDK.
Control over Braintrust tools Allow or restrict single Braintrust tools, per role or user. App and action restrictions on the account. Role permissions, down to the action.
Record of calls One audit entry per Braintrust call. A History tab of tool calls. A log of every tool call.
Single sign-on SAML or OIDC, plus SCIM, on Gold. SAML on Enterprise. SAML and OIDC on Enterprise.
Price Free for one person; $15 per user per month on Gold. 2 tasks per successful call. Billed per tool call.

Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

Braintrust tools for your AI agents

43 tools are ready to call through Elaichi's MCP endpoint the moment you connect Braintrust, governed by the same roles, restrictions, and audit log as everything else in Elaichi. Braintrust builds and runs these tools.

Questions, answered

How do I connect Braintrust to Claude?

Connect Braintrust in Elaichi first: you sign in to Braintrust over OAuth with your own account, and there is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude asks you to sign in to Elaichi, and from then on it can work with your Braintrust experiments, traces and monitoring views.

Does Braintrust work with ChatGPT and Cursor as well as Claude?

Yes. Once Braintrust is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect Braintrust once and every client picks it up, and you still sign in as yourself in each one.

What can an AI agent actually do with my Braintrust data?

It can summarize an experiment, run a SQL query over your logs and traces, list recent objects in a project, and generate a permalink to whatever it found. It can also search and create patterns, test a facet or preprocessor on a trace, turn on topics automation, and pull or create monitoring views and charts in Braintrust. Short, concrete asks such as summarize yesterday's experiment in the checkout project work better than long paragraphs.

Does connecting Braintrust give the AI access to every project and organization?

No. The agent works inside the Braintrust access of the person who signed in, so it sees the organizations and projects that person can already open and nothing more. Elaichi can narrow that further with roles and restrictions, and it never widens it beyond what Braintrust itself allows.

Can my team share one Braintrust connection?

Yes. One person connects Braintrust in Elaichi and shares the connection with a team, and nobody else ever handles a credential or an API key. Each teammate still signs in to Elaichi as themselves, so the audit log names the person who ran each query or created each pattern in Braintrust.

Can I stop an agent from changing patterns or monitoring views in Braintrust?

Yes. Restrictions in Elaichi work per action, so you can allow reading experiments and traces in Braintrust while restricting the creation of patterns, facets, preprocessors or monitoring views. A restricted action still appears in Elaichi's tool search, flagged as restricted, but the AI client cannot run it, whatever the prompt says.

What happens to a Braintrust connection when someone leaves?

Offboarding that person in Elaichi ends their access to Braintrust through every client at once. A shared Braintrust connection keeps working for everyone else on the team. If you disconnect Braintrust in Elaichi, it disappears from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client in one step.

Does the Braintrust MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Braintrust is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Is Elaichi an alternative to Zapier MCP for Braintrust?

Yes. Both let Claude, ChatGPT or Cursor use Braintrust. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Braintrust call.

How is Elaichi different from Composio for Braintrust?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Braintrust: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put Braintrust in front of your team

14 days of Black, no credit card. Connect it once and pick what each team can call.

When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.

Add one link to your AI app

The same link for everyone on your team.

https://api.elaichi.ai/mcp
  • ChatGPT
  • Claude
  • Cursor
  • Microsoft Copilot