x-portkey-beta header (or the equivalent SDK parameter) in your request with the feature’s version string.
Currently Available Beta Features
Server-Side MCP Execution
Header value:server-side-mcp-2026-06-01
Enables Portkey to fetch and execute MCP tools on your behalf — directly inside the gateway — rather than delegating execution to the upstream provider. This is required whenever you use the @portkey-mcp prefix in the Responses API or Messages API.
When to use it
- You are routing through a provider that does not natively support remote MCP tool execution (e.g. AWS Bedrock, Google Vertex AI).
- You want MCP credentials and tool invocations to stay within your own VPC and never touch provider infrastructure.
- You need per-user attribution, audit logs, and full observability over every MCP tool call.
SDK Parameter Reference
Thex-portkey-beta HTTP header maps to the following SDK parameters:
| SDK | Parameter name |
|---|---|
| Portkey Node SDK | portkeyBeta |
| Portkey Python SDK | portkey_beta |
OpenAI Node SDK (via createHeaders) | portkeyBeta |
OpenAI Python SDK (via createHeaders) | portkey_beta |
| cURL / raw HTTP | x-portkey-beta header |
Beta features may change before they are promoted to stable. Breaking changes within the same beta version string will not be made, but the stable API may look different. Check the changelog for updates.

