Back to MCP Servers
🧩

Queue Pilot MCP Server

API key required

MCP server for RabbitMQ and Kafka message inspection with JSON Schema validation

To add Queue Pilot to Claude, run the install command below or copy the ready-made config for Claude Code, Claude Desktop, Cursor and VS Code further down. Restart your client after adding it and its tools show up in your next conversation. It needs 8 environment variables, listed below.

DevTools

Install

npx -y queue-pilot@0.5.1

Environment variables

RABBITMQ_URLSet in your MCP config
RABBITMQ_USERSet in your MCP config
RABBITMQ_PASSSet in your MCP config
KAFKA_BROKERSSet in your MCP config
KAFKA_CLIENT_IDSet in your MCP config
KAFKA_SASL_MECHANISMSet in your MCP config
KAFKA_SASL_USERNAMESet in your MCP config
KAFKA_SASL_PASSWORDSet in your MCP config

Install with your client

Terminal
claude mcp add queue-pilot --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> -- npx -y queue-pilot@0.5.1

Run this in a terminal to add the server to Claude Code.

What this does

Queue Pilot exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.

Requirements

This server needs the following environment variables to be set before it can run:

RABBITMQ_URL
RABBITMQ_USER
RABBITMQ_PASS
KAFKA_BROKERS
KAFKA_CLIENT_ID
KAFKA_SASL_MECHANISM
KAFKA_SASL_USERNAME
KAFKA_SASL_PASSWORD

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

Frequently asked questions

How do I install Queue Pilot?

Run the Claude Code command in the install section to add Queue Pilot to Claude Code, or copy the ready-made config for your client from the install section on this page. Restart your client afterwards and the tools appear in your next conversation.

Which clients work with Queue Pilot?

This page carries setup and config for Claude Code, Claude Desktop, Cursor and VS Code. Any other MCP client that accepts a standard server config can connect to Queue Pilot as well.

Does Queue Pilot need an API key?

Yes. Before it can run, set these environment variables: RABBITMQ_URL, RABBITMQ_USER, RABBITMQ_PASS, KAFKA_BROKERS, KAFKA_CLIENT_ID, KAFKA_SASL_MECHANISM, KAFKA_SASL_USERNAME, KAFKA_SASL_PASSWORD. They go in the env block of your MCP config.

Imported from the Official MCP Registry. The details above come from the registry entry; the maker can claim this listing to correct them, add docs, and see its traffic.

Is this your MCP server?

Claim this listing to see its traffic, fix details yourself, and skip the review queue on future updates.

Listed on clauderules.net

Add this badge to your README

Show visitors this server is listed in the ClaudeRules directory. The badge links straight to this listing.

Markdown
[![Listed on clauderules.net](https://clauderules.net/api/badge/io-github-larscowe-queue-pilot)](https://clauderules.net/mcp/io-github-larscowe-queue-pilot)
HTML
<a href="https://clauderules.net/mcp/io-github-larscowe-queue-pilot" target="_blank" rel="noopener noreferrer"><img src="https://clauderules.net/api/badge/io-github-larscowe-queue-pilot" alt="Listed on clauderules.net" /></a>