streamnative

The StreamNative MCP Server provides a standard interface to access StreamNative Cloud resources, along with Apache Kafka and Apache Pulsar services, following the Model Context Protocol. This server enables large language models (LLMs) and AI agents to discover and operate on StreamNative Cloud clusters, Kafka topics, schemas, connectors, and Pulsar resources, all through a consistent MCP interface. You can connect using different backends (StreamNative Cloud, external Kafka, or external Pulsar) and choose between stdio or SSE (Server-Sent Events) endpoints depending on your deployment needs. Use the built-in context management features to switch between StreamNative Cloud contexts or interact directly with external messaging systems as required.

Prerequisites:

• Git
• Go (for building from source, if you prefer compiling)
• Docker (for the docker-based deployment approach)
• Access to StreamNative Cloud (if you plan to use StreamNative Cloud authentication)

Installation options:

1. Homebrew (macOS/Linux)

   • brew tap streamnative/streamnative
   • brew install streamnative/streamnative/snmcp

2. Docker Image

   • docker pull streamnative/snmcp
   • Run with appropriate environment variables, e.g. SNMCP_ORGANIZATION and SNMCP_KEY_FILE

3. From Github Release

   • Visit https://github.com/streamnative/streamnative-mcp-server/releases to download the latest binary

4. From Source (Go)

   • git clone https://github.com/streamnative/streamnative-mcp-server.git
   • cd streamnative-mcp-server
   • go mod tidy
   • go mod download
   • make

Example: running the Go binary directly after building

• ./snmcp stdio --organization <org> --key-file /path/to/key.json

Prerequisites for building from source:

• Go tooling configured on your system
• Git
• Network access to download dependencies

Tips and common considerations:

• When using external Kafka or Pulsar, ensure the correct bootstrap URLs and credentials are provided (e.g., --kafka-bootstrap-servers, --kafka-auth-*, --pulsar-web-service-url).
• For SSE with multi-session Pulsar mode, you can enable per-user sessions by using --multi-session-pulsar and related flags; this requires external Pulsar mode and is not available in stdio mode.
• If you deploy via Docker, you can mount your key file and pass organization details using environment variables (e.g., SNMCP_ORGANIZATION and SNMCP_KEY_FILE).
• Review the usage options in the CLI help to understand available commands and flags (stdio vs sse, and external resource options).
• When using the Helm chart or Kubernetes deployment, refer to charts/snmcp/README.md for installation details specific to Kubernetes.