Queue Pilot

Queue Pilot runs locally from a Node.js package published to the npm registry: queue-pilot version 0.5.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx — the usual command is npx -y queue-pilot@0.5.1. It reads these environment variables: RABBITMQ_URL, RABBITMQ_USER (secret), RABBITMQ_PASS (secret), KAFKA_BROKERS, KAFKA_CLIENT_ID, KAFKA_SASL_MECHANISM, KAFKA_SASL_USERNAME (secret) and KAFKA_SASL_PASSWORD (secret); set them in the client's configuration for this server. Required arguments: --schemas.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "queue-pilot": {
      "command": "npx",
      "args": [
        "-y",
        "queue-pilot@0.5.1"
      ],
      "env": {
        "RABBITMQ_URL": "<value>",
        "RABBITMQ_USER": "<secret>",
        "RABBITMQ_PASS": "<secret>",
        "KAFKA_BROKERS": "<value>",
        "KAFKA_CLIENT_ID": "<value>",
        "KAFKA_SASL_MECHANISM": "<value>",
        "KAFKA_SASL_USERNAME": "<secret>",
        "KAFKA_SASL_PASSWORD": "<secret>"
      }
    }
  }
}

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect