Send these headers to your cluster-specific endpoint. See Remote MCP Access for endpoint construction details.
Header reference
X-MCP-Readonly— set totruewhen the client only needs read access. The remote server enforces read-only semantics for supported tools and skips operations that mutate resources.X-MCP-Features— provide a comma-separated list of feature identifiers to narrow the tool catalog. When omitted, the server enables discovery for the default feature set, including Pulsar Functions and Orca agents as tools.
Available feature identifiers
Use these values inside theX-MCP-Features header, can use , to passing multiple tools.
Combination feature sets
all— enables every available capability across StreamNative Cloud, Pulsar, and Kafka.
Kafka tooling
all-kafkakafka-adminkafka-clientkafka-admin-topicskafka-admin-partitionskafka-admin-groupskafka-admin-schema-registrykafka-admin-connect
Pulsar tooling
all-pulsarpulsar-adminpulsar-clientpulsar-admin-brokerspulsar-admin-broker-statspulsar-admin-clusterspulsar-admin-functionspulsar-admin-functions-workerpulsar-admin-namespacespulsar-admin-namespace-policypulsar-admin-isolation-policypulsar-admin-packagespulsar-admin-resource-quotaspulsar-admin-schemaspulsar-admin-subscriptionspulsar-admin-tenantspulsar-admin-topicspulsar-admin-sinkspulsar-admin-sourcespulsar-admin-topic-policy
StreamNative Cloud tooling
agents-as-toolspulsar-functions-as-tools
Usage tips
- Start with a minimal feature list to reduce token usage and improve tool selection accuracy.
- Add
agents-as-toolsorpulsar-functions-as-toolsonly when remote MCP clients should call Orca agents or Pulsar Functions directly. - Combine feature groups as needed. For example,
X-MCP-Features: streamnative-cloud,pulsar-admin,agents-as-toolsenables cloud context utilities, Pulsar administration, and agent tooling while leaving Kafka features disabled.