Skip to main content
The Remote StreamNative MCP Server exposes a wide catalog of tools. Clients can opt into specific capabilities at connection time by setting HTTP headers. This page summarizes the supported flags and feature names.
Send these headers to your cluster-specific endpoint. See Remote MCP Access for endpoint construction details.

​
Header reference

  • X-MCP-Readonly — set to true when 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 the X-MCP-Features header. Separate multiple values with commas.

​
Combination feature sets

  • all — enables every available capability across StreamNative Cloud, Pulsar, and Kafka.
  • all-pulsar — includes all Pulsar tooling features.
  • all-kafka — includes all Kafka tooling features.
  • pulsar — alias for all-pulsar.
  • kafka — alias for all-kafka.

​
Kafka tooling

  • kafka-admin
  • kafka-client
  • kafka-admin-schema-registry
  • kafka-admin-kafka-connect

​
Pulsar tooling

  • pulsar-admin
  • pulsar-client
  • pulsar-admin-brokers
  • pulsar-admin-brokers-status
  • pulsar-admin-clusters
  • pulsar-admin-functions
  • pulsar-admin-functions-worker
  • pulsar-admin-namespaces
  • pulsar-admin-namespace-policy
  • pulsar-admin-ns-isolation-policy
  • pulsar-admin-packages
  • pulsar-admin-resource-quotas
  • pulsar-admin-schemas
  • pulsar-admin-subscriptions
  • pulsar-admin-tenants
  • pulsar-admin-topics
  • pulsar-admin-sinks
  • pulsar-admin-sources
  • pulsar-admin-topic-policy

​
StreamNative Cloud tooling

  • cloud — alias for streamnative-cloud.
  • streamnative-cloud

​
Dynamic tooling

  • functions-as-tools
  • agents-as-tools
  • agents — alias for agents-as-tools.
  • agent-functions — alias for agents-as-tools.

​
Usage tips

  • Start with a minimal feature list to reduce token usage and improve tool selection accuracy.
  • Add agents-as-tools or functions-as-tools only 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-tools enables cloud context utilities, Pulsar administration, and agent tooling while leaving Kafka features disabled.