A Model Context Protocol (MCP) server for integrating AI agents with StreamNative Cloud resources and Apache Kafka/Pulsar messaging systems.

StreamNative MCP Server provides a standard interface for LLMs (Large Language Models) and AI agents to interact with StreamNative Cloud services, Apache Kafka, and Apache Pulsar. This implementation follows the Model Context Protocol specification, enabling AI applications to access messaging services through a standardized interface.

• StreamNative Cloud Integration:
  • Connect to StreamNative Cloud resources with authentication
  • Switch to clusters available in your organization
  • Describe the status of clusters resources
• Apache Kafka Support: Interact with Apache Kafka resources including:
  • Kafka Admin operations (topics, partitions, consumer groups)
  • Schema Registry operations
  • Kafka Connect operations (*)
  • Kafka Client operations (producers, consumers)
• Apache Pulsar Support: Interact with Apache Pulsar resources including:
  • Pulsar Admin operations (topics, namespaces, tenants, schemas, etc.)
  • Pulsar Client operations (producers, consumers)
  • Functions, Sources, and Sinks management
• Multiple Connection Options:
  • Connect to StreamNative Cloud with service account authentication
  • Connect directly to external Apache Kafka clusters
  • Connect directly to external Apache Pulsar clusters

*: The Kafka Connect operations are only tested and verified on StreamNative Cloud.

The easiest way to install streamnative-mcp-server is using Homebrew:

# Add the tap repository brew tap streamnative/streamnative # Install streamnative-mcp-server brew install streamnative/streamnative/snmcp

StreamNative MCP Server releases the Docker Image to streamnative/snmcp, and it can be used to run both stdio server and sse server via docker command.

# Pull image from Docker Hub docker pull streamnative/snmcp 

Visit https://github.com/streamnative/streamnative-mcp-server/releases to get the latest binary of StreamNative MCP Server.

# Clone the repository git clone https://github.com/streamnative/streamnative-mcp-server.git cd streamnative-mcp-server go mod tidy go mod download # Build the binary make

If you want to access to your StreamNative Cloud, you will need to have following resources ready:

1. Access to StreamNative Cloud.
2. StreamNative Cloud Organization
3. StreamNative Cloud instance and cluster
4. Service Account with admin role
5. Download the Service Account Key file

# Start MCP server with StreamNative Cloud authentication bin/snmcp stdio --organization my-org --key-file /path/to/key-file.json # Start MCP server with StreamNative Cloud authentication and pre-configured context # When --pulsar-instance and --pulsar-cluster are provided, context management tools are disabled bin/snmcp stdio --organization my-org --key-file /path/to/key-file.json --pulsar-instance my-instance --pulsar-cluster my-cluster # Start MCP server with external Kafka bin/snmcp stdio --use-external-kafka --kafka-bootstrap-servers localhost:9092 --kafka-auth-type SASL_SSL --kafka-auth-mechanism PLAIN --kafka-auth-user user --kafka-auth-pass pass --kafka-use-tls --kafka-schema-registry-url https://sr.local --kafka-schema-registry-auth-user user --kafka-schema-registry-auth-pass pass # Start MCP server with external Pulsar snmcp stdio --use-external-pulsar --pulsar-web-service-url http://pulsar.example.com:8080 bin/snmcp stdio --use-external-pulsar --pulsar-web-service-url http://pulsar.example.com:8080 --pulsar-token "xxx" # Start MCP server with SSE by docker with StreamNative Cloud authentication docker run -i --rm -e SNMCP_ORGANIZATION=my-org -e SNMCP_KEY_FILE=/key.json -v /path/to/key-file.json:/key.json -p 9090:9090 streamnative/snmcp stdio

