SwiftMQ MCP Server

A local, read-only MCP server for SwiftMQ router networks. You start it on your own machine from an AI client (Claude, ChatGPT/Codex, GitHub Copilot, …). It connects with your SwiftMQ credentials via the CLI Admin API to a router, and from there it sees every router in that router network.

• Read-only: nothing can be created, changed or deleted, and message contents are not accessible.
• sys$authentication, sys$mgmt and sys$timer are never accessed. Passwords in the management tree are redacted.
• Transport: stdio (the client starts the server as a child process).
• Supported: SwiftMQ 13.x Community (CE), Universal (UR) and High Availability (HA) Edition, including UR's extension swiftlets (xt$jmsbridge, xt$amqpbridge, xt$javamail, xt$replicator). The edition is detected per router from its release (get_router_info shows it), so a network may mix editions.

Status: feature-complete for SwiftMQ 13.x. Tested against single CE and UR routers, an HA router pair and a 3-router CE network. An optional remote mode is a possible next step; see tasks/todo.md.

Tools

Area	Tool	What it shows
Connection	connection_info	Connection URL, user, state (incl. last error), available routers, selected router
	list_routers	Routers currently available in the router network
	select_router	Sets the default router for the following calls
Queues	list_queues	Active queues with messagecount, rates, totals, latency, and delta since the previous call; glob filter
	find_queue	Searches all routers for queues matching a pattern
	get_queue	One queue: usage, configuration (regular/clustered/composite incl. bindings), receivers/senders/browsers
Topics	list_topics	Topics with active and durable subscriber counts
	get_topic	One topic: subscribers and durable subscribers with backlog
	list_durable_subscribers	Durable subscribers with backlog (messages waiting), largest first
Routing	list_routing_connections	Active router-to-router connections
	get_routing_table	Destinations and dynamic routes
	get_routing_config	Listeners, connectors, static routes, filters (passwords redacted)
	network_topology	Graph of the whole network, plus issues (connector without connection, one-way links, unavailable routers)
Network	list_network_connections	All connections with owning swiftlet and throughput
	network_summary	Connections and throughput per swiftlet
Router	get_router_memory	Free/total/used memory of one router, or of all routers
	get_router_info	Release, OS, startup time, smart tree setting, memory, available swiftlets
Overview	network_health	Dead letter queue, unroutable, store-and-forward backlogs, fullest queues, memory, routing issues
Browse	list_swiftlets	Available management areas of a router
	browse_context	Any context of the management tree (properties + children), for everything without a dedicated tool
	change_context	Sets the current context for browse_context (like cc, with relative paths and ..)

Every tool takes an optional router. Without it, the tool uses the selected router, or the only available one. All tools are marked read-only.

Consumer details (receivers, senders, browsers) are only visible when the router runs with use-smart-tree="false" on the <router> element in routerconfig.xml. Otherwise the tools say so and give this hint.

Requirements

• Java 21+
• A SwiftMQ 13.x router reachable from your machine (default smqp://host:4001)
• A SwiftMQ user with admin access to the management tree. Recommended: a dedicated read-only user, see Read-only SwiftMQ user. Once connected, the server can reach every router connected to

... View full README on GitHub