diffusion

This MCP server acts as a bridge to a Diffusion server, exposing a programmable interface to explore topic trees, query time-series, manage topics and views, configure remote servers, and monitor metrics. It supports opening connections to a local or remote Diffusion server, retrieving details about topics, sessions, and system security stores, and performing operations such as creating, updating, and removing topics and topic views. Note that subscribing to topic updates is not supported by this MCP server; it is designed to facilitate exploration, testing, and monitoring in development or training scenarios, with the Diffusion Management Console recommended for subscriptions and live updates. You can connect to a local Diffusion server using default credentials or specify a ws:// URL along with a principal and password, then issue natural language or structured commands like exploring the topic tree, checking server health, or building a topic view or hierarchy for testing. The server is intended to work with Diffusion 6.12 or newer, though it can connect to earlier versions with some feature limitations.

Prerequisites:

• Java 17 or newer installed on the host.
• Access to a Diffusion server (local or remote).

Installation steps:

1. Ensure Java is available on the PATH and JAVA_HOME is set to a Java 17 JDK.
2. Download the latest shaded MCP server JAR from the project releases (diffusion-mcp-server-<version>.jar).
3. Run the MCP server:
   • Using STDIO transport (single local user): java -jar diffusion-mcp-server-1.0.0.jar
   • If you need HTTP transport, configure the server accordingly (e.g., enabling HTTP transport via command-line options or properties as per Diffusion MCP Server documentation).
4. (Optional) Set environment variables as needed, for example JAVA_HOME, or any Diffusion connection properties if supported by your build.
5. Verify startup by checking the console logs and connecting a Diffusion client (e.g., Claude Desktop or a custom client) to the running MCP server.

Note: If you plan to use HTTPS/HTTP transports, follow the Diffusion MCP Server guidance for keystore generation and transport configuration, and ensure the keystore is accessible to the JVM when launching the JAR.

Tips and common considerations:

• The MCP server is designed for exploration and monitoring; avoid using a production Diffusion server with writable operations unless you understand the permissions and impact.
• Ensure the Diffusion server you connect to supports the features you plan to use (e.g., Metrics Collectors, Alerts) as some capabilities may require newer Diffusion versions.
• When using HTTP transport, secure the transport with TLS/keystore as described in the README and ensure the keystore password is correctly configured.
• If Claude Desktop or another client shows issues with zombie processes, prefer starting the MCP server separately and connect via an STDIO bridge or HTTP transport to avoid shared process lifecycles.
• Remember to back up your Diffusion persistence files before performing destructive operations (create/remove topics, etc.).