# Start MCP server with SSE and StreamNative Cloud authentication snmcp sse --http-addr :9090 --http-path /mcp --organization my-org --key-file /path/to/key-file.json # Start MCP server with SSE and pre-configured StreamNative Cloud context # When --pulsar-instance and --pulsar-cluster are provided, context management tools are disabled snmcp sse --http-addr :9090 --http-path /mcp --organization my-org --key-file /path/to/key-file.json --pulsar-instance my-instance --pulsar-cluster my-cluster # Start MCP server with SSE and external Kafka snmcp sse --http-addr :9090 --http-path /mcp --use-external-kafka --kafka-bootstrap-servers localhost:9092 # Start MCP server with SSE and external Pulsar snmcp sse --http-addr :9090 --http-path /mcp --use-external-pulsar --pulsar-web-service-url http://pulsar.example.com:8080 # Start MCP server with SSE by docker with StreamNative Cloud authentication docker run -i --rm -e SNMCP_ORGANIZATION=my-org -e SNMCP_KEY_FILE=/key.json -v /path/to/key-file.json:/key.json -p 9090:9090 streamnative/snmcp sse

Usage: snmcp [command] Available Commands: stdio Start stdio server help Help about any command Flags: --audience string The audience identifier for the API server (default "https://api.streamnative.cloud") --client-id string The client ID to use for authorization grants (default "AJYEdHWi9EFekEaUXkPWA2MqQ3lq1NrI") --config-dir string If present, the config directory to use --enable-command-logging When enabled, the server will log all command requests and responses to the log file --features strings Features to enable, defaults to `all` -h, --help help for snmcp --issuer string The OAuth 2.0 issuer endpoint (default "https://auth.streamnative.cloud/") --kafka-auth-mechanism string The auth mechanism to use for Kafka --kafka-auth-pass string The auth password to use for Kafka --kafka-auth-type string The auth type to use for Kafka --kafka-auth-user string The auth user to use for Kafka --kafka-bootstrap-servers string The bootstrap servers to use for Kafka --kafka-ca-file string The CA file to use for Kafka --kafka-client-cert-file string The client certificate file to use for Kafka --kafka-client-key-file string The client key file to use for Kafka --kafka-schema-registry-auth-pass string The auth password to use for the schema registry --kafka-schema-registry-auth-user string The auth user to use for the schema registry --kafka-schema-registry-bearer-token string The bearer token to use for the schema registry --kafka-schema-registry-url string The schema registry URL to use for Kafka --key-file string The key file to use for authentication to StreamNative Cloud --log-file string Path to log file --organization string The organization to use for the API server --proxy-location string The proxy location to use for the API server (default "https://proxy.streamnative.cloud") --pulsar-auth-params string The auth params to use for Pulsar --pulsar-auth-plugin string The auth plugin to use for Pulsar --pulsar-token string The token to use for Pulsar --pulsar-cluster string The default cluster to use for the API server --pulsar-instance string The default instance to use for the API server --pulsar-tls-allow-insecure-connection The TLS allow insecure connection to use for Pulsar --pulsar-tls-cert-file string The TLS cert file to use for Pulsar --pulsar-tls-enable-hostname-verification The TLS enable hostname verification to use for Pulsar (default true) --pulsar-tls-key-file string The TLS key file to use for Pulsar --pulsar-tls-trust-certs-file-path string The TLS trust certs file path to use for Pulsar --pulsar-web-service-url string The web service URL to use for Pulsar -r, --read-only Read-only mode --server string The server to connect to (default "https://api.streamnative.cloud") --use-external-kafka Use external Kafka --use-external-pulsar Use external Pulsar --http-addr string HTTP server address (default ":9090") --http-path string HTTP server path for SSE endpoint (default "/mcp") -v, --version version for snmcp 

The StreamNative MCP Server supports enabling or disabling specific groups of functionalities via the --features flag. This allows you to control which MCP tools are available to your AI tools. Enabling only the toolsets that you need can help the LLM with tool choice and reduce the context size.

The StreamNative MCP Server allows you to enable or disable specific groups of features using the --features flag. This helps you control which tools are available to your AI agents and can reduce context size for LLMs.

Note: When using --pulsar-instance and --pulsar-cluster flags together, context management tools (sncloud_context_use_cluster) are automatically disabled since the context is pre-configured.

