ActiveMQ MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_connectionsA | List all configured ActiveMQ broker connections |
| connect_brokerB | Connect to an ActiveMQ broker with manual configuration |
| remove_connectionC | Remove an ActiveMQ broker connection |
| test_connectionC | Test connectivity to an ActiveMQ broker |
| connection_infoC | Get detailed information about a specific connection |
| health_statusC | Get health status of all connections |
| list_queuesB | List all queues for a connection |
| queue_infoC | Get queue statistics and information |
| send_messageC | Send a message to a queue or topic |
| consume_messageB | Consume a message from a queue |
| browse_messagesA | Browse messages in a queue without consuming them |
| purge_queueC | Remove all messages from a queue |
| list_topicsC | List all topics for a connection |
| publish_messageC | Publish a message to a topic |
| subscribe_topicC | Subscribe to a topic and receive messages |
| broker_infoC | Get broker statistics and health information |
| broker_statsB | Get comprehensive broker statistics for all connections |
| export_connectionsB | Export connection configurations for backup or migration |
| import_connectionsC | Import connection configurations from backup |
| connect_from_configB | Connect to an ActiveMQ broker using a named configuration from config file |
| show_configA | Show all ActiveMQ broker configurations available in the config file that can be used with connect_from_config |
| system_statusC | Get overall system status and performance metrics |
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 22 tools
Several tools have overlapping purposes that could cause misselection. connect_from_config, connect_broker, and test_connection all involve establishing/testing broker connections. health_status, system_status, broker_info, and broker_stats all report on system/broker health and metrics with unclear boundaries. An agent would struggle to pick the right one.
Most tools follow a verb_noun pattern (list_queues, send_message, purge_queue, export_connections), which is reasonable. However, there are deviations: show_config, system_status, broker_info, and connection_info use different structures, and the mixed usage of 'get' vs 'info' (queue_info vs broker_info) is slightly inconsistent.
At 22 tools, the surface is on the heavy side but not unreasonable for a broker management server. However, there is significant redundancy (broker_info, broker_stats, system_status, health_status overlap heavily; connect_from_config vs connect_broker), suggesting the count could be trimmed to ~14-16 tools without losing capability.
The server covers connect/disconnect, configuration management, queue operations (create... actually missing create_queue/delete_queue), messaging (send/consume/browse/publish/subscribe), and health monitoring. Gaps include queue/topic creation and deletion, message deletion for specific messages, and topic-specific management beyond publish/subscribe. The browsing+purge flow partially covers message lifecycle but lacks fine-grained control.