mcp -activemq
MCP Server for interacting with ActiveMQ
claude mcp add --transport stdio amazon-mq-mcp-server-activemq java -jar PATH-TO-JAR-FILE \ --env JAVA_HOME="Path to the Java installation (optional if java is in PATH)" \ --env JAVA_OPTS="Optional JVM options (e.g., -Xmx, -Dconfig.field=value)"
How to use
This MCP server provides an interface to manage an ActiveMQ broker via AI agents using the Model Context Protocol. It wraps the JMS Messaging APIs of ActiveMQ for sending messages to topics and queues, and exposes admin capabilities through Jolokia for inspecting the status of topics and queues (note: CORS must be enabled in Jolokia configuration to access these admin endpoints). The server communicates with the agent through standard input/output and talks to the ActiveMQ broker over OpenWire. To use the tools, deploy the MCP server jar and configure it in your MCP client so your agent can invoke: sending a message to a topic, sending a message to a queue, and querying runtime status for topics or queues. Ensure Jolokia is reachable and properly secured if you intend to inspect broker state from the AI agent. The 2 core tool actions are: Send message to a topic, and Send message to a queue. Additionally, you can Inspect the status of a topic or a queue (with Jolokia CORS enabled).
How to install
Prerequisites:
- Java Runtime Environment (JRE) or JDK
- Maven for building the MCP server from source
Step-by-step installation:
- Ensure Java and Maven are installed and available in your PATH.
- Obtain the MCP server source code (clone or download).
- Build the MCP server: mvn clean install This will produce a jar file under the target directory.
- Locate the generated jar file in the target folder, for example target/mcp-activemq-<version>.jar.
- Add the MCP client configuration to your agent’s MCP config as shown below, pointing to the generated jar file:
"mcp-activemq":{ "command": "java", "args":[ "-jar", "PATH-TO-JAR-FILE" ] }
- Ensure your environment is ready to run the server (adjust JAVA_HOME or JAVA_OPTS if necessary) and start the MCP server through the MCP framework.
Additional notes
Notes and tips:
- You must enable Cross-Origin Resource Sharing (CORS) for Jolokia if you plan to inspect broker status from a web UI or an AI agent running in a different origin.
- The server uses OpenWire to communicate with ActiveMQ; ensure network access to the broker from the host running the MCP server.
- If you are integrating with AWS Amazon MQ (ActiveMQ), verify compatibility of the broker version with the client libraries used by the MCP server.
- Manage credentials and access control for Jolokia and the MCP server according to your security posture; avoid exposing Jolokia endpoints publicly.
- The path PATH-TO-JAR-FILE in the configuration must point to the built jar, typically found in the target directory after mvn clean install.
- For debugging, inspect logs produced by the MCP server during startup and operation to verify proper connection to ActiveMQ and Jolokia, and to ensure the agent can invoke the provided tools.
