RabbitMQ MCP Server

Overview

The RabbitMQ MCP Server bridges AI agents with RabbitMQ's management capabilities through natural language interactions. It exposes the RabbitMQ HTTP Management API as MCP tools, enabling programmatic queue management, message operations, and system monitoring.

Key Features

Available Tools

Quick Reference

Detailed Usage

use_mcp_tool({
  server_name: "rabbitmq",
  tool_name: "get_queue_info",
  arguments: {
    queue_name: "orders",
    vhost: "/"
  }
});

use_mcp_tool({
  server_name: "rabbitmq",
  tool_name: "move_messages",
  arguments: {
    source_queue: "orders",
    destination_queue: "orders-priority",
    message_count: 500,
    vhost: "/"
  }
});

use_mcp_tool({
  server_name: "rabbitmq",
  tool_name: "purge_queue",
  arguments: {
    queue_name: "test-queue",
    vhost: "/"
  }
});

use_mcp_tool({
  server_name: "rabbitmq",
  tool_name: "list_queues",
  arguments: {
    vhost: "/"
  }
});

use_mcp_tool({
  server_name: "rabbitmq",
  tool_name: "check_alarms",
  arguments: {}
});

use_mcp_tool({
  server_name: "rabbitmq",
  tool_name: "get_vhost_status",
  arguments: {
    vhost: "/"
  }
});

Installation

{
  "mcpServers": {
    "rabbitmq": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "rabbitmq-mcp"],
      "env": {
        "RABBITMQ_HOST": "localhost",
        "RABBITMQ_USERNAME": "guest",
        "RABBITMQ_PASSWORD": "guest",
        "RABBITMQ_MANAGEMENT_PORT": "15672",
        "RABBITMQ_PROTOCOL": "http"
      }
    }
  }
}

{
  "mcpServers": {
    "rabbitmq": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "rabbitmq-mcp"],
      "env": {
        "RABBITMQ_HOST": "rabbitmq.example.com",
        "RABBITMQ_USERNAME": "admin",
        "RABBITMQ_PASSWORD": "your-password",
        "RABBITMQ_MANAGEMENT_PORT": "15671",
        "RABBITMQ_PROTOCOL": "https",
        "RABBITMQ_CA_PATH": "/path/to/ca-certificate.crt"
      }
    }
  }
}

Configuration Reference

Required Environment Variables

Optional TLS/HTTPS Variables

Configure TLS for secure connections (inline or file-based):

Inline PEM Strings:

File Paths:

Additional Options:

Enable RabbitMQ Management Plugin

The management plugin must be enabled on your RabbitMQ broker:

# Enable the management plugin
rabbitmq-plugins enable rabbitmq_management

# Verify it's running
curl -u guest:guest http://localhost:15672/api/overview

Common Use Cases

Conditional Queue Operations

Handle queue thresholds automatically:

"Get the message count in the orders queue. If it exceeds 10,000 messages,
move half of them to the orders-overflow queue"

Production Monitoring

Check system health before deployments:

"Check for any triggered alarms in the production RabbitMQ cluster"

Queue Maintenance

Reorganize queues during maintenance windows:

"List all queues in the / vhost and show me which ones have more than
1,000 unacknowledged messages"

Deadletter Recovery

Recover messages from deadletter queues:

"Move 100 messages from the orders.dlq deadletter queue back to the
orders queue for reprocessing"

Best Practices

Security

• Use HTTPS in production with RABBITMQ_PROTOCOL="https"
• Never commit credentials to version control
• Use environment variables or secure secret management
• Create dedicated RabbitMQ users with minimal required permissions
• Enable TLS certificate validation (RABBITMQ_REJECT_UNAUTHORIZED="true")

Monitoring

• Check alarms regularly with check_alarms
• Monitor queue depths to prevent memory issues
• Track unacknowledged message counts
• Set up alerting for abnormal queue growth

Queue Management

• Use descriptive queue names with environment prefixes
• Implement deadletter queues for failed messages
• Test purge_queue operations in non-production first
• Document queue purposes and message schemas

Performance

• Move messages in batches to avoid API rate limits
• Monitor management API response times
• Consider using AMQP directly for high-throughput publishing
• Use the HTTP API (MCP) for monitoring and management operations

Troubleshooting

Connection Refused

If you can't connect to RabbitMQ:

1. Verify the management plugin is enabled: rabbitmq-plugins list
2. Check the management port: default is 15672 (HTTP) or 15671 (HTTPS)
3. Test connectivity: curl http://localhost:15672/api/overview
4. Verify firewall rules allow access to the management port

Authentication Failed

If authentication fails:

1. Verify credentials with curl: curl -u username:password http://localhost:15672/api/overview
2. Check user permissions in RabbitMQ management UI
3. Ensure the user has the monitoring tag for read operations
4. Ensure the user has the administrator tag for write operations

TLS Certificate Errors

If you encounter TLS certificate errors:

1. Verify certificate paths are absolute, not relative
2. Check certificate validity: openssl x509 -in cert.crt -text -noout
3. Ensure CA certificate matches the server certificate chain
4. For self-signed certificates in development, set RABBITMQ_REJECT_UNAUTHORIZED="false"

Command Not Found

If npx or rabbitmq-mcp command is not found:

1. Verify Node.js is installed: node --version
2. Try absolute paths in configuration:
   {
     "command": "/usr/local/bin/node",
     "args": ["/usr/local/bin/rabbitmq-mcp"]
   }
   

3. For Claude Desktop on macOS, use full paths: /usr/local/bin/npx

Sources