NATS MCP by sinadarbouy
sinadarbouyLABSCO SUMMARY
One job, done from the assistant: getting a message onto the broker.
This is a narrow server and says so - the operation it documents is publishing to a queue or exchange. That covers the case that comes up most while developing against a broker: triggering the consumer you are actually working on, without stopping to write a throwaway producer.
What it is
A Go implementation of an MCP server for RabbitMQ. What it documents is the publish side: putting a message onto a queue or an exchange over the protocol, rather than through a client library you have to write.
What you get
- A message published to a RabbitMQ queue or exchange
Requirements
A running RabbitMQ instance the server can reach, and the Go toolchain - the repository ships source, and the binary is built from it.
Setup effort
Build from source — git clone https://github.com/maiconjobim/rabbitmq-mcp-go.git
USE CASES
01
Triggering a consumer you are in the middle of writing
Put a message on the queue the consumer listens to and watch it run, instead of building a producer for a one-off test.
02
Checking where an exchange actually routes
Publish to the exchange and see which bindings pick the message up, rather than reading the topology and hoping.
03
Replaying a payload someone pasted into the chat
Take the message body out of the conversation and publish it as it stands, no reformatting step in between.
BEFORE YOU INSTALL
What to know first
Requires
- Go 1.24.3 or later
- A reachable RabbitMQ broker — its AMQP address goes in RABBITMQ_URL
Where it runs
All 3 documented clients run the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
TERMINAL
git clone https://github.com/maiconjobim/rabbitmq-mcp-go.git
cd rabbitmq-mcp-go
go mod download
go build ./cmd/...MCP Clients
Claude Desktop, Cursor, Any MCP client
JSON
{
"mcpServers": {
"rabbitmq": {
"command": "<YOUR_PATH_TO_RABBITMQ_MCP_GO>",
"env": {
"RABBITMQ_URL": "amqp://guest:guest@localhost:5672/"
}
}
}
}go build ./cmd/... writes a binary named rabbitmq-mcp-go (after cmd/rabbitmq-mcp-go) into the repository folder; the README's own config calls it rabbitmq-mcp-server, a name no build or release produces. Put the full path of rabbitmq-mcp-go here. Prebuilt rabbitmq-mcp-go binaries for macOS, Linux and Windows are also attached to the project's GitHub releases. RABBITMQ_URL is your broker's AMQP address.
