Skip to content

Application Development

WarpStream MCP connector

The WarpStream connector lets Claude, ChatGPT, Cursor or any MCP client manage your WarpStream virtual clusters, credentials, access rules and pipelines through one governed endpoint, with every action tied to the person who signed in.

Connect on Elaichi How to connect

  • 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 WarpStream to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect WarpStream once

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

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

  3. Paste a WarpStream API key. One person generates a token in WarpStream 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.

warpstream
WarpStream
Apache Airflow
Apify
Boomi
Browserbase
Caspio
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.

WarpStream 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.

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

WarpStream 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.

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

Connect WarpStream on Elaichi See pricing

Use cases

What teams do with WarpStream through Elaichi

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

  • Platform engineering

    Spin up a virtual cluster for a new service

    Ask for a new WarpStream virtual cluster, set its configuration and tier, and hand back a credential to the team that needs it, all from the chat window you already have open.

  • Data engineering

    Create a pipeline from a plain description

    Describe the stream you want moved and where it should land, and the agent creates the WarpStream pipeline and its configuration for you to check before anything runs.

  • Security

    Review who can read and write each stream

    List the access rules, credentials and API keys across your WarpStream account, spot anything stale or too broad, and remove it in the same conversation.

  • Operations

    Check consumer groups when a stream falls behind

    Ask which consumer groups are attached to a WarpStream cluster and pull the cluster's details and configuration while you work out where the delay is.

  • Finance

    See quotas and tiers before the bill arrives

    Look up the quota on a WarpStream cluster and which tier each cluster is on, so tier changes are deliberate rather than discovered on the invoice.

  • Developer support

    Hand a developer access without a ticket

    When someone needs to publish to a WarpStream cluster, create the credential or API key for them, list what already exists, and delete it when the work is done.

Try asking

  • “List every WarpStream virtual cluster and its current tier.”
  • “Which WarpStream API keys have no cluster credentials attached?”
  • “Summarize configuration changes across our production virtual clusters.”

See all 58 WarpStream tools below

Compare

Elaichi vs Zapier MCP vs Composio for WarpStream

All three can connect WarpStream 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 WarpStream, 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 WarpStream tools Allow or restrict single WarpStream 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 WarpStream 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

WarpStream tools for your AI agents

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

See it in Elaichi

What connecting WarpStream gets you

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

The agent

Ask about virtual clusters, get live answers.

Plain language questions return current WarpStream cluster, credential and API key records.

  • virtual clusters
  • api keys
  • credentials
  • configurations

Ask Elaichi to work across your apps.

List every WarpStream virtual cluster and its current tier.

Which WarpStream API keys have no cluster credentials attached?

Summarize configuration changes across our production virtual clusters.

Also runs in Claude, ChatGPT or Cursor

MCP clients

Claude, ChatGPT and Cursor share one endpoint.

Connect any MCP client to WarpStream over OAuth, no SDK, no shared key.

ElaichiMCP clients
Claude ChatGPT Cursor

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

Tool catalog

58 WarpStream tools are ready to call.

Virtual clusters, configurations, credentials and API keys covered, with no custom code.

  • Create a WarpStream API key
  • Delete a WarpStream API key by ID
  • List all WarpStream API keys
  • Create a WarpStream virtual cluster
ElaichiTools
Tool Action Description
Create a WarpStream API key Create Create a new WarpStream API key with the specified name and access grants. Returns: id, created_at. API key names may only contain underscores and alphanumeric characters; WarpStream prepends an `akn_` prefix automatically. Required: name, access_grants.
Delete a WarpStream API key by ID Delete Delete a WarpStream API key by its api_key_id. Returns an empty response on success. Required: api_key_id.
List all WarpStream API keys List List all WarpStream API keys belonging to the same workspace as the authenticating key. Returns: id, created_at, virtual_cluster_id.
Create a WarpStream virtual cluster Create Create a new WarpStream virtual cluster. A new agent key is automatically provisioned with every cluster. Returns: virtual_cluster_id. Required: virtual_cluster_name, virtual_cluster_type, virtual_cluster_region, virtual_cluster_cloud_provider, virtual_cluster_tier.
Delete a WarpStream virtual cluster by ID Delete Permanently delete a WarpStream virtual cluster. Both virtual_cluster_id and virtual_cluster_name are required as confirmation that the correct cluster is being deleted. This operation is irreversible — all topics and data will be lost. Returns an empty 204 response on success. Required: virtual_cluster_id, virtual_cluster_name.

Toolboxes

Every team gets its own WarpStream toolbox.

Toolboxes scoped per team decide which WarpStream tools that team can reach.

  • Platform engineering
  • Data engineering
  • SRE
  • Security
ElaichiToolboxes
Name Source template Tools Created

Platform engineering toolbox

WarpStream · virtual clusters and tiers

 WarpStream starter 18 Mar 4, 2026

Data engineering toolbox

WarpStream · cluster configurations and credentials

 — 9 Mar 2, 2026

