Warp MCP connector
Connect Warp to Elaichi and Claude, ChatGPT, Cursor, Microsoft Copilot or any MCP client can start and follow Warp agent runs, read transcripts, and manage schedules, with each person acting under their own Warp access and every call logged.
- Connects with an API key
- Free 14-day trial
- No credit card
Summarize yesterday's Warp agent runs by agent.
Working in Warp with Elaichi
-
List all Warp agents
-
List all Warp agent connected self hosted workers
-
List all Warp run transcripts
How to connect Warp to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Warp 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.
Warp 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.
Warp 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.
Warp 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.
Warp 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 Warp 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 Warp through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Warp is logged.
-
Engineering
Start a Warp agent run from chat
Describe the task in Claude, pick the Warp agent, environment and model, and kick off the run without switching windows. Check back later and ask how it is going.
-
Engineering
Catch up on what an agent did
Pull the transcript and timeline of a Warp run, ask for a plain summary of the changes, and send a follow-up message to the agent if something needs clarifying.
-
Platform
Keep scheduled agent runs on track
Create a Warp agent schedule for recurring maintenance, pause it during a freeze, resume it afterward, and adjust the timing when the team's rhythm changes.
-
Engineering management
Spot stuck or failing runs early
List agent runs across the team, find the ones that have been going too long or ended badly, and cancel what is stuck before it burns more compute.
-
Support
Reconstruct a run that misbehaved
When a user reports a bad result, pull the run conversation, harness support transcripts and artifacts together so the problem is understood before anyone replies.
-
IT and security
Know which agent identities exist
List the agent identities, environments and connected self-hosted workers in Warp, and create a new identity for a project without hunting through settings.
Try asking
- “Summarize yesterday's Warp agent runs by agent.”
- “Which Warp agent schedules created runs this week?”
- “Show the transcript for our longest Warp run.”
What connecting Warp gets you
6 screens from Elaichi, each doing one job for your Warp account.
Ask Elaichi to work across your apps.
Summarize yesterday's Warp agent runs by agent.
Which Warp agent schedules created runs this week?
Show the transcript for our longest Warp run.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about Warp agent runs in plain language.
Answers come from live Warp runs, transcripts and schedules, not stale exports.
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot reach Warp here.
One org MCP endpoint over OAuth, no SDK and no shared API key.
Tool catalog
27 Warp tools are ready without custom code.
Browse tool names, resources and methods covering agents, runs, transcripts and schedules.
Toolboxes
Each team gets its own Warp toolbox.
Toolboxes are scoped per team, so platform and support see different Warp tools.
Shared connections
Teammates use Warp without seeing a credential.
The connections table shows who connected each Warp account and its shared teams.
Audit log
Every Warp call is answerable after the fact.
Append-only rows record when, who, what happened, type and Warp resource touched.
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.
Warp digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch agents
Warp
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
Warp
Queued
Automations
A schedule turns Warp runs into a digest.
Six steps fetch runs, group them, draft a digest, wait for approval, post back.
Warp health
Refreshed 4 minutes ago · every 15 minutes · from the agents collection
Agents
1,284 ↓ 12%
Runs
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Agents created
Last 14 days
By team
Share of activity
Platform 34%
Engineering EMEA 27%
Support 21%
Automation 18%
Collections and dashboards
Warp agent health arrives before anyone asks.
Four metrics, 14 days of runs created and a team breakdown, refreshed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Warp
All three can connect Warp 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 Warp tools | Allow or restrict single Warp 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 Warp 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.
Warp tools for your AI agents
27 tools are ready to call through Elaichi's MCP endpoint the moment you connect Warp, 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 Warp to Claude?
First connect Warp in Elaichi by pasting a Warp API key when prompted; there is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. Sign in with your Elaichi account and Warp appears in Claude, ready to use.
Does Warp work with ChatGPT and Cursor as well as Claude?
Yes. Once Warp 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 Warp once and every client you use picks it up.
What can an AI agent actually do with my Warp data?
With Warp connected through Elaichi, an AI agent can list your Warp agents, start a run, check its status, cancel it, read the transcript, timeline and conversation, and send a follow-up. It can also create, update, pause, resume or delete agent schedules, look up environments, models, artifacts, agent identities and connected self-hosted workers, and read harness support transcripts. It cannot do anything in Warp beyond those actions.
Does connecting Warp give the AI access to all my agents and runs?
No. An AI client only reaches what the Warp API key used to connect can already reach, so access follows the person who connected and the permissions their Warp account has. Elaichi can narrow that further with restrictions on individual actions, but it can never widen what Warp itself allows.
Can I stop an agent from deleting or changing things in Warp?
Yes. Restrictions in Elaichi apply per action, so you can allow reading Warp runs and transcripts while restricting the ability to start runs, cancel them, or delete and edit schedules. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor or Microsoft Copilot cannot run it, whatever the prompt says.
What happens to a Warp connection when someone leaves?
When you offboard someone in Elaichi, their access to Warp through every AI client ends at once. If they had shared a Warp connection with a team, that connection keeps working for everyone else. If you want Warp gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client at the same time.
Does the Warp MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Warp 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 Warp?
Yes. Both let Claude, ChatGPT or Cursor use Warp. 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 Warp call.
How is Elaichi different from Composio for Warp?
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 Warp: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Warp 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