Braintrust MCP connector
The Braintrust connector lets Claude, ChatGPT, Cursor 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.
-
How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Braintrust to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Braintrust once
-
Open Connections, choose Add connection, and pick Braintrust.
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in Braintrust. Braintrust's own window opens. Whoever approves it decides what this connection can reach.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Braintrust MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
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 ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Braintrust MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
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.
Connect Braintrust to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
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.
Use cases
What teams do with Braintrust through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
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”
Compare
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.
| 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 | $15 per user per month. | 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.
AI tools
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.
No tools match your search.
See it in Elaichi
What connecting Braintrust gets you
6 screens from the product, each doing one job for your Braintrust account.
The agent
Ask about Braintrust experiments in plain language.
Summarize an experiment, run a query over traces, and get a permalink back.
- experiments
- traces
- patterns
- monitoring views
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 or Cursor
MCP clients
One endpoint brings Braintrust to every client.
Claude, ChatGPT and Cursor connect over OAuth, with no SDK and no shared API key.
Copy the endpoint
Tool catalog
43 Braintrust tools, ready without any code.
Experiments, traces, patterns, facets and monitoring views, covered without writing a line of custom code.
- SQL query
- Infer schema
- Summarize experiment
- List recent objects
Toolboxes
Each team gets its own Braintrust toolbox.
Scope what AI engineering, product and support can reach in Braintrust, team by team.
- AI Engineering
- Product
- Quality
- Data
Shared connections
Share one Braintrust connection, never a credential.
Teammates query traces and experiments through a shared connection without seeing a secret.
- AI Engineering
- Product
- Quality
- Data
Audit log
Every Braintrust call answers who did what.
When, who, what happened and which trace or pattern, in an append-only log.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule drafts the Braintrust digest itself.
Experiments are fetched, grouped and summarized, a person approves, then it posts back to Braintrust.
Braintrust digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch experiments
Braintrust
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Braintrust
Queued
Collections and dashboards
Braintrust health numbers arrive without being asked.
Four metrics, 14 days of experiments created and a team breakdown, refreshed on schedule.
Braintrust health
Refreshed 4 minutes ago · every 15 minutes · from the experiments collection
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%
FAQ
Frequently asked questions
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, 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 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 blocking the creation of patterns, facets, preprocessors or monitoring views. A restricted action is never advertised to the AI client, so no prompt, however it is worded, can reach it.
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 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, 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 on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.