Skip to main content
The Remote StreamNative MCP Server supports root and organization-level sessions in addition to fixed cluster sessions. Use a root or organization-level session when you want an MCP client to discover MCP-enabled clusters, switch cluster context during a session, or manage StreamNative Cloud control-plane resources.

​
Choose a root or organization endpoint

Use one of the following endpoints: After connection, the session starts with StreamNative Cloud organization tools. The global identity tool sncloud_context_whoami is available for the session. Other organization tools are controlled by the organization feature set. Cluster-specific Pulsar, Kafka, and log tools become available only after you select a cluster with sncloud_context_use_cluster.
For a fixed cluster session, use https://mcp.streamnative.cloud/mcp/x/<organization>/<instance>/<cluster>. See Remote MCP Access.

​
Discover and select clusters

Organization-level sessions expose context tools for finding and selecting MCP-enabled clusters. When you select a cluster, the current MCP session becomes a hybrid session. It keeps organization-level tools and adds static Pulsar or Kafka tools for the selected cluster. The selected cluster overlay also adds sncloud_logs for logs from Functions, Sources, Sinks, and Kafka Connect connectors in the selected cluster. Dynamic tools such as functions-as-tools and agents-as-tools are available on fixed cluster endpoints, but not after in-session cluster switching.

​
Use StreamNative Cloud prompts

Organization-level sessions also expose StreamNative Cloud prompts that help clients discover and inspect enabled clusters. Use the clusterType returned by list-sncloud-clusters when you call read-sncloud-cluster. Disabled or non-exposed clusters aren’t returned.

​
Manage StreamNative Cloud resources

Organization-level sessions expose domain-scoped tools for StreamNative Cloud resources. Read tools support list and get operations. Write tools support apply and delete operations. get and delete require name. apply requires manifest, a JSON string that contains one StreamNative Cloud resource. After sncloud_context_use_cluster selects a cluster, the session also exposes sncloud_logs for Functions, Sources, Sinks, and Kafka Connect connectors in the selected cluster. All domain tool families can use these schema helpers:
Write operations can change organization-level resources. Use dry_run=true before applying changes, and keep the Remote MCP access mode set to Read-Only unless mutation tools are required.
When you create or update a StreamNative Cloud resource through MCP, use this workflow:
  1. Call sncloud_resource_catalog for the resource domain, such as clusters or identity.
  2. Call sncloud_resource_schema for the resource type, such as PulsarCluster, KafkaCluster, or ServiceAccount.
  3. Call the matching read tool to inspect existing resources.
  4. Compose the resource manifest as a JSON string.
  5. Call the matching write tool with operation=apply and dry_run=true.
  6. Review the validation result.
  7. Repeat the apply operation with dry_run=false only when the dry-run result is acceptable.
The manifest argument must be a JSON string. Do not pass YAML or a structured object. Omit status, metadata.managedFields, and other read-only fields copied from read responses. The schema summary is guidance, not a replacement for server-side validation. Runtime OpenAPI schemas do not encode every cross-field or cross-resource constraint.

​
Control organization tools with features

Use X-MCP-Features to narrow the organization tool catalog by tool group. For example, X-MCP-Features: sncloud_context,sncloud_clusters exposes context tools plus cluster-domain resources. A feature ID can enable multiple MCP tools, including read/write pairs such as sncloud_clusters_read and sncloud_clusters_write. If an administrator configured allowed tools for the organization MCP entry, the header can only request a subset of that allow list. If you omit X-MCP-Features, the server uses the configured organization feature set. For the full header reference, see Remote MCP Headers and Feature Selection.

​
Manage MCP settings in the Console

Use the StreamNative Cloud Console to manage MCP availability, access mode, and allowed tools for your organization and clusters. The organization settings control root and organization endpoints. Cluster settings control fixed cluster endpoints and cluster tools added after sncloud_context_use_cluster selects a cluster.