Create MCP Integration

Create a new MCP Integration. Requires either organisation_id (with admin API key) or workspace_id in body.

POST /mcp-integrations

Create MCP Integration

cURL

curl --request POST \
  --url https://api.portkey.ai/v1/mcp-integrations \
  --header 'Content-Type: application/json' \
  --header 'x-portkey-api-key: <api-key>' \
  --data '
{
  "name": "My MCP Server",
  "url": "https://mcp.example.com/mcp",
  "auth_type": "none",
  "transport": "http"
}
'

200

{
  "id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "slug": "<string>"
}

Authorizations

x-portkey-api-key · string · header · required

Body

application/json

Only include optional fields (slug, description, configurations) when you have values for them. The example and code samples show required fields plus workspace_id and organisation_id when scoping.

name · string · required

Display name of the MCP integration

url · string<uri> · required

MCP server URL

auth_type · enum<string> · required

Available options: oauth_auto, headers, none

transport · enum<string> · required

Available options: http, sse

organisation_id · string<uuid>

Organisation ID (optional; required when using org admin API key without workspace_id)

workspace_id · string<uuid>

Workspace ID (optional; to create at workspace level)

slug · string

Optional slug; must be unique within organisation

Pattern: ^[a-zA-Z0-9_-]+$

description · string | null

configurations · object

Auth/config key-value pairs (e.g. headers, client credentials)

Show child attributes

secret_mappings · object[]

Dynamically resolve secrets from secret references at runtime. Valid target_field values are "configurations." (e.g. "configurations.oauth_metadata"). Each target_field must be unique.

Show child attributes

Response

200 - application/json

OK

id · string<uuid>

slug · string