Setting up Event Portal MCP Server with Different AI Assistants

Solace Event Portal MCP Server is a set of tools that brings the full power of Solace Event Portal Designer to your favorite AI tools. By using the Model Context Protocol (MCP), this server exposes specialized tools that allow AI assistants to programmatically design, catalog, explore, extend and update your event-driven system.

In this post, we will explore setting up the Event Portal MCP Server with a few AI coding assistants. Previously, we have looked at using the EP MCP server with Claude Code and Solace Agent Mesh. Here we will look at setting up the EP MCP with Roo, Cline and Gemini CLI.

Why Use These Tools?

• Roo and Cline: These IDE-based agents allow architects and developers to document interactions and model events without ever leaving VS Code. It also enables the extraction of relevant information from the Event Portal like Schema and Topic for use in new development.
• Gemini CLI: Ideal for terminal-focused workflows, providing a fast way to “chat” with your architecture to understand event flows or list application domains. It also allows for elaborate design, extract and build loop directly from the CLI with the information that is inside of Event Portal.
• Claude Desktop: Ideal for less technical stakeholders who are not working in the terminal or IDE but are still leveraging LLMs in their day-to-day work. Claude desktop is a powerful business tool for organizing thoughts, doing research and creating assets from large amounts of information with natural language.

Setup with Roo (VS Code)

Roo utilizes a global configuration to manage its agentic capabilities.

• Open the MCP Servers view in the Roo sidebar and select Edit Global MCP.
• Add the following configuration to your your mcp_settings.json:

  {
    "mcpServers": {
      "solace-event-portal-designer": {
        "command": "uvx",
        "args": [
          "--from", "solace-event-portal-designer-mcp",
          "solace-ep-designer-mcp"
        ],
        "env": {
          "SOLACE_API_TOKEN": "<your_token>",
          "SOLACE_API_BASE_URL": "https://api.solace.cloud"
        }
      }
    }
  }

Setup with Cline (VS Code)

Cline offers project-specific flexibility for interacting with external tools.

• Click the MCP Icon in Cline and select Configure.
• Click Configure MCP Servers to edit the JSON configuration.
• Add solace-event-portal-designer server definition using the same JSON structure as above.
• Restart VS Code after configuration to ensure the connection is established.

Setup with Gemini CLI

The Gemini CLI provides a lightweight terminal interface for interacting with your EP objects.

• Open your global settings at ~/.gemini/settings.json.
• Insert the solace-ep-designer configuration into the mcpServers block:

  {
    "mcpServers": {
      "solace-ep": {
        "command": "uvx",
        "args": ["--from", "solace-event-portal-designer-mcp", "solace-ep-designer-mcp"],
        "env": {
          "SOLACE_API_TOKEN": "your-api-token-here"
        }
      }
    }
  }
  

• Alternatively, run the following command to add it automatically: gemini mcp add solace-ep uvx –args “–from,solace-event-portal-designer-mcp,solace-ep-designer-mcp”.
• Verify the connection by typing /mcp list within the CLI.

Setup with Claude Desktop

Open your Claude Desktop configuration file, which is typically located at:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json
  Add the following JSON block to the mcpServers section of the file. You will need your Solace API token, which can be generated in the Token Management section of the Solace Cloud Console.

    "mcpServers": {
      "solace-event-portal-designer": {
        "command": "uvx",
        "args": [
          "--from", "solace-event-portal-designer-mcp",
          "solace-ep-designer-mcp"
        ],
        "env": {
          "SOLACE_API_TOKEN": "your-api-token-here",
          "SOLACE_API_BASE_URL": "https://api.solace.cloud"
        }
      }
    }
  }
  

• Restart Claude Desktop: Fully quit and restart the application to apply the changes.
• Test the Connection: Open a new chat and ask Claude a question about your architecture, such as: “List my Solace application domains.”
• Check Tools: You should see a hammer icon or notification indicating that Claude is calling the <solace-event-portal-designer

Conclusion

Integrating the Solace Event Portal MCP Server transforms your architecture into a conversational asset, making it easier than ever to manage complex event flows. Whether you are an architect preparing a new feature in your terminal with markdown and wiki documents, a product owner looking at the entire product landscape in a desktop LLM tool or a developer implementing new events in your IDE, bring AI into your EDA workflow with the Solace Event Portal MCP Server. Head over to the Solace Labs GitHub to grab the server and start building today!