Skip to main content
POST
Register a custom MCP connector (owned by caller).

Authorizations

Authorization
string
header
required

Session JWT. After nasiko auth login, print it with jq -r '.clusters[.active].token' ~/.nasiko/config.json. API keys aren't supported.

Body

application/json
name
string
required
url
string
required
auth_type
string
basic_password
string | null
basic_username
string | null
credential_header_name
string | null
description
string | null
display_name
string | null
headers
object | null
logo_url
string | null
oauth_client_id
string | null
oauth_client_secret
string | null
oauth_scopes
string | null

Explicit OAuth scope (space-separated), replacing automatic selection.

oauth_send_resource
boolean | null

Force (true) or suppress (false) the RFC 8707 resource parameter; omit to let discovery decide.

transport
string
url_param_name
string | null

Response

Connector created — data is the connector view

Standard MCP response envelope: {"data": …, "status_code": N, "message": "…"}. data is a free-form object; each route's response description says what it contains.

data
object | null
required
message
string
required
status_code
integer<int32>
required
Required range: x >= 0
Example:

200