Skip to main content
POST
Create a new MCP server

Authorizations

x-api-key
string
header
required

Project API key. Create and manage keys in the dashboard under Project → API Keys. Send as header: x-api-key:

Body

application/json
name
string
required

Name (slug): lowercase letters, numbers, hyphens. Unique per project.

Pattern: SLUG_PATTERN
Example:

"my-mcp-server"

description
string

Description of the MCP server

Example:

"Pinned Gmail + Slack tools for Cursor"

mode
enum<string>
default:META

Mode of the MCP server: NORMAL (specific tools) or META (meta tools only)

Available options:
NORMAL,
META
discoveryToolsWhitelist
boolean
default:true

Meta mode only: true = discovery limited to selected tools; false = exclude those tools from discovery.

selectedTools
string[]

Tool slugs: NORMAL = agent tool set; META = discovery filter list.

Example:
isPublic
boolean
default:false

Whether the MCP server is public

config
object

Configuration for the MCP server (endpoint, authToken, etc.)

Example:
externalMcpConfigs
string[]

External MCP configs (name, url, headers?, tools), same as workflow.

Example:
connectionCallbackUrl
string

OAuth return URL after a toolkit connection. Empty string clears.

Maximum string length: 2048
Example:

"https://myapp.com/oauth/callback"

Response

201 - application/json

MCP server created successfully

success
boolean
required

Success status

Example:

true

message
string
required

Success message

Example:

"Operation completed successfully"

data
object
required
Example: