MCP Server Registration

Each workspace can register multiple MCP servers. Servers are identified by a unique slug within the workspace. Transport URLs are stored securely and masked in API responses.

Register a server

curl -X POST https://app.korclaw.com/api/v1/mcp-servers \
  -H "Authorization: Bearer kc_live_your_api_key_here" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Analytics Tools",
    "slug": "analytics",
    "transport_url": "https://mcp.analytics.example.com/sse"
  }'

Response

{
  "data": {
    "id": "uuid",
    "workspace_id": "uuid",
    "name": "Analytics Tools",
    "slug": "analytics",
    "transport_url": "https://mcp.analytics.example.com/sse",
    "transport_url_masked": "https://mcp.analytics.example.com/sse?••••",
    "status": "registered",
    "created_at": "2026-09-20T10:00:00Z",
    "updated_at": "2026-09-20T10:00:00Z"
  }
}

Rejected fields

Registration rejects credential fields in the request body: credentials, secret, headers, authorization, api_key, token, auth, password. Transport URLs must be public http/https with no embedded credentials and no private IP addresses.

Management endpoints

• GET /mcp-servers — list all servers in workspace
• GET /mcp-servers/{id} — retrieve one server
• PATCH /mcp-servers/{id} — update name, slug, or transport_url
• DELETE /mcp-servers/{id} — remove server