OpenPipe MCP connector
The OpenPipe connector brings your logged calls, datasets, fine-tuned models and evaluation judges to Claude, ChatGPT, Cursor, Microsoft Copilot and any MCP client, so your team can work with OpenPipe from the tools they already use.
- Connects with an API key
- Free 14-day trial
- No credit card
List our OpenPipe datasets and their entry counts.
Working in OpenPipe with Elaichi
-
List all OpenPipe local testing only get latest logged calls
-
List all OpenPipe datasets
-
List all OpenPipe models
How to connect OpenPipe to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
OpenPipe 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.
OpenPipe MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
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.
OpenPipe 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. The plugin directory lives at chatgpt.com/plugins.
OpenPipe 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.
OpenPipe MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
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 OpenPipe 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.
What teams do with OpenPipe through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in OpenPipe is logged.
-
AI engineering
Turn logged calls into a training dataset
Pull the latest logged calls from OpenPipe, tag the good ones, and add them as entries to a dataset without leaving the chat you are already working in.
-
AI engineering
Kick off a fine-tune from a conversation
Pick a dataset, choose a base model, and start a fine-tuning job in OpenPipe, then check on it later by asking how the run is going.
-
Data science
Keep datasets tidy before a training run
List every dataset in OpenPipe, spot the stale or duplicate ones, and remove them so the next fine-tune starts from a clean set.
-
Quality
Score model output against your own criteria
Run a criteria judge in OpenPipe on a batch of responses and get a plain summary of where the model passed and where it fell short.
-
Product
Label production calls by feature and customer
Update tags and metadata on logged calls in OpenPipe after a launch, so the team can filter later by the feature or account that produced them.
-
Platform
Compare the models you have deployed
List the models in OpenPipe, look up any single one by ID, and retire the ones nobody is calling anymore.
Try asking
- “List our OpenPipe datasets and their entry counts.”
- “Which OpenPipe models were called most this week.”
- “Show the latest logged calls and their tags.”
What connecting OpenPipe gets you
6 screens from Elaichi, each doing one job for your OpenPipe account.
Ask Elaichi to work across your apps.
List our OpenPipe datasets and their entry counts.
Which OpenPipe models were called most this week.
Show the latest logged calls and their tags.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about datasets, get answers back.
Plain language questions run against live OpenPipe datasets, models and logged calls.
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot share one endpoint.
Reach OpenPipe from any MCP client over OAuth, no SDK, no shared key.
Tool catalog
23 OpenPipe tools ready to call.
Datasets, dataset entries, models, chat completions and logs, with no custom code.
Toolboxes
Every team gets its own toolbox.
Curate one OpenPipe toolbox per team so each sees only relevant tools.
Shared connections
Teammates use OpenPipe without seeing keys.
One connected OpenPipe account, shared to named teams and members, credential never exposed.
Audit log
Answer who touched which dataset.
Every OpenPipe call is logged with time, person, action, type and resource.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
OpenPipe digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch datasets
OpenPipe
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 Jake Morgan
Approve Deny -
Post the digest
OpenPipe
Queued
Automations
A schedule fires, a digest ships.
Six steps fetch OpenPipe logged calls, group them, draft, get approval, then post back.
OpenPipe health
Refreshed 4 minutes ago · every 15 minutes · from the datasets collection
Datasets
1,284 ↓ 12%
Dataset entries
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Datasets created
Last 14 days
By team
Share of activity
Machine learning 34%
Data platform 27%
Product engineering 21%
Quality 18%
Collections and dashboards
OpenPipe numbers land before anyone asks.
Four metrics, 14 days of dataset entries and a team breakdown, computed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for OpenPipe
All three can connect OpenPipe 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 OpenPipe tools | Allow or restrict single OpenPipe 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 OpenPipe 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.
OpenPipe tools for your AI agents
23 tools are ready to call through Elaichi's MCP endpoint the moment you connect OpenPipe, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect OpenPipe to Claude?
Connect OpenPipe in Elaichi first, which means pasting the API key you copy from your OpenPipe project settings. 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 the endpoint https://api.elaichi.ai/mcp. Sign in as yourself and OpenPipe is available in your next conversation.
Does OpenPipe work with ChatGPT and Cursor as well as Claude?
Yes. Once OpenPipe 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 OpenPipe once and every client picks it up.
What can an AI agent actually do with my OpenPipe data?
An agent can fetch your latest logged calls from OpenPipe, tag them, update their metadata and add the useful ones to a dataset. It can create and remove datasets, start a fine-tuning job, check how a fine-tune is going, list and look up your models, run a criteria judge on responses and send chat completions through OpenPipe. In short, the everyday work of building a dataset and training a model, done by asking.
Does connecting OpenPipe give the AI access to every project?
No. Access follows the OpenPipe API key the person connected, so the agent can only reach the project and records that key already covers. Elaichi can narrow that further by turning off individual actions, but it can never widen access beyond what OpenPipe itself grants.
Can I stop an agent from deleting datasets or models in OpenPipe?
Yes. Restrictions in Elaichi work per action, so you can allow an agent to read logged calls and add dataset entries while restricting it from deleting datasets, models or fine-tuning jobs in OpenPipe. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT or any other client cannot run it, whatever the prompt says.
What happens to an OpenPipe connection when someone leaves?
Offboarding that person in Elaichi ends their access to OpenPipe through every client at once. If they shared an OpenPipe connection with a team, it keeps working for everyone else on that team. Disconnecting OpenPipe once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client at the same time.
Does the OpenPipe MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. OpenPipe 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 OpenPipe?
Yes. Both let Claude, ChatGPT or Cursor use OpenPipe. 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 OpenPipe call.
How is Elaichi different from Composio for OpenPipe?
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 OpenPipe: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put OpenPipe 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