StreamNative MCP

StreamNative's MCP server gives an agent both the admin plane and the data plane of a streaming cluster. On the Pulsar side it covers tenants, namespaces, topics, subscriptions, and schemas, and it can produce messages to a topic or consume from one for inspection. On the Kafka side it handles topics, consumer groups, and message production and consumption through the platform's Kafka-compatible protocol, so a mixed estate is reachable through a single connection. It also reaches the StreamNative Cloud control plane: listing organizations, instances, and clusters, managing service accounts and API keys, and inspecting connectors and functions running on the platform. That combination lets an assistant move from noticing that a topic is backing up to reading a sample of the offending messages, without a human switching between a console, a command-line tool, and a throwaway consumer script. It is built for platform and data engineers who operate event streaming as shared infrastructure, and for teams giving support or on-call staff a safer path into cluster internals. Access is scoped through StreamNative service accounts, so the agent only sees the tenants and clusters its credentials permit, and destructive operations such as deleting a topic stay gated by that same model. The server is open source and distributed as a binary and container image for local or remote use.