
Queue Pilot
- LarsCowe/queue-pilot
Queue Pilot is a MCP server that inspects RabbitMQ and Kafka messages with JSON Schema validation for developers.
About
Queue Pilot is a local stdio MCP server for developers running event-driven backends who need their coding agent to peek at RabbitMQ or Kafka traffic with schema guardrails. Install runs through npx with a mandatory --schemas directory so every message inspection can be checked against your contract files. RabbitMQ connects through the management API URL and credentials; Kafka is selectable with --broker kafka when that is your stack. The workflow suits debugging: trace poison messages, confirm envelope shape, and reason about consumers without leaving the agent thread. It is intermediate complexity because you must supply broker access, schema layout, and understand which broker mode is active. It complements observability dashboards rather than replacing them—think interactive inspection and validation, not long-term metrics storage or autoscaling policies.
- stdio MCP via npx queue-pilot (npm registry, v0.5.1)
- Broker switch: rabbitmq or kafka (default rabbitmq)
- Required --schemas path to a directory of JSON Schema files
- RabbitMQ Management API via RABBITMQ_URL, RABBITMQ_USER, RABBITMQ_PASS
- JSON Schema validation on inspected messages
Queue Pilot by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
claude mcp add --env RABBITMQ_URL=YOUR_RABBITMQ_URL --env RABBITMQ_USER=YOUR_RABBITMQ_USER --env RABBITMQ_PASS=YOUR_RABBITMQ_PASS --env KAFKA_BROKERS=YOUR_KAFKA_BROKERS --env KAFKA_CLIENT_ID=YOUR_KAFKA_CLIENT_ID --env KAFKA_SASL_MECHANISM=YOUR_KAFKA_SASL_MECHANISM --env KAFKA_SASL_USERNAME=YOUR_KAFKA_SASL_USERNAME --env KAFKA_SASL_PASSWORD=YOUR_KAFKA_SASL_PASSWORD queue-pilot -- npx -y queue-pilot filepath stringAdd your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| Package | queue-pilot |
|---|---|
| Transport | STDIO |
| Auth | Required |
| Repository | LarsCowe/queue-pilot ↗ |
What it does
Let your agent inspect RabbitMQ or Kafka queues and validate message payloads against your JSON Schemas during debugging and ops.
Who is it for?
Best when you're operating RabbitMQ or Kafka and want MCP-driven message inspection tied to local JSON Schema files.
Skip if: Greenfield projects with no message broker yet, or teams that only need hosted APM without direct queue access.
What you get
You register Queue Pilot locally so the agent can read broker messages and validate them against your schema directory during incidents.
- Agent-readable queue message snapshots from RabbitMQ or Kafka
- Payload validation results against your JSON Schema set
- Broker-targeted inspection without custom ad-hoc scripts
By the numbers
- Server version 0.5.1 on npm identifier queue-pilot
- 2 broker modes: rabbitmq (default) and kafka
- 1 required CLI argument: --schemas (directory of JSON Schema files)
Recommended MCP Servers
How it compares
Broker inspection MCP with schema validation, not a cloud metrics dashboard or deployment skill.
FAQ
Who is Queue Pilot for?
Developers shipping event-driven APIs or workers who use Claude Code or Cursor and need agent access to RabbitMQ or Kafka plus schema checks.
When should I use Queue Pilot?
Use it in production or staging when debugging stuck consumers, malformed payloads, or schema mismatches on queues you already operate.
How do I add Queue Pilot to my agent?
Add an stdio MCP server running npx queue-pilot with --schemas pointing at your JSON Schema directory, set RABBITMQ_* env vars, and optional --broker kafka.