Build on the AI-agent fabric
KubeMQ's A2A and MCP gateways are live the moment it runs — connect an MCP host, register an agent, or drive it from an LLM.
KubeMQ must be running — see the Quickstart (steps 1–2 get you there; instant if it's already up).
KubeMQ's Agent-to-Agent (A2A) and Model Context Protocol (MCP) gateways are live
the moment KubeMQ runs — both ship on by default on the shared HTTP server, port 9090.
Unlike the seven wire-protocol connectors under Replace your messaging
stack, which are opt-in and need an enable flag, there's
no CONNECTORS_*_ENABLE step here: start the broker and the fabric is already listening.
Three ways in
Connect an MCP host
Point Claude Desktop, Cursor, or any MCP host at KubeMQ's built-in MCP endpoint, list the tools, and drive messaging from your LLM.
Register your first agent
Wrap an existing plain-HTTP service as a KubeMQ A2A agent with zero SDK — register, discover by capability, and invoke it.
Drive KubeMQ from an LLM
Orchestrate durable messaging and A2A agents from an LLM over MCP in a single session — the end-to-end fabric in action.
What the fabric gives you
Both doors open into the same fabric, not two bolted-together servers:
- A shared discovery and registry layer so callers find agents by capability
- Streaming responses over Server-Sent Events (SSE) for long-running work
- An HA agent registry replicated to every cluster node so a node failure doesn't strand an agent
- Guardrails — TTL liveness, request timeouts, and per-agent concurrency caps — that keep a whole agent fleet production-safe rather than a demo
The full picture, including the enterprise envelope and both getting-started guides, lives on KubeMQ Aiway.
Didn't work?
- Nothing answers on
:9090— the fabric is only live while KubeMQ itself is running; confirm withdocker psorkmq status, or work through Quickstart if you haven't started it yet. - Port 9090 not published — if you started KubeMQ with a custom
docker run(or<RunKubeMQ ports={[]} />), make sure9090is exposed. - No license key — a standalone server refuses to boot without one; see Get a license key.
Was this page helpful?
Replace JMS, ActiveMQ, or AMQP 1.0 with KubeMQ
Move JMS, ActiveMQ (Java), or native AMQP 1.0 clients onto KubeMQ's one AMQP 1.0 connector — per-client on-ramps and verification.
Connect an MCP host
Point Claude Desktop, Cursor, or any MCP host at KubeMQ's built-in MCP endpoint, list the tools, and drive messaging from your LLM.