Configure feature flags and access policies when connecting to the Remote StreamNative MCP Server.
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.
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.
Start with a minimal feature list to reduce token usage and improve tool selection accuracy.
Add agents-as-tools or pulsar-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.