Name	Name	Last commit message	Last commit date
parent directory ..
README.md	README.md
byoc-infrastructure.md	byoc-infrastructure.md
cloud-core.md	cloud-core.md
identity.md	identity.md
kafka-admin.md	kafka-admin.md
kafka-clusters.md	kafka-clusters.md
pulsar-admin.md	pulsar-admin.md
pulsar-clusters.md	pulsar-clusters.md
workspaces.md	workspaces.md

Name

Last commit message

Last commit date

Remote MCP smoke tests

These walkthroughs verify StreamNative Cloud remote MCP execution path. Existing docs/smoke-tests/*.md files remain snctl route tests.

Prerequisites:

Agent runtime connected to StreamNative Cloud remote MCP server.
Remote MCP server is public preview and disabled by default. Enable org-level MCP manually in StreamNative Cloud UI before org/control-plane tests.
Enable cluster-level MCP manually in StreamNative Cloud UI for every cluster used by Pulsar/Kafka data-plane tests. New clusters default to cluster-level MCP disabled.
Fixed cluster endpoint or org-level cluster selection available for Pulsar/Kafka data-plane tests. sncloud_context_use_cluster works only when cluster-level MCP is enabled on the target cluster.
Disposable <test-org> and explicit approval for billable/destructive resources.

Acceptance:

Agent uses MCP tools, not snctl, except for documented fallback-only gaps.
Control-plane writes use sncloud_resource_catalog / sncloud_resource_schema, JSON-string manifest, dry_run=true, then dry_run=false.
Agent never calls or mentions generic sncloud_resources_* tools.
If org-level or cluster-level MCP is not enabled, remote MCP smoke result is an explicit prerequisite skip/failure with UI enablement guidance, not a cluster defect.

Navigation Menu