artemis-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ARTEMIS_MODE | No | read-only or admin | read-only |
| ARTEMIS_USER | Yes | Broker user for both AMQP and Jolokia | |
| ARTEMIS_AMQP_URL | Yes | AMQP endpoint, e.g., amqp://host:5672 or amqps://host:5671 | |
| ARTEMIS_PASSWORD | Yes | Broker password | |
| ARTEMIS_LOG_LEVEL | No | error, warn, info, or debug | info |
| ARTEMIS_MAX_BROWSE | No | Hard cap on messages returned by browse_messages/consume_message | 200 |
| ARTEMIS_BROKER_NAME | No | Broker name used in the management ObjectName | 0.0.0.0 |
| ARTEMIS_JOLOKIA_URL | Yes | Jolokia endpoint, e.g., http://host:8161/console/jolokia | |
| ARTEMIS_AMQP_TIMEOUT_MS | No | AMQP connection and operation timeout | 15000 |
| ARTEMIS_JOLOKIA_TIMEOUT_MS | No | Jolokia request timeout | 10000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| browse_messagesA | Read messages from a queue without removing them. |
| list_queuesA | List the names of all queues on the broker. |
| list_addressesA | List the names of all addresses on the broker. |
| get_queue_infoC | Return the configuration of a queue. |
| get_queue_statsB | Return runtime counters for a queue. |
| get_broker_overviewA | Return high level broker status and counts. |
| list_consumersA | List the consumers currently attached to the broker. |
| list_connectionsA | List the connections currently open to the broker. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.