Ask Your Cluster Anything: The WarpStream MCP Server

I typed one sentence into Cursor: “Is anything wrong with my WarpStream clusters?”

Fifteen seconds later, the AI had checked all 36 clusters and surfaced three issues I didn't know about:

• A cluster silently approaching its partition limit
• An Agent running pipelines alongside Kafka operations
• A consumer group with a rebalance timeout short enough to trigger infinite rebalancing

That's what WarpStream's MCP Server makes possible. It's a Model Context Protocol integration that connects AI assistants like Claude, Cursor, and Windsurf directly to your WarpStream clusters, so you can query cluster health, search event logs, inspect ACL decisions, and explore topics without leaving your IDE.

What Is MCP, and Why Does It Matter for Kafka Data Infrastructure?

The Model Context Protocol is an open standard that lets AI assistants call external tools and data sources on your behalf. Instead of copy-pasting log snippets into a chat window and hoping the AI can make sense of them, MCP lets the AI query your systems directly with the right context, in real time.

For a data streaming platform, this is a natural fit. The questions operators ask most often – "Is anything broken right now?", "Who denied that ACL operation?", "How many errors has my pipeline thrown in the last hour?" – are exactly the kind of structured queries that map cleanly onto a tool-based interface. The WarpStream MCP server makes those queries available that any MCP-compatible AI can call.

What You Can Do

The MCP server exposes a set of tools that cover the most common operational workflows:

These are just the highlights. The MCP Server exposes 30+ tools covering cluster configuration, consumer groups, ACLs, pipelines, and more. See the full list in the MCP Server documentation.

<span class="codeinline">events_query</span> is the most powerful of the bunch. It runs queries across Agent logs, ACL logs, pipeline logs, and data lake events using the WarpStream query language, and it's where most real debugging questions get answered. 

<span class="codeinline">diagnostics_status</span> is the second most powerful tool. It returns a snapshot of your cluster's health – active issues with severity levels, failing checks, and cost optimization suggestions – the same data surfaces you'd find in the Diagnostics section of the Console, but now queryable by your AI assistant as part of answering a broader question. If you ask, "Is anything wrong with my cluster right now?", this is the tool doing the heavy lifting.

<span class="codeinline">list_topics</span> is worth noting, too: it includes recently-deleted topics, which is useful when you're investigating something that's no longer there. 

Everything else, from cluster discovery to Diagnostics to events configuration, is handled by the supporting tools the table above maps out.

A few examples of what you can now ask your AI assistant directly:

• "By how much are my consumer group falling behind?"
• "Did anything change in my cluster in the last 24 hours?"
• "Which principal has been hitting ACL denials this morning?"
• "Is my pipeline throwing errors, and if so, from which stage?"

The AI handles the query construction. You just ask the question.

Under the Hood

The MCP server is available at <span class="codeinline">https://console.warpstream.com/mcp</span> and uses standard HTTP transport, so it works with any MCP-compatible client. Authentication uses WarpStream API keys passed via HTTP headers, which are the same keys you already use to interact with the platform.

API keys generated from the MCP setup page are read-only and scoped to the specific workspaces you select, so there's no risk of an AI assistant accidentally modifying anything. If you manage multiple workspaces, you can grant access to all of them using workspace-scoped headers in a single configuration, rather than maintaining separate setups per workspace.

Setup takes about two minutes. Navigate to the MCP section in the Console, select your workspace(s), and click Generate Configuration. The Console produces a ready-to-paste configuration snippet for whichever client you're using.

For Cursor, that looks like:

{
  "mcpServers": {
    "warpstream": {
      "url": "https://console.warpstream.com/api/v1/mcp",
      "headers": {
        "warpstream-api-key": ""
      }
    },
    "warpstream-docs": {
      "url":"https://docs.warpstream.com/warpstream/~gitbook/mcp"
    }
  }
}

‍

Claude Desktop, Windsurf, and Claude Code (via CLI) are supported out of the box as well.

Built on the Same Foundation as Events

If you've been using WarpStream's Events feature, the MCP server will feel immediately familiar. The <span class="codeinline">events_query</span> tool uses the same pipe-separated query language:

from topic "" | time 1h | filter data.log_level == "error" | fields @kafka_ts, data.message | sort @kafka_ts desc | limit 50

‍

The <span class="codeinline">events_query</span> tool requires Events to be enabled on your virtual cluster, which is a separate step from connecting the MCP server. If you're already using Events for observability, you're halfway there. If you're not using Events yet, this is a good reason to take them for a spin.

Why This Matters

Streaming infrastructure is operationally complex. Agents, topics, ACLs, pipelines, and schema registry all have their own failure modes, and when something goes wrong, the last thing you want is to remember the exact query syntax for pulling ACL denial events from the last 30 minutes.

The MCP server doesn't replace understanding your infrastructure, but it does reduce the friction between having a question and getting an answer, which is most of what debugging actually involves.

We think of this as a natural extension of the work we've done with Events and Diagnostics. It’s not a replacement for those features or tools, but a new way to access them that fits into how engineers are increasingly working.

That opening wasn't hypothetical. The WarpStream team runs the MCP server against our own staging environments across AWS, GCP, and Azure. The partition limit issue above, the consumer group rebalance timeout, the embedded pipeline conflict – we caught them this way. This is how we debug now.

This is also not a static release. We'll keep expanding the MCP server's capabilities as we identify new opportunities, and as customers tell us what's most useful to them.

Getting Started

The WarpStream MCP works with common dev environments: Cursor, Claude, VS Code, and others. Quick-start deep links are provided for Cursor and VS Code. For everything else, getting started is a quick copy-and-paste.

The MCP server is available now for all WarpStream accounts. You'll need at least one virtual cluster and admin access to your workspace to generate an API key. Check out the MCP Server documentation to get started.