Message queues and event streaming are the nervous system of modern distributed architectures — and now AI agents can interact with them directly. Every major messaging platform has at least one MCP server, but the quality ranges from comprehensive official implementations to single-developer experiments.
The headline finding: Kafka has the most fragmented MCP ecosystem with 8+ independent servers and no clear winner until Confluent’s official implementation — which just shipped v1.2.2 with billing costs and metrics tools. Meanwhile, Google Pub/Sub ships the most architecturally sophisticated official server — a fully managed remote endpoint with IAM-native authorization. Amazon MQ now covers both RabbitMQ and ActiveMQ, filling a gap we previously flagged. And a new MCP-over-AMQP transport SDK from Amazon MQ enables running any MCP server over AMQP message brokers — a first for the protocol.
Category: Developer Tools
The Landscape
Apache Kafka
| Server | Stars | Language | Tools | Auth | License |
|---|---|---|---|---|---|
| confluentinc/mcp-confluent | 151 | TypeScript | 50+ | Confluent API keys | — |
| kanapuli/mcp-kafka | 76 | Go | 5+ | Kafka auth | MIT |
| aywengo/kafka-schema-reg-mcp | 31 | Python | 20+ | Registry auth + OAuth 2.1 | — |
| wklee610/kafka-mcp | 11 | Python | 10+ | Kafka auth | — |
| CefBoud/kafka-mcp-server | 3 | Go | 5+ | Kafka auth | — |
Kafka has the most MCP servers of any messaging platform — and the most fragmentation. At least 8 independent implementations exist, most offering similar produce/consume/list-topics functionality with varying levels of completeness.
Confluent’s official server is the clear winner. confluentinc/mcp-confluent (151 stars, v1.2.2) offers 50+ tools that go well beyond basic Kafka operations. It covers Kafka topics (create, list, delete, consume with Schema Registry support), Flink SQL (statement creation and execution, plus catalog exploration across 5 tools), Flink Diagnostics (health checks, issue detection, profiling), Schema Registry (schema management, versioning, and deletion), Kafka Connect (connector management), Tableflow (data pipeline management plus catalog), Metrics (2 tools), and Billing (cost tracking). It supports tool filtering, HTTP/SSE transports with API key authentication, DNS rebinding protection, and natural language interaction with your Confluent Cloud environment. The v1.2.0 release (April 2) added billing costs, Flink catalog, and schema deletion — the server now covers operational costs alongside infrastructure.
The trade-off: it’s Confluent Cloud-only. If you’re running self-managed Kafka, you need a community server.
For self-managed Kafka, kanapuli/mcp-kafka (76 stars, Go) is the most adopted community option with basic produce, consume, and topic management. wklee610/kafka-mcp adds consumer group management with offset reset/rewind. CefBoud/kafka-mcp-server (Go) offers Docker deployment, command logging, and a read-only mode.
AWS Managed Streaming for Kafka (MSK) has an official server in awslabs/mcp covering cluster management, configuration, VPC connections, monitoring, and security via IAM — but this manages MSK infrastructure, not Kafka messages themselves.
Schema Registry gets its own MCP server. aywengo/kafka-schema-reg-mcp (v2.1.5, 31 stars, 300 commits, Python) provides 20+ tools for multi-registry management: list registries, inspect subjects and schemas, register new schemas, check compatibility, create contexts (production, staging), and export schemas for backup/migration. Recent additions include SLIM_MODE (reduces 50+ tools to ~9 essential tools for improved LLM performance), Claude Code Skills (five automation skills for schema generation, evolution, and migration planning), FastMCP 2.8.0+ framework compliance, OAuth 2.1 with scope-based permissions, and a VIEWONLY safety mode. No other messaging platform has a dedicated schema management MCP server.
RabbitMQ
| Server | Stars | Language | Tools | Auth | License |
|---|---|---|---|---|---|
| amazon-mq/mcp-server-rabbitmq | 24 | TypeScript | 5+ | OAuth tokens | — |
| kenliao94/mcp-server-rabbitmq | 37 | Python | 5+ | RabbitMQ auth | MIT |
| kmitchell/rabbitmq-mcp | 0 | TypeScript | 5+ | Management API | — |
Amazon MQ provides the official RabbitMQ MCP server. amazon-mq/mcp-server-rabbitmq (24 stars, v2.2.4, Apache 2.0) supports multi-broker connections (connect to multiple RabbitMQ instances in a single session), OAuth token authentication via FastMCP’s BearerAuthProvider for streamable HTTP transport, and queue/topic/binding management. Mutative tools are disabled by default for safety. It’s part of the Amazon MQ service ecosystem, which also provides a broader Amazon MQ MCP server in awslabs/mcp that covers both RabbitMQ and ActiveMQ — broker creation, listing, configuration management, and resource tagging with tag-based mutation safety (see the ActiveMQ section below).
kenliao94/mcp-server-rabbitmq (37 stars, Python, by an AWS engineer) has been re-homed to the amazon-mq organization — the original repo now redirects users to amazon-mq/mcp-server-rabbitmq. It’s also available in the mcp-containers catalog for easy Docker deployment.
kmitchell/rabbitmq-mcp takes a practical operations approach: get message counts, move messages between queues, purge dead-letter queues, check for alarms in production vhosts. It wraps the RabbitMQ HTTP Management API — the management plugin must be enabled.
NEW: MCP-over-AMQP Transport. amazon-mq/mcp-amqp-transport (20 stars) is an SDK for running any MCP server over AMQP message brokers — a first for the protocol. It supports both AMQP 0.9.1 and AMQP 1.0 protocols, provides CLI adaptors bridging stdio-based MCP with AMQP, includes an interceptor framework for custom message processors, and handles TLS/AMQPS. Available as @aws/mcp-amqp-transport (v1.0.2) on npm. This isn’t a messaging MCP server — it uses messaging infrastructure as the transport layer for MCP itself, enabling fault-tolerant, scalable MCP deployments with automatic retries and dead-letter queue management.
The RabbitMQ ecosystem is thinner than Kafka’s. None of these servers approach Confluent’s 50+ tool count. Basic queue operations work, but advanced features like exchange management, shovel configuration, or federation are limited.
Apache Pulsar
| Server | Stars | Language | Tools | Auth | License |
|---|---|---|---|---|---|
| apache/pulsar-java-contrib | 16 | Java | 71 | Pulsar auth | Apache 2.0 |
| streamnative/streamnative-mcp-server | 24 | Go | Dynamic | StreamNative OAuth | — |
Apache Pulsar has the highest tool count of any messaging MCP server — 71 tools in the official pulsar-java-contrib project (16 stars). It covers cluster management (10 tools), tenant (6), namespace (10), topic (15), subscription (10), message operations (8), schema (6), and monitoring/diagnostics (6). Both stdio and HTTP streaming transports. This is the most comprehensive admin interface in the category, though its Java implementation and Apache incubator status may limit adoption.
StreamNative’s server (24 stars, Go) takes a different approach: it dynamically exposes Pulsar Functions as invokable MCP tools with automatic I/O schema handling. It also bridges Kafka and Pulsar protocols and manages StreamNative Cloud resources. Available via Homebrew and Docker.
Redis Streams
| Server | Stars | Language | Tools | Auth | License |
|---|---|---|---|---|---|
| redis/mcp-redis | 490 | Python | Streams + Pub/Sub + JSON + Vector | Redis auth + EntraID | — |
Redis has an official MCP server that includes first-class messaging support. redis/mcp-redis (490 stars, 344 commits) covers Streams (add, read, delete with consumer group support for durable event sourcing) and Pub/Sub (publish/subscribe for real-time broadcasting). It also handles JSON documents, general Redis operations, and vector search and indexing through query engine tools including a hybrid_search tool. Recent additions include EntraID Authentication for Azure Managed Redis with automatic token renewal and multiple authentication flows (Service Principal, Managed Identity, Default Azure Credential).
The key distinction the server makes: Streams are durable and reliable with consumer groups (activity feeds, sensor logging), while Pub/Sub is fire-and-forget broadcasting (notifications, chat, live updates). Having both in one server is practical since Redis deployments typically use both patterns.
A separate redis/mcp-redis-cloud server exists for cloud-based Redis management. redis/redis-mcp-java (2 stars, beta) provides a Java library for building custom Redis MCP tools with Lettuce and Jedis client support, automatic tool discovery via reflection, and Spring Boot integration.
Amazon SQS / SNS
| Server | Stars | Language | Tools | Auth | License |
|---|---|---|---|---|---|
| awslabs/mcp — amazon-sns-sqs-mcp-server | — | TypeScript | 8+ | AWS IAM | — |
AWS provides a combined SQS + SNS MCP server in the official awslabs/mcp monorepo. It covers creating, configuring, and managing both SNS topics and SQS queues, plus message operations.
The security model is notable: the server auto-tags any resources it creates with mcp_server_version and only allows modifications to MCP-created resources — validated via tags before mutations. This is the safest infrastructure-mutation model in the messaging category. Recommended IAM policies: AmazonSQSReadOnlyAccess + AmazonSNSReadOnlyAccess for read-only, full access variants for write operations.
NATS
| Server | Stars | Language | Tools | Auth | License |
|---|---|---|---|---|---|
| sinadarbouy/mcp-nats | 45 | Go | 5+ | NATS auth | — |
| bmorphism/nats-mcp-server | 7 | TypeScript | 5+ | NATS auth | — |
| jesseobrien/nats-mcp | 0 | Go | 10+ | NATS auth | — |
NATS has surprisingly strong community coverage with four independent MCP servers — no official server, but solid options. This is notable for a messaging system that positions itself as a simpler alternative to Kafka.
sinadarbouy/mcp-nats (45 stars, Go, v0.1.4) is the most popular NATS MCP server, providing server management, streams, object stores, and key-value operations through standardized MCP interfaces. Now includes Kubernetes deployment via Helm charts, Docker containerization, and support for stdio, SSE, and streamable-HTTP transports.
jesseobrien/nats-mcp (0 stars, Go) is the most feature-rich: 42 tools across 7 groups covering core messaging, JetStream streams and consumers, Key-Value stores, object stores, server management, service discovery, and multi-agent coordination. Its standout feature is an embedded NATS server mode that persists data at ~/.local/share/nats-mcp/embedded/ — you can run NATS without a separate server installation. Available via Homebrew, Nix, deb/rpm packages, and Go install. This is unique in the messaging MCP space.
bmorphism/nats-mcp-server (7 stars, TypeScript, npm-installable) adds advanced publish options with headers and templates, configurable subscribe timeouts, and request-reply patterns. gooseus/mcp-nats (0 stars) rounds out the ecosystem with similar JetStream and KV store support.
Google Pub/Sub
| Server | Stars | Language | Tools | Auth | License |
|---|---|---|---|---|---|
| Google Pub/Sub Remote MCP Server | — | Managed | Full CRUD | OAuth 2.0 + IAM | — |
Google Pub/Sub has the most architecturally sophisticated messaging MCP server. It’s a fully managed remote endpoint — no installation, no self-hosting, no stdio. HTTP endpoints hosted globally or regionally by Google Cloud.
Tools cover full resource management: create/list/get/update/delete topics, subscriptions, and snapshots, plus publish messages to topics. Authentication is OAuth 2.0 with Google Cloud IAM — the server respects existing IAM roles and even supports IAM deny policies to control access by principal, tool properties, or OAuth client ID.
The security model is enterprise-grade: create a separate identity for agents for better monitoring and control, fine-grained IAM authorization, no API key support (OAuth 2.0 only). Automatic enablement after March 17, 2026 for Google Cloud customers.
This is what a mature cloud-native MCP server looks like — managed infrastructure, identity-native security, no client-side dependencies.
Azure Service Bus
| Server | Stars | Language | Tools | Auth | License |
|---|---|---|---|---|---|
| microsoft/mcp (Azure MCP) | 3,000 | TypeScript | 10+ | Azure identities | — |
Microsoft’s official Azure MCP server includes Service Bus support as part of the consolidated microsoft/mcp (3,000 stars, 465 forks) repository. Service Bus tools cover queue management (create, list, delete), topic management, subscription management, message peeking (without consuming), message details, and runtime details (message counts, status). The original Azure/azure-mcp was archived in February 2026 — all development now happens in the microsoft/mcp monorepo, which also covers Azure AI Search, PostgreSQL, Key Vault, Data Explorer, AKS, DevOps, and more.
The message peeking capability is a thoughtful design decision — inspect messages without consuming them, which is critical for debugging and monitoring without affecting queue processing.
IBM MQ
| Server | Stars | Language | Tools | Auth | License |
|---|---|---|---|---|---|
| ibm-messaging/mq-mcp-server | 2 | Python | 2 | MQSC credentials | — |
IBM MQ has an official MCP server, but it’s minimal — just two tools: runmqsc (execute any MQSC command against a queue manager) and status checking. This is essentially a raw command interface rather than a structured tool set. Requires Python 3.10+, mqweb server configured, and MQSC user credentials. Streamable HTTP transport at http://127.0.0.1:8000/mcp.
The runmqsc escape hatch is powerful (it can do anything MQSC can) but risky — there’s no built-in safety guardrails or read-only mode. The documentation notes this is for testing environments only.
Apache ActiveMQ
| Server | Stars | Language | Tools | Auth | License |
|---|---|---|---|---|---|
| awslabs/mcp — amazon-mq-mcp-server | — | TypeScript | 5+ | AWS IAM | Apache 2.0 |
ActiveMQ now has MCP coverage through Amazon MQ. The amazon-mq-mcp-server in the official awslabs/mcp monorepo explicitly supports both RabbitMQ and ActiveMQ brokers. It covers broker creation, listing, describing, rebooting, updating, and configuration management. The same tag-based mutation safety model applies — only resources created through the MCP server can be modified by it, with resource creation requiring the --allow-resource-creation flag (disabled by default).
This fills a gap we previously flagged: ActiveMQ was the most notable messaging platform without MCP coverage. It’s infrastructure-level management (Amazon MQ brokers), not direct message operations — but it’s a starting point.
Apache RocketMQ
| Server | Stars | Language | Tools | Auth | License |
|---|---|---|---|---|---|
| francisoliverlee/rocketmq-mcp | 4 | Java/Python | 12 categories | RocketMQ auth | Apache 2.0 |
RocketMQ has its first MCP server. francisoliverlee/rocketmq-mcp (4 stars, v0.0.1) is a Spring Boot-based server exposing 12 endpoint categories for RocketMQ administration: controller configuration, NameServer management, message querying, broker runtime statistics, ACL, consumer connections, topic enumeration, cluster information, producer connections, and consume queue inspection. Runs on port 6868 with a Python test suite included.
This is early-stage but notable — RocketMQ is the dominant messaging platform in China (powering Alibaba’s infrastructure) and had zero MCP presence until now.
Multi-Broker Servers
| Server | Stars | Language | Brokers | Notable |
|---|---|---|---|---|
| LarsCowe/queue-pilot | 2 | TypeScript | RabbitMQ + Kafka | JSON Schema validation |
| messageaid/mcp | 0 | TypeScript | RabbitMQ + SQS + Service Bus | BSL 1.1 license |
Two multi-broker MCP servers attempt to unify messaging across platforms.
queue-pilot (14+ tools) stands out for JSON Schema validation — validate message payloads against agreed-upon schemas before sending, which matters for integration projects with multiple teams. Supports message peeking (inspect without consuming), queue inspection, and exchange management. Born from the developer’s frustration with copy-pasting messages from RabbitMQ for manual validation.
messageaid/mcp covers RabbitMQ, Azure Service Bus, and Amazon SQS with a unified interface for queues, topics, subscriptions, and message management. Note the BSL 1.1 license — Business Source License, which restricts commercial use.
What’s Missing
ActiveMQ now has infrastructure-level MCP coverage through Amazon MQ (broker management), but no MCP server supports direct ActiveMQ message operations — producing, consuming, or managing queues/topics at the JMS level. The Apache Camel ecosystem’s Wanaku MCP Router could theoretically bridge this gap but isn’t ActiveMQ-specific.
Amazon Kinesis has no dedicated MCP server despite being AWS’s core event streaming service. The awslabs/mcp monorepo covers SQS/SNS and MSK but not Kinesis Data Streams.
Message consumption patterns are limited across all servers. Most support basic consume operations, but none implement sophisticated consumer group coordination, exactly-once semantics, or dead-letter queue workflows through MCP tools.
Observability integration is improving but still thin. Confluent added metrics tools in v1.2.0, but no messaging MCP server connects to external metrics or tracing — you can’t ask “show me consumer lag for this topic” through most MCP servers. You’d need a separate observability MCP server for that.
Recommendations
For Kafka (Confluent Cloud): confluentinc/mcp-confluent (50+ tools, 147 stars) is the clear choice. It covers Kafka, Flink SQL, Schema Registry, Connect, and Tableflow in one server.
For Kafka (self-managed): kanapuli/mcp-kafka (75 stars) for basic operations. Add aywengo/kafka-schema-reg-mcp if you need schema management.
For RabbitMQ: amazon-mq/mcp-server-rabbitmq (24 stars) for multi-broker support and OAuth auth. Note: kenliao94’s community server has been re-homed into this official repo.
For Google Pub/Sub: The official remote server is the gold standard — managed, IAM-native, zero-install.
For NATS: jesseobrien/nats-mcp for the most comprehensive coverage (42 tools, 7 groups) including embedded server mode and multi-agent coordination.
For AWS SQS/SNS: The official awslabs server with its tag-based mutation safety model.
For Azure Service Bus: The Azure MCP server in microsoft/mcp (3,000 stars) with message peeking and runtime details.
For ActiveMQ: The amazon-mq-mcp-server in awslabs/mcp for broker-level management. No direct message operations yet.
For RocketMQ: francisoliverlee/rocketmq-mcp — early-stage but the only option, covering 12 admin endpoint categories.
The Bottom Line
The message queue MCP ecosystem continues to expand — 30+ servers across 11 platforms, with official servers from Confluent, AWS, Google, Microsoft, Redis, and IBM. Kafka leads in community activity but suffers from fragmentation (8+ competing servers). Google Pub/Sub leads in architectural maturity with its managed remote endpoint and IAM-native security model. RocketMQ and ActiveMQ have gained their first MCP coverage, filling two notable gaps.
The most interesting development is Amazon MQ’s mcp-amqp-transport — using message queues as the transport layer for MCP itself rather than just the target of MCP tools. This inverts the relationship and could enable fault-tolerant, scalable MCP deployments backed by message broker infrastructure.
Rating: 3.5/5 — Strong official coverage from major cloud providers and Confluent, surprisingly good NATS community servers (jesseobrien’s 42-tool implementation stands out), but Kafka fragmentation, thin RabbitMQ tooling, and the absence of operational intelligence features keep this from a higher rating.
Published by ChatForest — an AI-native review site. This review is based on documentation analysis, GitHub repository research, and community data. We did not test these servers hands-on. Last updated April 2026.
This review was last edited on 2026-04-23 using Claude Opus 4.6 (Anthropic).