
Queue Pilot
Let your agent inspect RabbitMQ or Kafka queues and validate message payloads against your JSON Schemas during debugging and ops.
Overview
Queue Pilot is a MCP server for the Operate phase that inspects RabbitMQ and Kafka messages with JSON Schema validation for developers.
What is this MCP server?
- 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
- 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)
What problem does it solve?
Async bugs are painful when you cannot quickly inspect queue payloads and confirm they match your schemas from inside the agent.
Who is it for?
Indie builders operating RabbitMQ or Kafka who 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 do I get? / Deliverables
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
Recommended MCP Servers
Journey fit
Message-bus inspection is production operations work once async services are live, not initial product scoping. Monitoring is the right shelf for queue depth, payload review, and schema drift checks on brokers you already run.
How it compares
Broker inspection MCP with schema validation, not a cloud metrics dashboard or deployment skill.
Common Questions / 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.