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.
-
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.
58 tools
How to connect
How to connect WarpStream to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect WarpStream once
-
Open Connections, choose Add connection, and pick WarpStream.
-
Optionally set Share with to give a team access, then press Connect.
-
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.
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 WarpStream to 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.
Connect WarpStream to 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.
Connect WarpStream to 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 WarpStream 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 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.”
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.
No tools match your search.
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 clientsClaude
ChatGPT
Cursor
Copy the endpoint
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
ElaichiToolsToolboxes
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
ElaichiToolboxesShared 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
ElaichiConnectionsAudit 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 logLaunching 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 Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch virtual clusters
WarpStream
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
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
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%
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 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.
Put WarpStream in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.