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
One command plus a key — rabbitmq-mcp-server, then supply credentials