Skip to content

Artificial Intelligence

Warp MCP connector

Connect Warp to Elaichi and Claude, ChatGPT, Cursor 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.

  • How it connects. Connects with an API key. 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 Warp to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Warp once

  1. Open Connections, choose Add connection, and pick Warp.

  2. Optionally set Share with to give a team access, then press Connect.

  3. Paste a Warp API key. One person generates a token in Warp and pastes it once. Everyone else works through Share with, and never sees it.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

warp
Warp
AirOps
Algolia
Botpress
Chatvolt
Cohere
2

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.

Connect Warp to 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.

Connect Warp to 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 today. The plugin directory lives at chatgpt.com/plugins.

Connect Warp to 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.

Connect Warp 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.

Use cases

What teams do with Warp through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • 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.”

See all 27 Warp tools below

AI tools

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.

See it in Elaichi

What connecting Warp gets you

6 screens from the product, each doing one job for your Warp account.

The agent

Ask about Warp agent runs in plain language.

Answers come from live Warp runs, transcripts and schedules, not stale exports.

  • agents
  • runs
  • transcripts
  • schedules

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 or Cursor

MCP clients

Claude, ChatGPT and Cursor reach Warp here.

One org MCP endpoint over OAuth, no SDK and no shared API key.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

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

Emma Laurent

• Connected 4 minutes ago
Cursor
S

Sofia Ricci

• Connected 2 hours ago
ChatGPT
C

Clara Nowak

• Connected Yesterday

Tool catalog

27 Warp tools are ready without custom code.

Browse tool names, resources and methods covering agents, runs, transcripts and schedules.

  • List all Warp agents
  • List all Warp agent connected self hosted workers
  • List all Warp run transcripts
  • Create a Warp agent run
ElaichiTools
Tool Action Description
List all Warp agents List List available Warp agents (skills) that can be used to run tasks, discovered from accessible environments or a specific repository. Returns each agent's name and a variants array; each variant includes id, description, base_prompt, source (owner, name, skill_path, worker_host), environments, last_run_timestamp, and error.
List all Warp agent connected self hosted workers List List currently connected self-hosted workers for the authenticated team in Warp. Returns: worker_host, connection_count, connected_at, last_seen_at. Worker presence is derived from websocket heartbeats and may be briefly stale.
List all Warp run transcripts List Retrieve the raw conversation transcript for a warp agent run. The API issues a 302 redirect to a time-limited download URL containing the transcript content; no structured JSON body is returned on success. Required: run_id.
Create a Warp agent run Create Spawn a Warp cloud agent run with a prompt and optional configuration. The agent is queued for execution and assigned a unique run ID. Returns: run_id, task_id, state, at_capacity. Required: prompt.
List all Warp agent runs List List Warp agent runs with optional filtering by state, creator, model, date range, skill, and more. Results default to sort_by=updated_at and sort_order=desc. Returns: run_id, task_id, title, state, execution_location, prompt, created_at, updated_at, run_time, started_at, status_message, source, schedule, session_id, session_link, trigger_url, creator, executor, request_usage, agent_config,…

Toolboxes

Each team gets its own Warp toolbox.

Toolboxes are scoped per team, so platform and support see different Warp tools.

  • Platform
  • Engineering
  • Support
  • Automation
ElaichiToolboxes
Name Source template Tools Created

Platform toolbox

Warp · agents and self-hosted workers

Warp starter 18 Mar 4, 2026

Engineering toolbox

Warp · agent runs and followups

9 Mar 2, 2026

Support toolbox

Warp · run transcripts and conversations

24 Feb 27, 2026

Automation toolbox

Warp · agent schedules and cancelations

Warp starter 6 Feb 19, 2026

Data toolbox

Warp · run timelines and reporting

31 Jan 30, 2026

Security toolbox

Warp · connected workers and access review

12 Jan 22, 2026

Shared connections

Teammates use Warp without seeing a credential.

The connections table shows who connected each Warp account and its shared teams.

  • Platform
  • Engineering EMEA
  • Support
  • Automation
ElaichiConnections
Connection Scope Status Access
WA

Warp (Platform)

Connected by Emma Laurent

Personal • Active 1 team · 6 members
WA

Warp (Engineering EMEA)

Connected by James Whitfield

Organization • Active 3 teams · 24 members
WA

Warp (Support)

Connected by Sofia Ricci

Organization • Active 2 teams · 11 members
WA

Warp (Automation)

Connected by Daniel Ortega

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

Warp (Data)

Connected by Clara Nowak

Personal • Active Not shared
WA

Warp (Security)

Connected by Michael Brennan

Personal • Active 2 teams · 9 members

Audit log

Every Warp call is answerable after the fact.

Append-only rows record when, who, what happened, type and Warp resource touched.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emma Laurent

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

James Whitfield

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

S

Sofia Ricci

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

D

Daniel Ortega

[email protected]

Warp Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

C

Clara Nowak

[email protected]

Warp Agents Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

M

Michael Brennan

[email protected]

Warp Agents List Toolbox

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 turns Warp runs into a digest.

Six steps fetch runs, group them, draft a digest, wait for approval, post back.

Warp digest

Run 418 · started 2 minutes ago · on behalf of Emma Laurent

  1. Schedule

    Every weekday at 08:00

    0.2s
  2. Fetch agents

    Warp

    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 Michael Brennan

    Approve
  6. Post the digest

    Warp

    Queued

Collections and dashboards

Warp agent health arrives before anyone asks.

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

Warp health

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

Live

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%

FAQ

Frequently asked questions

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, 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 my team share one Warp connection?

Yes. One person connects Warp in Elaichi and shares the connection with a team, and nobody else ever handles or sees the Warp API key. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every Warp run started, schedule changed or transcript read.

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 blocking the ability to start runs, cancel them, or delete and edit schedules. A blocked action is never advertised to Claude, ChatGPT or Cursor, so no prompt, however worded, can reach it.

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 and every other client at the same time.

Put Warp in front of your team

Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.