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.
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.
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
Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| Tool | What it does |
|---|---|
| Feature | Description |
| all | Enables all features: StreamNative Cloud, Pulsar, and Kafka tools |
| all-kafka | Enables all Kafka admin and client tools, without Apache Pulsar and StreamNative Cloud tools |
| kafka-admin | Kafka administrative operations (all admin tools) |
| kafka-client | Kafka client operations (produce/consume) |
| kafka-admin-topics | Manage Kafka topics |
| kafka-admin-partitions | Manage Kafka partitions |
| kafka-admin-groups | Manage Kafka consumer groups |
| kafka-admin-schema-registry | Interact with Kafka Schema Registry |
| kafka-admin-connect | Manage Kafka Connect connectors |
| all-pulsar | Enables all Pulsar admin and client tools, without Apache Kafka and StreamNative Cloud tools |
| pulsar-admin | Pulsar administrative operations (all admin tools) |
| pulsar-client | Pulsar client operations (produce/consume) |
| pulsar-admin-brokers | Manage Pulsar brokers |
| pulsar-admin-brokers-status | Check Pulsar broker or proxy status |
| pulsar-admin-broker-stats | Access Pulsar broker statistics |
| pulsar-admin-clusters | Manage Pulsar clusters |
| pulsar-admin-functions-worker | Manage Pulsar Function workers |
| pulsar-admin-namespaces | Manage Pulsar namespaces |
| pulsar-admin-namespace-policy | Configure Pulsar namespace policies |
| pulsar-admin-ns-isolation-policy | Manage namespace isolation policies |
| pulsar-admin-packages | Manage Pulsar packages |
| pulsar-admin-resource-quotas | Configure resource quotas |
| pulsar-admin-schemas | Manage Pulsar schemas |
| pulsar-admin-subscriptions | Manage Pulsar subscriptions |
| pulsar-admin-tenants | Manage Pulsar tenants |
| pulsar-admin-topics | Manage Pulsar topics |
| pulsar-admin-sinks | Manage Pulsar IO sinks |
| pulsar-admin-functions | Manage Pulsar Functions |
| pulsar-admin-sources | Manage Pulsar Sources |
| pulsar-admin-topic-policy | Configure Pulsar topic policies |
| streamnative-cloud | Manage StreamNative Cloud context and check resource logs |
| functions-as-tools | Dynamically exposes deployed Pulsar Functions as invokable MCP tools, with automatic input/output schema handling. |
{
"mcpServers": {
"mcp-streamnative": {
"command": "${PATH_TO_SNMCP}/bin/snmcp",
"args": [
"stdio",
"--organization",
"${STREAMNATIVE_CLOUD_ORGANIZATION_ID}",
"--key-file",
"${STREAMNATIVE_CLOUD_KEY_FILE}"
]
}
}
}From the project documentation. Replace placeholders and example paths before connecting.
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
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Build a programmable telecommunications stack for connecting telephony services with the Internet via a cloud-based utility.
Deterministic, offline FMECA MCP server: failure modes, criticality matrix, mitigations, readiness
All-in-one Feishu/Lark MCP for Claude Code & Codex. 84 tools, 3 auth layers, send-as-user.
Connect any MCP-compatible LLM (Claude, Cursor, Continue) to 9,400+ AI-scored commercial real estate deals and 118,000+ closed comps across the
SendPulse MCP Server implements the Model Context Protocol (MCP) as a remote server operating over Streamable HTTP Transport.