Create an MCP integration from an external server URL. Registers the Portkey-side connection and returns the new id and slug; if auth_type is headers, custom_headers are required, and you usually follow with create_mcp_server and capability updates.
AI agents use create_mcp_integration to create or update resources in Portkey Admin — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Portkey Admin environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | Yes | URL endpoint of the MCP server to integrate |
name | string | Yes | Display name for the MCP integration |
slug | string | — | Custom slug. Auto-generated if omitted |
auth_type | string | Yes | Authentication type: 'none', 'headers' (custom headers), or 'oauth_auto' (OAuth) |
transport | string | Yes | MCP transport protocol: 'http' (streamable HTTP) or 'sse' (server-sent events) |
description | string | — | Description of the MCP integration |
workspace_id | string | — | Workspace ID — required when using organization admin API keys |
custom_headers | object | — | Custom headers for authentication (e.g. { "Authorization": "Bearer xxx" }). Sent via configurations.custom_headers |
Parameters from the server's own tool schema.
An AI agent can call create_mcp_integration faster than any human can review — one bad instruction and it creates or modifies resources in Portkey Admin by the hundred, each call as confident as the last.
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
Create an MCP integration from an external server URL. Registers the Portkey-side connection and returns the new id and slug; if auth_type is headers, custom_headers are required, and you usually follow with create_mcp_server and capability updates. It is categorised as a Write tool in the Portkey Admin MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_mcp_integration accepts 8 parameters: url, name, slug, auth_type, transport, description, workspace_id, custom_headers. Required: url, name, auth_type, transport. The full parameter table on this page comes from the server's own tool schema.
Register the Portkey Admin MCP server in PolicyLayer and add a rule for create_mcp_integration: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Portkey Admin. Nothing to install.
create_mcp_integration is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_mcp_integration rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for create_mcp_integration. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
create_mcp_integration is provided by the Portkey Admin MCP server (CodesWhat/portkey-admin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.