Hey Everyone,
On behalf of the team here at Solace, it is my delight to announce the new Solace Broker MCP Server.
Point any MCP-compatible agent, such as Claude Code, Claude Desktop, or Solace Agent Mesh, at it, and it can inspect and operate on your brokers directly, in natural language.
What it gives you:
- 24 read-only monitoring tools: broker and redundancy status, VPNs, queues, clients, bridges, Kafka receivers/senders, REST delivery points, and discard stats.
- 16 write and action tools: create, update, or delete Message VPNs, queues, topic endpoints, and REST delivery points; disconnect clients; clear stats. Off by default behind
enable_write_tools, and destructive tools are flagged so a client can prompt before running them. - Multi-broker support: addressed by alias, so one server instance can front your whole fleet.
- Flexible client auth: dev mode, a static token, or OAuth 2.1/OIDC, with per-tool authorization by OIDC claim.
- Built-in observability: structured, correlated audit logs, plus Prometheus and OpenTelemetry metrics and traces.
Deploy it as a standalone binary, a Docker image, or build it from source with go install. The README covers configuration, authentication setup, and wiring it into Claude Code, Claude Desktop, or Solace Agent Mesh.
Repository (Apache 2.0): GitHub - SolaceProducts/solace-broker-mcp: Production MCP server for the Solace broker · GitHub
Andrea Ross
Senior Manager, Developer and Agent Experience
