{"id":"amazon-mq-mcp-server-activemq","name":"mcp-server-activemq","homepage":null,"repo_url":"https://github.com/amazon-mq/mcp-server-activemq","category":"messaging","subcategories":[],"tags":["mcp","activemq","jms","jolokia","stdio","java","messaging","agent-tools"],"what_it_does":"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.","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"],"best_when":null,"avoid_when":null,"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"],"af_score":32.8,"security_score":30.2,"reliability_score":16.2,"package_type":"mcp_server","discovery_source":["github"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T19:50:15.329264+00:00","interface":{"has_rest_api":false,"has_graphql":false,"has_grpc":false,"has_mcp_server":true,"mcp_server_url":null,"has_sdk":false,"sdk_languages":["Java"],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":[],"oauth":false,"scopes":false,"notes":"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":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"No pricing information provided (open-source project implied by Apache-2.0 license, but no cost details in README excerpt)."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":32.8,"security_score":30.2,"reliability_score":16.2,"mcp_server_quality":55.0,"documentation_accuracy":45.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":50.0,"rate_limit_clarity":0.0,"tls_enforcement":40.0,"auth_strength":20.0,"scope_granularity":20.0,"dependency_hygiene":35.0,"secret_handling":40.0,"security_notes":"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.","uptime_documented":0.0,"version_stability":25.0,"breaking_changes_history":20.0,"error_recovery":20.0,"idempotency_support":"false","idempotency_notes":"The README describes sending messages and inspecting status, but does not mention idempotency controls (e.g., message IDs/deduplication) or safe retry semantics for send operations.","pagination_style":"none","retry_guidance_documented":false,"known_agent_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."]}}