You can combine these features as needed using the --features flag. For example, to enable only Pulsar client features:

# Enable only Pulsar client features bin/snmcp stdio --organization my-org --key-file /path/to/key-file.json --features pulsar-client

You can use the @modelcontextprotocol/inspector tool to inspect and test your MCP server. This is particularly useful for debugging and verifying your server's configuration.

npm install -g @modelcontextprotocol/inspector

# Inspect a stdio server mcp-inspector stdio --command "snmcp stdio --organization my-org --key-file /path/to/key-file.json" # Inspect an SSE server mcp-inspector sse --url "http://localhost:9090/mcp"

The inspector provides a web interface where you can:

• View available tools and their schemas
• Test tool invocations
• Monitor server responses
• Debug connection issues

This server can be used with any MCP-compatible client, such as:

• Claude Desktop
• Other AI assistants supporting the MCP protocol
• Custom applications built with MCP client libraries

⚠️ Reminder: Please ensure you have an active paid plan with your LLM provider to fully utilize the MCP server. Without it, you may encounter the error: message will exceed the length limit for this chat.

{ "mcpServers": { "mcp-streamnative": { "command": "${PATH_TO_SNMCP}/bin/snmcp", "args": [ "stdio", "--organization", "${STREAMNATIVE_CLOUD_ORGANIZATION_ID}", "--key-file", "${STREAMNATIVE_CLOUD_KEY_FILE}" ] } } }

Please remember to replace ${PATH_TO_SNMCP} with the actual path to the snmcp binary and ${STREAMNATIVE_CLOUD_ORGANIZATION_ID} and ${STREAMNATIVE_CLOUD_KEY_FILE} with your StreamNative Cloud organization ID and key file path, respectively.

Optionally, you can use docker image to start the stdio server if you have Docker installed.

{ "mcpServers": { "mcp-streamnative": { "command": "docker", "args": [ "run", "-i", "--rm", "-e", "SNMCP_ORGANIZATION", "-e", "SNMCP_KEY_FILE", "-v", "${STREAMNATIVE_CLOUD_KEY_FILE}:/key.json", "streamnative/snmcp", "stdio" ], "env": { "SNMCP_ORGANIZATION": "${STREAMNATIVE_CLOUD_ORGANIZATION_ID}", "SNMCP_KEY_FILE": "/key.json" } } } }

First, install the mcp-proxy tool:

pip install mcp-proxy

Then configure Claude Desktop to use the SSE server:

{ "mcpServers": { "mcp-streamnative-proxy": { "command": "mcp-proxy", "args": [ "http://localhost:9090/mcp/sse" ] } } }

Note: If mcp-proxy is not in your system PATH, you'll need to provide the full path to the executable. For example:

• On macOS: /Library/Frameworks/Python.framework/Versions/3.11/bin/mcp-proxy
• On Linux: /usr/local/bin/mcp-proxy
• On Windows: C:\Python311\Scripts\mcp-proxy.exe

Please remember to replace http://localhost:9090/mcp/sse with the right URL.

The Model Context Protocol (MCP) is an open protocol that standardizes how applications provide context to LLMs. MCP helps build agents and complex workflows on top of LLMs by providing:

• A growing list of pre-built integrations that your LLM can directly plug into
• The flexibility to switch between LLM providers and vendors
• Best practices for securing your data within your infrastructure

For more information, visit modelcontextprotocol.io.

This section describes how to release a new version of snmcp.

1. Generate a tag for the new version (see Versioning, below):

git tag -a v0.0.1 -m "v0.0.1" 

5. Push the tag to the git repository:

git push origin refs/tags/v0.0.1 

The release workflow will:

• build Go binaries for supported platforms
• archive the binaries
• publish a release to the github repository (ref)

This project uses semver semantics.

• Stable: vX.Y.Z
• Pre-release: vX.Y.Z-rc.W
• Snapshot: vX.Y.Z-SNAPSHOT-commit

Licensed under the Apache License Version 2.0: http://www.apache.org/licenses/LICENSE-2.0