A
amazon-mq/mcp-server-rabbitmq
MCP server for RabbitMQ
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
Install & config
- Copy the command above
- Paste it as one entry under
mcpServersinclaude_desktop_config.json— local servers take command + args (example: clients) - Restart your client
Install command from the repository
pip install amq-mcp-server-rabbitmq
Parsed from the README we fetched on 2026-11-04; we have not executed it.
This is the install method the repository states, not an MCP client config, so no JSON is generated.
Key names differ by client: Clients & CLI
- Source
- collected from the abordage/awesome-mcp list · type: MCP server
- Harvest history
- first seen 2026-11-05 · last seen 2026-11-14 · seen 10× · listed by 10 sources
- Score
- score 1,003 · 10 sources · mcp
- Install
pip install amq-mcp-server-rabbitmq
FAQ (answers come from our records)
How do I install it?
The repository provides this install command:
pip install amq-mcp-server-rabbitmq. It comes from the repository itself; we cannot guarantee it runs as-is in your client.Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
first catalogued 2026-11-05;last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.
# mcp-server-rabbitmq
以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →
A Model Context Protocol (MCP) server for RabbitMQ broker management and operations. It lets AI agents manage RabbitMQ brokers conversationally: multi-broker connections, blue-green migration, health checks, and full observability.
Package: amq-mcp-server-rabbitmq on PyPI · Stack: Python, MCP Python SDK (mcp.server.fastmcp), uv
## Features
31 tools in v4 (enum-based dispatchers), or 61 tools in v3 (one tool per operation) for broker management - connections, queues, exchanges, health checks, observability, and blue-green migration
16 composable skills - topology visualization, dead letter analysis, capacity planning, and more
Multi-broker support - connect multiple brokers simultaneously, switch between them by alias
Startup connection from the environment - set RABBITMQAMQPENDPOINT so the tools work without a connect call, for hosts that respawn the server per session
Mutative tools gated behind --allow-mutative-tools flag (off by default for safety)
Tool groups - load only the tools you need with --tool-groups
Security hardened - SSRF protection, credential stripping, TLS warnings, JWKS HTTPS enforcement
## Versions
The server ships two tool layouts so you can choose your upgrade path:
| Version | Layout | Upgrade impact | Choose it when |
| v3 (3.x) | 61 tools, one per operation (e.g. rabbitmqbrokerlistqueues). All v2.x tool names preserved. | Non-breaking - a drop-in upgrade from v2.x. | You have existing prompts/integrations bound to v2/v3 tool names and want zero churn. |
| v4 (4.x) | 31 enum-based dispatchers (e.g. queues(action="list")), selectable via --tool-groups. | Breaking - tool names change (opt in with --v4). --v1-compat re-registers v3 aliases to ease migration. | You want ~60% fewer tool-description tokens per turn, faster startup, and per-group tool loading (see Why opt in to v4). |
Both are published from this repo. v4 defaults to v3 behavior unless you pass --v4, so installing the latest package never breaks an existing setup on its own. See v4 Mode for the full mapping and the CHANGELOG for the v3 → v4 tool-name table.
## Quick Start
### Install via PyPI
bash
pip install amq-mcp-server-rabbitmq
# or
uv pip install amq-mcp-server-rabbitmq
### Configure in Claude Desktop (v4 mode - recommended)
json
"mcpServers": {
"rabbitmq": {
"command": "uvx",
"args": [
"amq-mcp-server-rabbitmq@latest",
"--v4",
"--allow-mutative-tools"
### Configure in Claude Desktop (v3 mode - legacy, 61 tools)
json
"mcpServers": {
"rabbitmq": {
"command": "uvx",
"args": [
"amq-mcp-server-rabbitmq@latest",
"--allow-mutative-tools"
### Basic Usage
Once configured, the agent can connect to your broker and manage it conversationally:
You: Connect to my RabbitMQ broker at rabbitmq.example.com with user admin
You: List all queues and show me which ones have messages backing up
You: Create a dead letter exchange and bind it to the orders queue
## v4 Mode
v4 consolidates the 61 individual v3 tools into 31 enum-based dispatchers (29 consolidated groups plus the 2 standalone mutative tools below), reducing context window pressure while preserving full functionality. Each consolidated tool accepts an action parameter to select the operation.
Package: amq-mcp-server-rabbitmq on PyPI · Stack: Python, MCP Python SDK (mcp.server.fastmcp), uv
## Features
31 tools in v4 (enum-based dispatchers), or 61 tools in v3 (one tool per operation) for broker management - connections, queues, exchanges, health checks, observability, and blue-green migration
16 composable skills - topology visualization, dead letter analysis, capacity planning, and more
Multi-broker support - connect multiple brokers simultaneously, switch between them by alias
Startup connection from the environment - set RABBITMQAMQPENDPOINT so the tools work without a connect call, for hosts that respawn the server per session
Mutative tools gated behind --allow-mutative-tools flag (off by default for safety)
Tool groups - load only the tools you need with --tool-groups
Security hardened - SSRF protection, credential stripping, TLS warnings, JWKS HTTPS enforcement
## Versions
The server ships two tool layouts so you can choose your upgrade path:
| Version | Layout | Upgrade impact | Choose it when |
| v3 (3.x) | 61 tools, one per operation (e.g. rabbitmqbrokerlistqueues). All v2.x tool names preserved. | Non-breaking - a drop-in upgrade from v2.x. | You have existing prompts/integrations bound to v2/v3 tool names and want zero churn. |
| v4 (4.x) | 31 enum-based dispatchers (e.g. queues(action="list")), selectable via --tool-groups. | Breaking - tool names change (opt in with --v4). --v1-compat re-registers v3 aliases to ease migration. | You want ~60% fewer tool-description tokens per turn, faster startup, and per-group tool loading (see Why opt in to v4). |
Both are published from this repo. v4 defaults to v3 behavior unless you pass --v4, so installing the latest package never breaks an existing setup on its own. See v4 Mode for the full mapping and the CHANGELOG for the v3 → v4 tool-name table.
## Quick Start
### Install via PyPI
bash
pip install amq-mcp-server-rabbitmq
# or
uv pip install amq-mcp-server-rabbitmq
### Configure in Claude Desktop (v4 mode - recommended)
json
"mcpServers": {
"rabbitmq": {
"command": "uvx",
"args": [
"amq-mcp-server-rabbitmq@latest",
"--v4",
"--allow-mutative-tools"
### Configure in Claude Desktop (v3 mode - legacy, 61 tools)
json
"mcpServers": {
"rabbitmq": {
"command": "uvx",
"args": [
"amq-mcp-server-rabbitmq@latest",
"--allow-mutative-tools"
### Basic Usage
Once configured, the agent can connect to your broker and manage it conversationally:
You: Connect to my RabbitMQ broker at rabbitmq.example.com with user admin
You: List all queues and show me which ones have messages backing up
You: Create a dead letter exchange and bind it to the orders queue
## v4 Mode
v4 consolidates the 61 individual v3 tools into 31 enum-based dispatchers (29 consolidated groups plus the 2 standalone mutative tools below), reducing context window pressure while preserving full functionality. Each consolidated tool accepts an action parameter to select the operation.
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/amazon-mq-mcp-server-rabbitmq/)
- Source
- awesome · https://github.com/amazon-mq/mcp-server-rabbitmq
- Browse by field
- MCP servers
- Listed by
- 10 independent sources
- added
- today
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.