kafka-admin can expose kafka_admin_topics_read for inspection and kafka_admin_topics_write for mutations. Read tools are marked as read-only and support safe inspection operations. Write tools are marked as mutating or destructive and can create, update, delete, apply, trigger, produce, or otherwise change resources. In read-only mode, the server omits write or destructive tools where possible and also blocks mutation calls server-side.
StreamNative Cloud tool groups
Organization-level sessions expose StreamNative Cloud tools for cluster discovery and control-plane resources. For workflow details, see Organization-Level Tools.| Feature ID | Tools | Description |
|---|---|---|
streamnative-cloud or cloud | All sncloud_* tools | Enable all StreamNative Cloud organization tool families. |
sncloud_context or sncloud-context | sncloud_context_available_clusters, sncloud_context_use_cluster, sncloud_context_reset | List MCP-enabled clusters, select a cluster, or reset cluster context. The global identity tool sncloud_context_whoami is always available. |
sncloud_byoc or sncloud-byoc | sncloud_resource_catalog, sncloud_resource_schema, sncloud_byoc_read, sncloud_byoc_write | Read or manage BYOC resources such as CloudConnection, CloudEnvironment, Volume, and PoolMember. |
sncloud_identity or sncloud-identity | sncloud_resource_catalog, sncloud_resource_schema, sncloud_identity_read, sncloud_identity_write | Read or manage identity and RBAC resources such as User, ServiceAccount, ServiceAccountBinding, Role, RoleBinding, OIDCProvider, and IdentityPool. |
sncloud_clusters or sncloud-clusters | sncloud_resource_catalog, sncloud_resource_schema, sncloud_clusters_read, sncloud_clusters_write | Read or manage cluster resources such as Instance, PulsarInstance, PulsarCluster, PulsarGateway, and KafkaCluster. |
list and get. Write tools support apply and delete. Write tools accept manifests as JSON strings and support dry_run=true for validation. Use sncloud_resource_catalog to discover supported kinds, then use sncloud_resource_schema to get summary, example, runtime JSON schema, or selected schema paths before writing manifests.
After sncloud_context_use_cluster selects a cluster in a root or organization-level session, sncloud_logs is also available for logs from Functions, Sources, Sinks, and Kafka Connect connectors in the selected cluster. sncloud_logs is cluster-scoped and appears only after cluster selection.
Pulsar tool groups
Pulsar clusters support the following tool groups.| Feature ID | Alias | MCP tools | Description |
|---|---|---|---|
pulsar-admin | All Pulsar administration tools | All Pulsar administration tool groups. | |
pulsar-admin-topics | topics | pulsar_admin_topic_read, pulsar_admin_topic_write | List, create, delete, and inspect Pulsar topics. |
pulsar-admin-namespaces | namespaces | pulsar_admin_namespace_read, pulsar_admin_namespace_write | List and manage Pulsar namespaces. |
pulsar-admin-namespace-policy | namespace-policy | pulsar_admin_namespace_policy_get, pulsar_admin_namespace_policy_set, pulsar_admin_namespace_policy_remove, pulsar_admin_namespace_policy_get_anti_affinity_namespaces | Get and set namespace-level policies such as retention, TTL, backlog, and anti-affinity namespace lists. |
pulsar-admin-tenants | tenants | pulsar_admin_tenant_read, pulsar_admin_tenant_write | List and manage Pulsar tenants. |
pulsar-admin-schemas | schemas | pulsar_admin_schema_read, pulsar_admin_schema_write | View and manage topic schemas. |
pulsar-admin-subscriptions | subscriptions | pulsar_admin_subscription_read, pulsar_admin_subscription_write | List and manage topic subscriptions. |
pulsar-admin-brokers | brokers | pulsar_admin_brokers_read, pulsar_admin_brokers_write | List and inspect broker nodes. |
pulsar-admin-brokers-status | brokers-status | pulsar_admin_status | Retrieve broker status. |
pulsar-admin-broker-stats | broker-stats | pulsar_admin_broker_stats | Retrieve broker-level statistics and metrics. |
pulsar-admin-clusters | clusters | pulsar_admin_cluster_read, pulsar_admin_cluster_write | List and inspect Pulsar clusters. |
pulsar-admin-functions | functions | pulsar_admin_functions_read, pulsar_admin_functions_write | List, inspect, and manage Pulsar Functions. |
pulsar-admin-functions-worker | functions-worker | pulsar_admin_functions_worker | Inspect Functions worker status. |
pulsar-admin-ns-isolation-policy | ns-isolation | pulsar_admin_nsisolationpolicy_read, pulsar_admin_nsisolationpolicy_write | Manage namespace isolation policies. |
pulsar-admin-packages | packages | pulsar_admin_package_read, pulsar_admin_package_write | Manage Pulsar packages. |
pulsar-admin-resource-quotas | resource-quotas | pulsar_admin_resourcequota_read, pulsar_admin_resourcequota_write | View and manage resource quotas. |
pulsar-admin-sinks | sinks | pulsar_admin_sinks_read, pulsar_admin_sinks_write | List and manage Pulsar IO sinks. |
pulsar-admin-sources | sources | pulsar_admin_sources_read, pulsar_admin_sources_write | List and manage Pulsar IO sources. |
pulsar-admin-topic-policy | topic-policy | pulsar_admin_topic_policy_read, pulsar_admin_topic_policy_write | Get and set topic-level policies. |
pulsar-client | pulsar_client_consume, pulsar_client_produce | Consume and produce messages on Pulsar topics. |
Kafka tool groups
Kafka clusters support the following tool groups.| Feature ID | MCP tools | Description |
|---|---|---|
kafka-admin | kafka_admin_topics_read, kafka_admin_topics_write, kafka_admin_groups_read, kafka_admin_groups_write, kafka_admin_partitions_write | Manage Kafka topics, partitions, and consumer groups. |
kafka-admin-schema-registry | kafka_admin_sr_read, kafka_admin_sr_write | Manage Schema Registry subjects and schemas. |
kafka-client | kafka_client_consume, kafka_client_produce | Consume and produce messages on Kafka topics. |
kafka-admin-kafka-connect | kafka_admin_connect_read, kafka_admin_connect_write | Kafka Connect tools. This feature ID is accepted, but Kafka Connect tools are not exposed on Remote MCP Kafka cluster sessions in the current preview. |
Kafka topic, partition, and consumer-group tools are enabled by
kafka-admin.
There are no separate Remote MCP feature IDs named kafka-admin-topics,
kafka-admin-partitions, or kafka-admin-groups.Combination shortcuts
Use these shortcut IDs to enable multiple tool groups at once.| Shortcut | Includes |
|---|---|
all | Every available tool group across Pulsar, Kafka, StreamNative Cloud, and dynamic tools. |
all-pulsar | Pulsar tooling features. |
pulsar | Alias for all-pulsar. |
all-kafka | Kafka tooling features. |
kafka | Alias for all-kafka. |
pulsar-admin | All pulsar-admin-* tool groups. |
kafka-admin | Kafka topic, partition, consumer group, and compatible admin tools. |
cloud | Alias for streamnative-cloud. |
streamnative-cloud | StreamNative Cloud organization tool families. |
Dynamic tools
In addition to static tool groups, the Remote MCP Server supports dynamic tools that expose your own workloads as MCP tools.| Feature ID | Description |
|---|---|
functions-as-tools | Expose Pulsar Functions as callable MCP tools on fixed Pulsar cluster sessions. See Functions as Tools. |
agents-as-tools | Accepted dynamic agent-tool feature ID. In the current preview, include functions-as-tools or pulsar-admin-functions when you want to expose eligible Orca agents on fixed Pulsar cluster sessions. See Agents as Tools. |
Dynamic tools are available on fixed cluster endpoints. They are not added
after selecting a cluster inside an organization-level session with
sncloud_context_use_cluster.Client tool parameter notes
- Kafka consume tools use
groupfor the Kafka consumer group ID. Whengroupis omitted, the server uses an ephemeral group and cannot read committed offsets. - Pulsar consume tools use
subscription-namefor the subscription. This is the Pulsar equivalent of a durable cursor; do not pass a Kafkagroupparameter to Pulsar tools. - StreamNative Cloud domain read tools use
operation=list|get,resource, and optionalname.nameis required forget. - StreamNative Cloud domain write tools use
operation=apply|delete,resource, and eithermanifestforapplyornamefordelete. - StreamNative Cloud write tools use
manifestas a JSON string. Do not pass YAML or an object. Usedry_run=trueforapplybefore applying changes. sncloud_logsrequires a selected cluster in a root or organization-level session. Use it for logs from Functions, Sources, Sinks, and Kafka Connect connectors.- StreamNative Cloud read tools omit
statusandmetadata.managedFieldsunless you setincludeStatus=trueorincludeManagedFields=true. sncloud_resource_schemadefaults toformat=summary. Useformat=examplefor an example manifest,format=jsonschemafor runtime Kubernetes schema when available, andpathssuch asspec.brokerorspec.clusterRefsto reduce schema size.
Usage tips
- Start minimal. Enable only the tool groups you need. Fewer tools reduce token usage and help AI agents select the right tool more reliably.
- Use shortcuts for broad access. If you need all Pulsar tools, use
all-pulsarinstead of listing each group individually. - Match groups to your cluster type. Pulsar tool groups only work on Pulsar clusters, and Kafka tool groups only work on Kafka clusters. Enabling mismatched groups has no effect.
- Combine groups freely. You can mix StreamNative Cloud, Pulsar, Kafka, and dynamic tool groups. For example,
sncloud_context,pulsar-admin-topics,pulsar-clientenables cluster discovery, Pulsar topic administration, and Pulsar message operations. - Use StreamNative Cloud schema helpers before writes. Call
sncloud_resource_catalog, thensncloud_resource_schema, then a read tool, then a write tool withdry_run=truebefore applying changes.