mcp-server-activemq

Provides an MCP server (stdio transport) that wraps ActiveMQ JMS messaging operations as MCP tools, and uses Jolokia for admin-level inspection of topics/queues. Clients run it locally by compiling a Java jar and configuring the MCP client to launch the jar.

Evaluated Apr 04, 2026 (16d ago)

Repo ↗ Messaging mcp activemq jms jolokia stdio java messaging agent-tools

⚙ Agent Friendliness

/ 100

Can an agent use this?

🔒 Security

/ 100

Is it safe for agents?

⚡ Reliability

/ 100

Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality

Documentation

Error Messages

Auth Simplicity

Rate Limits

🔒 Security

TLS Enforcement

Auth Strength

Scope Granularity

Dep. Hygiene

Secret Handling

The supplied README does not describe authentication, TLS enforcement, or how credentials are handled for ActiveMQ/Jolokia. It explicitly notes CORS must be enabled for Jolokia status inspection, which can be risky if allowed origins/headers are not tightly restricted. No details are provided about secure defaults (e.g., TLS, authz) or logging/secret redaction.

⚡ Reliability

Uptime/SLA

Version Stability

Breaking Changes

Error Recovery

Use Cases

• Send messages to an ActiveMQ topic via an AI agent
• Send messages to an ActiveMQ queue via an AI agent
• Inspect topic status via Jolokia (requires CORS enabled per README)
• Inspect queue status via Jolokia (requires CORS enabled per README)

Not For

• Production-grade operational use without verifying Jolokia security/configuration
• Environments where running arbitrary local Java processes is not acceptable
• Use cases needing a REST/HTTP API for messaging/admin operations

Interface

REST API

GraphQL

gRPC

MCP Server

Yes

SDK

Webhooks

Authentication

OAuth: No Scopes: No

No authentication mechanism is described for the MCP server in the README. ActiveMQ/Jolokia authentication is presumably configured out-of-band, but details are not provided in the supplied content.

Pricing

Free tier: No

Requires CC: No

No pricing information provided (open-source project implied by Apache-2.0 license, but no cost details in README excerpt).

Agent Metadata

Pagination

none

Idempotent

False

Retry Guidance

Not documented

Known Gotchas

⚠ Topic/queue inspection via Jolokia requires enabling CORS in Jolokia configuration (per README), which can introduce security exposure if misconfigured.
⚠ The README indicates users must build locally (mvn clean install) and configure the MCP client to run the resulting jar; agent deployments may need operational setup beyond simple installation.

Alternatives

Use ActiveMQ directly via JMS client libraries (Java) Use Spring/JMS integration for application-to-broker messaging Build/extend an MCP server with a documented HTTP-facing broker proxy layer rather than Jolokia directly Use existing cloud messaging integrations (e.g., managed brokers) with supported APIs/SDKs

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for mcp-server-activemq.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

API endpoint ↗ Agent guide ↗ Report inaccuracy

Scores are editorial opinions as of 2026-04-04.