Create MCP Server Config

Create an MCP server config. Tests the connection before creating. Returns 422 if the connection test fails. Provide either auth_config (inline) or auth_config_id (pre-existing, e.g. after OAuth).

Body Params

Schema for creating an MCP server config.

Creating an MCP server config also:

  1. Validates the URL (SSRF checks)
  2. Tests the connection by calling tools/list on the remote server
  3. Creates an auth_config for the credentials (or uses an existing one)

If the connection test fails, no records are created.

Provide either auth_config (inline creation) or auth_config_id (pre-existing),
but not both. Use auth_config_id when the auth config was created separately,
e.g. after completing an OAuth authorization flow via the /auth_configs and /oauth endpoints.

string
required
length between 2 and 255

Display name of the MCP server. Must be unique per tenant.

This name is used to derive the tool prefix (e.g., "Slack MCP Server" -> "slack_mcpserver").

Optional description of the MCP server's purpose.

string
required
length ≥ 1

MCP server URL (HTTPS only, no IPs/localhost/private ranges).

integer
1 to 120
Defaults to 60

Request timeout in seconds (default 60, max 120).

AuthConfigCreate | null

Authentication configuration for connecting to the MCP server.

Use auth_type=NONE for public servers, or provide credentials as needed.
Mutually exclusive with auth_config_id.

ID of an existing auth config to use for this MCP server.

Use this when the auth config was created separately, e.g. after completing
an OAuth authorization flow. Mutually exclusive with auth_config.

Responses

422

Connection test failed or validation error.

Language
Credentials
URL
LoadingLoading…
Response
Choose an example:
application/json