Skip to main content
Glama
RabbitMQ MCP Server

RabbitMQ MCP Server

by sobue-code

RabbitMQ MCP Server

MCP сервер для работы с RabbitMQ с полной поддержкой SSL/CA сертификатов.

Репозиторий: https://github.com/sobue-code/rabbitmq_mcp

Возможности

  • Полная поддержка SSL/TLS с CA сертификатами

  • Управление очередями (создание, удаление, очистка)

  • Управление exchanges (создание, удаление)

  • Привязка очередей к exchanges

  • Публикация сообщений

  • Чтение сообщений из очередей

  • Проверка статуса соединения

Related MCP server: rabbitmq-mcp

Установка

Вариант 1: Из GitHub (рекомендуется)

Добавьте в конфигурацию MCP (~/.config/opencode/opencode.json или .mcp.json в проекте):

{
  "mcpServers": {
    "rabbitmq": {
      "command": "uvx",
      "args": [
        "--from",
        "git+https://github.com/sobue-code/rabbitmq_mcp.git",
        "rabbitmq-mcp-altqa"
      ],
      "env": {
        "RABBITMQ_HOST": "your-rabbitmq-host.com",
        "RABBITMQ_PORT": "5671",
        "RABBITMQ_USER": "your-username",
        "RABBITMQ_PASSWORD": "your-password",
        "RABBITMQ_VHOST": "your-vhost",
        "RABBITMQ_USE_SSL": "true",
        "RABBITMQ_CA_CERT": "/path/to/your/ca_cert.pem"
      }
    }
  }
}

Вариант 2: Локальная установка (для разработки)

# Клонировать репозиторий
git clone https://github.com/sobue-code/rabbitmq_mcp.git
cd rabbitmq_mcp

# Установить зависимости
uv sync

Конфигурация для локальной установки:

{
  "mcpServers": {
    "rabbitmq": {
      "command": "uv",
      "args": [
        "run",
        "--directory",
        "/path/to/rabbitmq_mcp",
        "rabbitmq-mcp-altqa"
      ],
      "env": {
        "RABBITMQ_HOST": "your-rabbitmq-host.com",
        "RABBITMQ_PORT": "5671",
        "RABBITMQ_USER": "your-username",
        "RABBITMQ_PASSWORD": "your-password",
        "RABBITMQ_VHOST": "your-vhost",
        "RABBITMQ_USE_SSL": "true",
        "RABBITMQ_CA_CERT": "/path/to/your/ca_cert.pem"
      }
    }
  }
}

Переменные окружения

Переменная

Описание

По умолчанию

RABBITMQ_HOST

Хост RabbitMQ

localhost

RABBITMQ_PORT

Порт

5672

RABBITMQ_USER

Имя пользователя

guest

RABBITMQ_PASSWORD

Пароль

guest

RABBITMQ_VHOST

Виртуальный хост

/

RABBITMQ_USE_SSL

Использовать SSL (true/false)

false

RABBITMQ_CA_CERT

Путь к CA сертификату

(нет)

RABBITMQ_HEARTBEAT

Интервал heartbeat (сек)

3600

RABBITMQ_SOCKET_TIMEOUT

Таймаут сокета (сек)

5

Доступные инструменты

Управление соединением

  • rabbitmq_connect — Подключиться к RabbitMQ

  • rabbitmq_disconnect — Отключиться

  • rabbitmq_status — Проверить статус соединения

Очереди

  • rabbitmq_declare_queue — Создать очередь (quorum по умолчанию)

  • rabbitmq_delete_queue — Удалить очередь

  • rabbitmq_purge_queue — Очистить очередь

  • rabbitmq_queue_message_count — Количество сообщений

  • rabbitmq_get_message — Получить сообщение

Exchanges

  • rabbitmq_declare_exchange — Создать exchange

  • rabbitmq_delete_exchange — Удалить exchange

Связи

  • rabbitmq_bind_queue — Привязать очередь к exchange

  • rabbitmq_unbind_queue — Отвязать очередь

Публикация

  • rabbitmq_publish — Опубликовать в exchange

  • rabbitmq_publish_to_queue — Опубликовать напрямую в очередь

Примеры использования

Подключение

Вызови rabbitmq_connect

Проверка статуса

Проверь статус соединения через rabbitmq_status

Создание очереди

Создай quorum очередь "my-queue" через rabbitmq_declare_queue