SRE toolbox

WarpStream · cluster health and limits

 — 24 Feb 27, 2026

Security toolbox

WarpStream · API keys and rotation

 WarpStream starter 6 Feb 19, 2026

Application development toolbox

WarpStream · client credentials and endpoints

 — 31 Jan 30, 2026

Finance operations toolbox

WarpStream · cluster tiers and spend

 — 12 Jan 22, 2026

Shared connections

Teammates use WarpStream without seeing a credential.

One connected account, shared with named teams and members, secrets stay hidden.

  • Platform
  • Data engineering
  • SRE
  • Production
ElaichiConnections
Connection Scope Status Access
WA

WarpStream (Platform)

Connected by Emily Carter

 Personal • Active 1 team · 6 members
WA

WarpStream (Data engineering)

Connected by Jake Morgan

 Organization • Active 3 teams · 24 members
WA

WarpStream (SRE)

Connected by Megan Brooks

 Organization • Active 2 teams · 11 members
WA

WarpStream (Production)

Connected by Tyler Reed

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

WarpStream (Staging)

Connected by Ryan Hayes

 Personal • Active Not shared
WA

WarpStream (Security)

Connected by Ashley Parker

 Personal • Active 2 teams · 9 members

Audit log

Every WarpStream call lands on the record.

An append-only log shows when, who, what happened, type and resource.

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

2 minutes ago

Mar 6, 2026, 3:10 PM
E

Emily Carter

emily.carter@northwind.io

 Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM
J

Jake Morgan

jake.morgan@northwind.io

 Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM
M

Megan Brooks

megan.brooks@northwind.io

 Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM
T

Tyler Reed

tyler.reed@northwind.io

 WarpStream Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM
R

Ryan Hayes

ryan.hayes@northwind.io

 WarpStream Virtual clusters Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM
A

Ashley Parker

ashley.parker@northwind.io

 WarpStream Virtual clusters 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 runs WarpStream work end to end.

Six steps fetch virtual clusters, group them, draft a digest, await approval, post back.

WarpStream digest

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

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch virtual clusters

    WarpStream

    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

    WarpStream

    Queued

Collections and dashboards

WarpStream health, computed and refreshed on schedule.

Four metrics, 14 days of clusters created, and a team breakdown, no model.

WarpStream health

Refreshed 4 minutes ago · every 15 minutes · from the virtual clusters collection

Live

Virtual clusters

1,284 ↓ 12%

Api keys

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Virtual clusters created

Last 14 days

By team

Share of activity

Platform 34%

Data engineering 27%

SRE 21%

Production 18%

Related connectors

More from the catalog

Browse all 600+ connectors →

FAQ

Frequently asked questions

How do I connect WarpStream to Claude?

Connect WarpStream in Elaichi first: you paste a WarpStream API key, and that is the whole sign-in step, with no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Claude asks you to sign in to Elaichi, and from then on it can work in WarpStream as you.

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

Yes. Once WarpStream 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 WarpStream once and every client picks it up, with the same restrictions and the same audit log behind each one.

What can an AI agent actually do with my WarpStream account?

Through this connector an agent can create, look up, update and delete WarpStream virtual clusters, change a cluster's configuration or tier, and manage the credentials, API keys and access rules that control who can reach each one. It can also list consumer groups, check quotas, and create or remove pipelines and their configurations. Because WarpStream exposes a lot of actions, short concrete asks such as "list the credentials on the payments cluster" get better results than long paragraphs.

Does connecting WarpStream give the AI access to every cluster in my account?

Only what the WarpStream API key you connected can already reach. The agent works inside that person's own WarpStream access, and Elaichi can narrow it further by team or by action, but it can never widen it. If the key cannot touch a cluster, neither can any AI client using it.

Can my team share one WarpStream connection?

Yes. One person connects WarpStream in Elaichi and shares the connection with a team, and nobody else ever sees or handles the API key. Each teammate still signs in to Elaichi as themselves, so every cluster change or credential created through the shared WarpStream connection is logged under the name of the person who asked for it.

Can I stop an agent from deleting or changing things in WarpStream?

Yes. In Elaichi you restrict actions one by one, so you can allow listing WarpStream clusters, credentials and pipelines while blocking deletion or configuration changes. A blocked action is never shown to Claude, ChatGPT, Cursor or any other client at all, so no prompt, however worded, can reach it.

What happens to a WarpStream connection when someone leaves?

Offboarding that person in Elaichi ends their access to WarpStream through every client at once. If they had shared a WarpStream connection with a team, it keeps working for everyone else. And if you ever want WarpStream gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client in the same moment.

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

Yes. WarpStream 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 WarpStream?

Yes. Both let Claude, ChatGPT or Cursor use WarpStream. 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 WarpStream call.

How is Elaichi different from Composio for WarpStream?

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 WarpStream: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put WarpStream in front of your team

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

Connect WarpStream Talk to us
Works with
Claude ChatGPT Cursor 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.