Contract-first MCP server for RabbitMQ: one typed tool per message contract, safe error recovery.
Rabbit-mcp is an MCP integration. Contract-first MCP server for RabbitMQ: one typed tool per message contract, safe error recovery.
The published nuget package is RabbitMcp.Server, version 3.0.0. Its declared MCP transport is stdio.
The package declares RabbitMcp__Uri (required): AMQP URI of the broker, e.g. amqp://user:pass@localhost:5672/vhost.; RabbitMcp__EnablePublish: true to enable the publish_/request_ tools (off by default).; RabbitMcp__EnableRepublish: true to enable republish_from_error / dead_letter_from_error (off by default).; RabbitMcp__EnableTopology: true to enable declare_exchange / declare_queue (off by default).; RabbitMcp__HumanConfirmation: required (default): changes and replies need the person's OK in the client's dialog, refused when it cannot ask. auto: then the model's own call counts.; RabbitMcp__ManagementUri: RabbitMQ Management API, e.g. http://localhost:15672 (list_queues, contract_consumers).; RabbitMcp__ContractAssemblies: Your [MessageContract] DLLs (";"-separated). Empty: built-in sample contracts.; RabbitMcp__ContractFiles: AsyncAPI files (YAML/JSON) whose messages become contracts (";"-separated)..
The published oci package is ghcr.io/lazogio/rabbit-mcp:3.0.0. Its declared MCP transport is stdio.
The package declares RabbitMcp__Transport (required): stdio for a local client (the image defaults to http).; RabbitMcp__Uri (required): AMQP URI of the broker, reachable from the container..
This package has launch arguments in its registry record. Use the maintainer’s configuration for those arguments rather than launching it with only the package name.
Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.
View the publisher’s registry entry · Project repository. This profile uses version 3.0.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.
Browse related developer tools MCP servers for tools that cover the same kind of work.
| Variable | Description | Required |
|---|---|---|
| RabbitMcp__Uri | AMQP URI of the broker, e.g. amqp://user:pass@localhost:5672/vhost. | Yes |
| RabbitMcp__EnablePublish | true to enable the publish_/request_ tools (off by default). | Check documentation |
| RabbitMcp__EnableRepublish | true to enable republish_from_error / dead_letter_from_error (off by default). | Check documentation |
| RabbitMcp__EnableTopology | true to enable declare_exchange / declare_queue (off by default). | Check documentation |
| RabbitMcp__HumanConfirmation | required (default): changes and replies need the person's OK in the client's dialog, refused when it cannot ask. auto: then the model's own call counts. | Check documentation |
| RabbitMcp__ManagementUri | RabbitMQ Management API, e.g. http://localhost:15672 (list_queues, contract_consumers). | Check documentation |
| RabbitMcp__ContractAssemblies | Your [MessageContract] DLLs (";"-separated). Empty: built-in sample contracts. | Check documentation |
| RabbitMcp__ContractFiles | AsyncAPI files (YAML/JSON) whose messages become contracts (";"-separated). | Check documentation |
Read, search and edit files inside allowed directories with the Model Context Protocol reference Filesystem server.
Retrieve version-aware library documentation and code examples with Context7 MCP, using resolve-library-id and query-docs.
Official MCP server for the Perigon API
<strong>Perforce P4 MCP Server is a Model Context Protocol (MCP) server that integrates with the Perforce P4 version control system. It is built on
Token-bounded repository context for coding agents over MCP.
MCP Server for ComfyUI text to image Workflow