A Model Context Protocol (MCP) server for integrating AI agents with StreamNative Cloud resources and Apache Kafka/Pulsar messaging systems.
A Model Context Protocol (MCP) server for integrating AI agents with StreamNative Cloud resources and Apache Kafka/Pulsar messaging systems. The streamnative mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 4 defined tools rather than through you.
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.
Everything the assistant can do here goes through one of these:
Prerequisites — If you want to access to your StreamNative Cloud, you will need to have following resources ready:Installation — The Installation tool exposed by this serverUsage — The Usage tool exposed by this serverVersioning — The Versioning tool exposed by this server@modelcontextprotocol/inspector on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
You will need 3 environment variables: SNMCP_ORGANIZATION, SNMCP_KEY_FILE, STREAMNATIVE_CLOUD_ORGANIZATION_ID. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
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
This sits in the team communication group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Streamnative's toolset — Prerequisites, Installation, Usage and 1 more — is a fair guide to whether it matches your workflow. It is maintained by streamnative; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Prerequisites | If you want to access to your StreamNative Cloud, you will need to have following resources ready: |
| Installation | The Installation tool exposed by this server. |
| Usage | The Usage tool exposed by this server. |
| Versioning | The Versioning tool exposed by this server. |
{
"mcpServers": {
"mcp-streamnative": {
"command": "${PATH_TO_SNMCP}/bin/snmcp",
"args": [
"stdio",
"--organization",
"${STREAMNATIVE_CLOUD_ORGANIZATION_ID}",
"--key-file",
"${STREAMNATIVE_CLOUD_KEY_FILE}"
]
}
}
}Configuration as documented by the project. Restart the client after saving.
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
| Variable | Description | Required |
|---|---|---|
| SNMCP_ORGANIZATION | Configuration value read at startup. | Optional |
| SNMCP_KEY_FILE | Credential the server authenticates with. | Yes |
| STREAMNATIVE_CLOUD_ORGANIZATION_ID | Configuration value read at startup. | Optional |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.