Публикация сообщения

Опубликуй сообщение {"task": "test"} в exchange "" с routing key "my-queue"

Получение сообщения

Получи сообщение из очереди "my-queue" через rabbitmq_get_message

Разработка

# Клонировать и установить
git clone https://github.com/sobue-code/rabbitmq_mcp.git
cd rabbitmq_mcp
uv sync

# Тестирование сервера
echo '{"jsonrpc":"2.0","method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"test","version":"1.0"}},"id":1}' | uv run rabbitmq-mcp-altqa

Лицензия

Apache-2.0

Available Tools

16 tools
rabbitmq_bind_queueB

Bind a queue to an exchange with a routing key.

Inputs: queue_name (required), routing_key (required), exchange_name (required).

rabbitmq_connectA

Connect to RabbitMQ broker using environment variables. Set RABBITMQ_HOST, RABBITMQ_PORT, RABBITMQ_USER, RABBITMQ_PASSWORD, RABBITMQ_VHOST, RABBITMQ_USE_SSL, RABBITMQ_CA_CERT before calling.

Inputs: no named parameters.

rabbitmq_declare_exchangeC

Declare a new exchange.

Inputs: exchange_name (required), durable, exchange_type.

rabbitmq_declare_queueB

Declare a new queue. Creates quorum queue by default.

Inputs: queue_name (required), durable, exclusive, queue_type, +1 more.

rabbitmq_delete_exchangeC

Delete an exchange.

Inputs: exchange_name (required), if_unused.

rabbitmq_delete_queueB

Delete a queue from the vhost.

Inputs: queue_name (required), if_empty, if_unused.

rabbitmq_disconnectB

Disconnect from RabbitMQ broker.

Inputs: no named parameters.

rabbitmq_get_messageA

Get a single message from a queue (non-destructive peek, or with ack).

Inputs: queue_name (required), auto_ack.

rabbitmq_list_exchangesA

List all exchanges in the connected vhost using Management API.

Inputs: no named parameters.

rabbitmq_list_queuesA

List all queues in the connected vhost using Management API.

Inputs: no named parameters.

rabbitmq_publishB

Publish a message to an exchange with a routing key.

Inputs: message (required), routing_key (required), exchange_name (required), content_type.

rabbitmq_publish_to_queueA

Publish a message directly to a queue (using default exchange).

Inputs: message (required), queue_name (required), content_type.

rabbitmq_purge_queueB

Remove all messages from a queue.

Inputs: queue_name (required).

rabbitmq_queue_message_countC

Get the number of messages in a queue.

Inputs: queue_name (required).

rabbitmq_statusC

Check connection status to RabbitMQ broker.

Inputs: no named parameters.

rabbitmq_unbind_queueA

Unbind a queue from an exchange.

Inputs: queue_name (required), routing_key (required), exchange_name (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.3/5.0

    Scored across 16 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: connect/status/disconnect manage connection, queue/exchange operations are separate, publish vs publish_to_queue are clearly differentiated by target (exchange vs default exchange), and get_message vs queue_message_count serve different purposes. No two tools appear to do the same thing.

    Naming Consistency4/5

    The naming follows a consistent rabbitmq_<verb>_<noun> pattern for most tools (e.g., list_queues, declare_queue, delete_queue). Minor deviations exist: 'rabbitmq_status' uses a noun instead of a verb phrase, and 'rabbitmq_queue_message_count' is an awkward noun-heavy construction rather than a verb-first name. Overall the pattern is predictable and readable.

    Tool Count4/5

    16 tools is slightly above the typical well-scoped range of 3-15, but the breadth is justified by covering connection management, queue and exchange lifecycle, bindings, publishing, and message retrieval. It does not feel bloated or redundant, given the full RabbitMQ management surface.

    Completeness4/5

    The tool surface covers core RabbitMQ operations: connection handling, queue/exchange CRUD, bindings, publishing, and message inspection. Minor gaps exist, such as no list_bindings or get_exchange tool, but agents can still perform most common workflows. No severe missing operations that would cause failures.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      D
      maintenance
      An MCP server for RabbitMQ that exposes the RabbitMQ HTTP API as tools, enabling natural language interaction with RabbitMQ management.
      100
      166 npm
      1
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      An MCP server with HTTP/stdio support, a web admin panel for managing services, capabilities, and user permissions with Bearer token authentication, enabling relay and access control for MCP tools.
      -