artemis-mcp-server
This server provides a comprehensive interface for an AI agent to interact with an ActiveMQ Artemis broker via MCP, covering messaging, queue management, monitoring, and administration.
Messaging
Browse messages (
browse_messages) — Read messages from a queue without removing themSend messages (
send_message) (admin) — Send a message to an address or queue with customizable body, headers, and propertiesConsume messages (
consume_message) (admin) — Receive and remove messages from a queue
Queue & Address Management
List queues/addresses (
list_queues,list_addresses) — Retrieve all queue or address names on the brokerGet queue info (
get_queue_info) — View queue configuration (address, routing type, durability, filter, max consumers)Create queue (
create_queue) (admin) — Create a new queue with configurable optionsDelete queue (
delete_queue) (admin + confirm) — Permanently destroy a queue
Monitoring
Get queue stats (
get_queue_stats) — View runtime counters (message count, added, acknowledged, expired, consumers, etc.)Get broker overview (
get_broker_overview) — High-level broker status: version, uptime, memory, connection/queue/address countsList consumers (
list_consumers) — See all consumers currently attached to the brokerList connections (
list_connections) — See all connections currently open to the broker
Administration (admin + confirm required)
Purge queue (
purge_queue) — Remove every message from a queueMove messages (
move_messages) — Move messages from one queue to another, with optional filterDelete messages (
delete_messages) — Remove messages matching a filterRetry DLQ (
retry_dlq) — Resend dead-letter queue messages to their original destination
Note: The server is read-only by default. Write and administrative tools are only exposed when
ARTEMIS_MODE=adminis set. Destructive operations additionally requireconfirm: trueto prevent accidental data loss.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@artemis-mcp-server list all queues on the broker"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
artemis-mcp-server
An MCP server that lets an AI agent work with an ActiveMQ Artemis broker. Messaging runs over AMQP 1.0; queue management, monitoring and administration run over the broker's Jolokia REST endpoint.
The server is read-only by default. Tools that change broker state are only exposed
when ARTEMIS_MODE=admin, and the four destructive operations additionally require an
explicit confirm: true argument so an agent cannot delete data by accident.
Requirements
Node.js 20 or newer
An Artemis broker with an AMQP acceptor and the web console (Jolokia) enabled
Related MCP server: DiceDB MCP
Compatibility
The server uses AMQP 1.0 and the Jolokia REST API rather than a build-specific client, so it is not pinned to one broker release. CI runs the integration suite against these ActiveMQ Artemis versions:
Server | Tested Artemis versions |
0.1.x | 2.30 – 2.44, and the latest |
The server's version is independent of the broker's; there is no need to keep them in step. Older brokers may still work — management calls fall back to legacy Jolokia forms where the API changed — but are unverified, and the server logs a warning at startup when the broker predates the tested range.
Install
Run it directly from a client without installing:
npx artemis-mcp-serverOr install it globally:
npm install -g artemis-mcp-serverConfiguration
Configuration comes entirely from environment variables. Missing or invalid values fail fast at startup with a description of what is wrong.
Variable | Required | Default | Description |
| yes | — | AMQP endpoint, |
| yes | — | Jolokia endpoint, e.g. |
| yes | — | Broker user for both AMQP and Jolokia |
| yes | — | Broker password |
| no |
| Broker name used in the management ObjectName |
| no |
|
|
| no |
| Hard cap on messages returned by |
| no |
| Jolokia request timeout |
| no |
| AMQP connection and operation timeout |
| no |
|
|
See .env.example for a starting point. The password is never written to the logs.
Using it with an MCP client
Claude Code (plugin)
This repository is a Claude Code plugin marketplace. Add it and install the plugin; Claude Code prompts for the broker URL, credentials and mode, then runs the server for you:
/plugin marketplace add k-krawczyk/artemis-mcp-server
/plugin install artemis-mcp-server@artemis-mcpThe password is stored in your system keychain.
Claude Code (CLI)
Without the plugin, register the server directly:
claude mcp add artemis \
--env ARTEMIS_AMQP_URL=amqp://localhost:5672 \
--env ARTEMIS_JOLOKIA_URL=http://localhost:8161/console/jolokia \
--env ARTEMIS_USER=artemis \
--env ARTEMIS_PASSWORD=artemis \
--env ARTEMIS_MODE=admin \
-- npx -y artemis-mcp-serverCodex
In ~/.codex/config.toml:
[mcp_servers.artemis]
command = "npx"
args = ["-y", "artemis-mcp-server"]
env = { ARTEMIS_AMQP_URL = "amqp://localhost:5672", ARTEMIS_JOLOKIA_URL = "http://localhost:8161/console/jolokia", ARTEMIS_USER = "artemis", ARTEMIS_PASSWORD = "artemis", ARTEMIS_MODE = "admin" }Cursor
In .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):
{
"mcpServers": {
"artemis": {
"command": "npx",
"args": ["-y", "artemis-mcp-server"],
"env": {
"ARTEMIS_AMQP_URL": "amqp://localhost:5672",
"ARTEMIS_JOLOKIA_URL": "http://localhost:8161/console/jolokia",
"ARTEMIS_USER": "artemis",
"ARTEMIS_PASSWORD": "artemis",
"ARTEMIS_MODE": "admin"
}
}
}
}VS Code
In .vscode/mcp.json (note the servers key):
{
"servers": {
"artemis": {
"command": "npx",
"args": ["-y", "artemis-mcp-server"],
"env": {
"ARTEMIS_AMQP_URL": "amqp://localhost:5672",
"ARTEMIS_JOLOKIA_URL": "http://localhost:8161/console/jolokia",
"ARTEMIS_USER": "artemis",
"ARTEMIS_PASSWORD": "artemis",
"ARTEMIS_MODE": "admin"
}
}
}
}Claude Desktop and other clients
Most clients accept the same mcpServers shape as Cursor above. Add the artemis entry to
the client's MCP config file (for Claude Desktop, claude_desktop_config.json).
Tools
Tools marked write are hidden unless ARTEMIS_MODE=admin. Tools marked confirm
do nothing unless called with confirm: true.
Messaging
send_message(write) — send one message to an address or queue. Arguments:address,body,bodyType(textorbytes, base64 for bytes),subject?,durable?,ttlMs?,messageId?,properties?.{ "address": "orders", "body": "hello", "properties": { "priority": 9 } }browse_messages— read messages without removing them. Arguments:queue,address?,limit?.consume_message(write) — receive and remove messages. Arguments:queue,address?,count?.
For a named queue on a multicast address, pass both queue and address; the server
addresses it as address::queue.
Management
list_queues— names of all queues.list_addresses— names of all addresses.create_queue(write) — create a queue. Arguments:name,address?,routingType?(anycast/multicast),durable?,filter?,maxConsumers?,autoCreateAddress?.delete_queue(write, confirm) — destroy a queue. Arguments:name,removeConsumers?,autoDeleteAddress?,confirm.get_queue_info— configuration of a queue (address, routing type, durability, filter).
Monitoring
get_queue_stats— runtime counters (message count, added, acknowledged, delivering, scheduled, consumers).get_broker_overview— version, uptime, memory usage, connection/consumer totals and queue/address counts.list_consumers— consumers currently attached.list_connections— open connections.
Administration
purge_queue(write, confirm) — remove every message from a queue.{ "queue": "orders", "confirm": true }move_messages(write, confirm) — move messages to another queue. Arguments:queue,targetQueue,filter?,confirm.delete_messages(write, confirm) — remove messages matching a filter. A filter is required so this cannot become an accidental purge.retry_dlq(write, confirm) — resend a dead-letter queue's messages to their original destination.
Security
The default mode is read-only. Granting write access is an explicit choice through
ARTEMIS_MODE=admin.Destructive operations require
confirm: trueon every call.Credentials are redacted from log output and stack traces are never returned to the client; unexpected failures surface as a generic message and are logged on stderr.
Jolokia is an administrative surface. In production use a dedicated service account with the least privilege it needs, keep the endpoint off the public network, and prefer TLS for both AMQP and the console.
Development
Start a local broker with the console and Jolokia enabled:
docker compose up -dThen:
npm install
npm run build
npm test # unit tests
npm run test:integration # spins up a broker with Testcontainers; needs Dockernpm run lint, npm run typecheck and npm run format:check round out the checks that
CI runs on every push and pull request.
License
MIT
Available Tools
8 toolsbrowse_messagesBrowse messagesARead-only
Read messages from a queue without removing them.
Inputs: queue (required), address, limit. Returns: queue, count, messages
get_broker_overviewGet broker overviewARead-only
Return high level broker status and counts.
Inputs: no named parameters. Returns: version, uptime, started, addressMemoryUsage, +5 more
get_queue_infoGet queue infoCRead-only
Return the configuration of a queue.
Inputs: queue (required). Returns: queue, address, routingType, durable, +3 more
get_queue_statsGet queue statsBRead-only
Return runtime counters for a queue.
Inputs: queue (required). Returns: queue, messageCount, messagesAdded, messagesAcknowledged, +4 more
list_addressesList addressesARead-only
List the names of all addresses on the broker.
Inputs: no named parameters. Returns: count, addresses
list_connectionsList connectionsARead-only
List the connections currently open to the broker.
Inputs: no named parameters. Returns: count, connections
list_consumersList consumersARead-only
List the consumers currently attached to the broker.
Inputs: no named parameters. Returns: count, consumers
list_queuesList queuesARead-only
List the names of all queues on the broker.
Inputs: no named parameters. Returns: count, queues
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 8 tools
Each tool targets a distinct resource or aspect of the broker (messages, overview, queue config, queue stats, addresses, connections, consumers, queues). No overlapping purposes.
All tools follow a consistent verb_noun pattern (e.g., browse_messages, list_queues) with no mixing of conventions.
8 tools is well-scoped for a broker monitoring and management server, covering core read and listing operations without being excessive or sparse.
The tool set covers reading, listing, and status checks well, but lacks write operations such as creating/deleting queues or sending/consuming messages, which are notable gaps for full broker management.
Maintenance
Related MCP Connectors
MCP Server for an Agent Task Marketplace
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
MCP server that lets your AI assistant build and deploy apps, hosting each one at a live URL.
One MCP server for the services your AI needs: memory, files, Microsoft 365, kanban and more.
Related MCP Servers
- AlicenseAqualityDmaintenanceAn MCP server that delivers cryptocurrency sentiment analysis to AI agents.547MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI applications to interact with DiceDB databases.5MIT
- AlicenseAqualityDmaintenanceAn MCP server that enables LLMs to interact with Agent-to-Agent (A2A) protocol compatible agents, allowing for sending messages, tracking tasks, and receiving streaming responses.528MIT
- AlicenseAqualityDmaintenanceMCP server for multi-agent AI systems providing mailbox messaging, A2A task delegation, resource coordination, and a web dashboard.2117 npm1MIT