Using AI with Solace Products

You can use the Model Context Protocol (MCP) server with Solace event brokers and AI plugins to develop applications for your AI-based flows.

Solace Broker MCP Server
Solace Broker MCP Server allows you to monitor and configure event brokers using AI applications that call tools. Instead of using Solace Element Management Protocol (SEMP) calls, Solace Event Broker CLI, or graphical interfaces such as Broker Manager, you can use plain language to monitor and manage Solace event brokers. For more information, see Using Broker MCP Server.
AI plugins
We provide plugins that ground AI coding assistants with Solace product knowledge and design guidance using Solace documentation. You can use them to generate applications that follow our best practices, or as a learning tool to deepen your understanding as you build. For more information, see Using Agent Plugins.

Using Broker MCP Server

Broker MCP Server gives AI applications, Solace Agent Mesh and Claude Code, the ability to monitor and manage your Solace event brokers. Instead of using SEMP calls, admin consoles, or metrics screens yourself, you can ask a question or describe a change in plain language, and your AI assistant queries connected event brokers and acts on them following the operations you allow.

Broker MCP Server provides two types of tools:

  • Read-only tools — Enabled by default and used for monitoring.
  • Write tools — Disabled by default. You must explicitly enable them to configure event brokers.

Broker MCP Server can connect to one or more event brokers. Your AI application interprets your natural language request and decides which MCP Server tools to call. The server runs those tools by sending SEMP requests to the event brokers you configure, and returns the results to your AI application. Because LLMs are non-deterministic and can misread data, draw wrong conclusions, or select the wrong tool, Solace strongly recommends that you always:

  • Review the responses from the Broker MCP Server before you act on them.
  • Confirm that any write or destructive actions are correct before you allow them.
  • Test against a non-production event broker before using Broker MCP Server on an event broker in production.

You can get Solace Broker MCP Server (solace-broker-mcp) from the SolaceProducts/solace-broker-mcp GitHub repository.

For other MCP servers from Solace, see the SolaceProducts/solace-platform-mcp GitHub repository.

Using Agent Plugins

Solace provides plugins that give AI coding assistants, such as Claude Code, the skills and knowledge to help you build event-driven messaging applications quickly. Instead of piecing together API references and design guidance on your own, you describe the application you want, and your AI assistant designs and implements it, following Solace best practices for both application development and topic structure from the start.

You can also use the skills in the plugins as a learning tool. Get them from the SolaceProducts/agent-plugins GitHub repository. Because the skills in each plugin ground their design decisions and generated patterns in Solace documentation, you deepen your understanding of our products as you build.

These skills run on LLMs, which are non-deterministic and may change over time. Generated code can vary between runs and may be incorrect, insecure, incomplete, or unsuitable for your environment. You are responsible for reviewing, testing, and validating all generated code before use, especially before deploying to production.

AI plugins are currently available for building messaging applications with the following APIs: