The read and write split is what makes this safe to expose to an agent: the read tool only accepts read operations and their parameters, and in read-only mode the write tool is never registered at all, so there is nothing to call by accident. Binding the session to a cluster is an explicit step — until you do, cluster-specific tools refuse with a context error rather than guessing.
A messaging-platform server for StreamNative Cloud, Apache Kafka and Apache Pulsar. It covers admin and client operations for both stacks, and can connect either through a StreamNative Cloud service account or directly to an external cluster.
- kafka_admin_topics_read and kafka_admin_topics_write — list topics, read one topic's configuration and metadata; create and delete topics
- kafka_admin_groups_read and kafka_admin_groups_write — consumer group inspection and management
- kafka_admin_connect_read and kafka_admin_connect_write — Kafka Connect connectors
- pulsar_admin_topic_read and pulsar_admin_topic_write — list, stats, lookup, internal stats, compaction and offload status; create, delete, unload, terminate, compact and offload
- pulsar_admin_tenant_read, pulsar_admin_cluster_read, pulsar_admin_brokers_read, pulsar_admin_schema_read and their write counterparts — tenants, clusters, brokers and schemas
- pulsar_admin_sources_read, pulsar_admin_sinks_read, pulsar_admin_package_read and their write counterparts — connectors and packages
- sncloud_context_available_clusters, sncloud_context_use_cluster, sncloud_context_reset, sncloud_context_whoami — see which clusters the session can bind to, bind one, reset, and check the logged-in service account
- sncloud_logs — logs for Pulsar functions, sources, sinks and Kafka Connect connectors in the bound cluster
- sncloud_resources_apply and sncloud_resources_delete — apply and remove cloud resources
- Read-only mode: the write half of every pair is simply not registered
For StreamNative Cloud: an organization, an instance and cluster, and a service account key file with the admin role — passed as --organization and --key-file. For an external cluster, skip the account and use --use-external-kafka with bootstrap servers and SASL settings, or --use-external-pulsar with the web service URL and a token. Install with Homebrew from the streamnative tap, the streamnative/snmcp Docker image, a Helm chart, or a release binary. Runs as stdio or SSE.
One command plus a key — brew install streamnative/streamnative/snmcp, then supply credentials