ct-rabbitmq-mcp-server
A thin CloudThinker wrapper over amq-mcp-server-rabbitmq (the AWS-maintained RabbitMQ MCP server). It makes that server auto-connect from environment variables instead of requiring a runtime initialize_connection tool call, so it drops into CloudThinker's env-injection connection model.
What it does
- Reads
RABBITMQ_*env vars at startup and connects a default broker. - Exposes the broker read tools by default; mutative tools only when
RABBITMQ_ALLOW_MUTATIONS=true. - Never exposes upstream's
initialize_connection/get_guidelinetools. - Talks to the Management HTTP API and serves over stdio.
Run
uvx --from ct-rabbitmq-mcp-server@0.1.0 ct-rabbitmq-mcp-server
Environment
| Var | Required | Default | Purpose |
|---|---|---|---|
RABBITMQ_HOST |
yes | — | broker hostname |
RABBITMQ_USERNAME |
yes | — | management-API user |
RABBITMQ_PASSWORD |
yes | — | management-API password |
RABBITMQ_USE_TLS |
no | false |
true → HTTPS management API |
RABBITMQ_MANAGEMENT_PORT |
no | 15672 (443 if TLS) |
Management HTTP API port |
RABBITMQ_ALLOW_MUTATIONS |
no | false |
true → also register mutative tools |
LOG_LEVEL |
no | info |
mapped to FASTMCP_LOG_LEVEL |
The connecting user needs the RabbitMQ management or administrator tag, and the broker needs the Management plugin (rabbitmq-plugins enable rabbitmq_management).
Tool surface (upstream amq-mcp-server-rabbitmq==2.2.4)
Read (14, always): rabbitmq_broker_list_queues, _list_exchanges, _list_vhosts, _get_queue_info, _get_exchange_info, _list_shovels, _get_shovel_info, _get_cluster_nodes_info, _list_connections, _list_consumers, _list_users, _is_in_alarm, _is_quorum_critical, _get_broker_definition.
Mutative (4, opt-in): rabbitmq_broker_delete_queue, _purge_queue, _delete_exchange, _update_definition.
Implementation notes (read before bumping the upstream pin)
This wrapper depends on two upstream internals, frozen by the exact pin amq-mcp-server-rabbitmq==2.2.4:
import src.*— upstream ships its package under the top-level namesrc.- Private registration methods — we call
RabbitMQModule._RabbitMQModule__register_read_only_tools()(and__register_mutative_tools()) to register the tool sets without the critical/connect tools.
Upstream's RabbitMQAdmin builds its base URL with no port (hardcoded for Amazon MQ on 443). To support self-managed brokers on 15672, the wrapper folds the management port into the hostname (host:port).
When raising the upstream pin, re-verify both internals and the management-URL behavior.
License
Apache-2.0 (matching upstream).
1 maintainer
Metadata
1 maintainer
Release files for ct-rabbitmq-mcp-server 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| ct_rabbitmq_mcp_server-0.1.2.tar.gz | 139.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ct_rabbitmq_mcp_server-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 149.7 kB
Release files / ct_rabbitmq_mcp_server-0.1.2.tar.gz
| Download URL | ct_rabbitmq_mcp_server-0.1.2.tar.gz |
|---|---|
| Size | 139.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2c8c9dac2711f648f98461396051fd9ca8f8108c46a6f2e79900f00ebfb90400
|
|
BLAKE2b-256 checksum How to use checksums |
4b09f52294931965f0aecc8475988975ba999ce5cb6f116e1cbdc65971452ab7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.13 {"installer":{"name":"uv","version":"0.11.13","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / ct_rabbitmq_mcp_server-0.1.2-py3-none-any.whl
| Download URL | ct_rabbitmq_mcp_server-0.1.2-py3-none-any.whl |
|---|---|
| Size | 10.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
85baaa2c4c2c8c18339b897db700e193f9bc8bdaa52be3f1317d3c2c506035ba
|
|
BLAKE2b-256 checksum How to use checksums |
9fa1b422eb8d094f5037818009f9efe65dadb3013b276994666cba73bede7124
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.13 {"installer":{"name":"uv","version":"0.11.13","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for ct-rabbitmq-mcp-server 0.1.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
