Skip to content
RabbitMQ logo

RabbitMQ MCP server

Give your AI assistant 2 tools it can call in RabbitMQ, over one server URL.

RabbitMQ is not a separate install. One Activepieces MCP server exposes it alongside 760+ other apps, behind a single URL.

Tools
2
Works with
Any MCP client
Auth
Custom auth
License
MIT, open source
Updated
September 2026

About the RabbitMQ MCP server

Connect RabbitMQ once in Activepieces and every action it ships becomes a tool your assistant can call, behind the same server URL as the rest of your apps. Your agent reaches RabbitMQ and 760+ other apps over a single connection, on our cloud or a self-hosted install.

Tools

RabbitMQ tools your AI can run

Once connected, your assistant can call any of these RabbitMQ actions by asking in plain language.

  • sendMessageToExchange

    Send a message on a RabbitMQ exchange

    3 fields

  • sendMessageToQueue

    Send a message on a RabbitMQ queue

    2 fields

Triggers

RabbitMQ events your agent can watch

These start a run the moment something happens in RabbitMQ, so work gets picked up on its own.

  • Message Received

    Triggers when a message is received on a RabbitMQ queue

    2 fields

Give your assistant RabbitMQ

Connect RabbitMQ once and every tool above is callable from Claude, Cursor or any MCP client, behind the same server URL as 760+ other apps. Free to start.

RabbitMQ MCP, answered.

No. That is the point of it. One Activepieces server exposes RabbitMQ alongside every other piece you connect, so your client keeps a single connection.

Yes. Activepieces is open source and free to start, and the MCP server is included on every plan, from the free cloud tier to any self-hosted deployment.

Connect RabbitMQ in Activepieces, enable the server under Settings → MCP Server, then paste your server URL into your client config. It authenticates over OAuth on first use.

It can call 2 tools, including sendMessageToExchange, sendMessageToQueue, and chain them with steps in other apps inside the same run.

Connections use OAuth2 with limited scopes and are stored under 256-bit encryption, with no API to read them back, so an agent gets scoped access rather than your keys.