Skip to main content
POST
/
mcp-integrations
Create MCP Integration
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"
}
'
{
  "id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "slug": "<string>"
}

Documentation Index

Fetch the complete documentation index at: https://docs.portkey.ai/docs/llms.txt

Use this file to discover all available pages before exploring further.

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)

Response

200 - application/json

OK

​
id
string<uuid>
​
slug
string
Last modified on February 6, 2026