MCP Configurations

User-owned MCP configuration profiles that assemble published data-cluster and external-API tools into a picker-shaped selection consumed by mcp-alien's AlienBackendProfileResolver. Each user owns one or more named, slug-addressed configurations; exactly one is flagged as the default and resolves when an MCP connection omits the ?config=<slug> query parameter. Also includes the per-session tool registry (/mcp-tools) that mcp-alien reads at tools/list time.

📄️ List the per-session MCP tool registry

Returns the full wire-shape tool catalog mcp-alien reads at `tools/list` time: enabled/public datacluster tools synthesized from `mcp_tool_definitions` joined with their `client_cluster_endpoint`, plus authored external-API tools. Unauthenticated callers (no bearer token) fall through to the global public catalog only. Authenticated callers additionally receive external-API tools from connectors owned by their own organization (gated on the `mcp_config:read` access-token ability), on top of the public catalog. The full `transport` field (routing/proxy details) is included in this response, unlike the UI-facing `available-sources` projection.

📄️ List the caller's MCP configurations

Returns all MCP configurations owned by the authenticated caller, ordered with the default configuration first, then by most recently created. Requires the `mcp_config:read` access-token ability.

📄️ List sources available to bind into an MCP configuration

Returns the catalog of data sources the caller can select from when building an MCP configuration: clusters the caller can access (public clusters plus clusters owned by the caller's organizations) enriched with their available datacluster tools and datasets, and external-API connectors visible to the caller enriched with their available tools. Requires the `mcp_config:read` access-token ability.

📄️ Promote a configuration to the caller's default

Marks the slug-addressed configuration as the caller's default, demoting the previous default in the same transaction. If the configuration is already the default, returns it unchanged. Owner only.

📄️ Get an MCP configuration by slug

Returns the stored configuration summary plus a resolved `{clusters, external_apis}` projection: each binding in the stored `config` is enriched with the cluster's name or the connector's slug, and any binding whose cluster/connector is no longer visible to the caller is silently dropped. Readable by the owner always; by other callers only when `visibility` is `org` (same organization) or `public`.

📄️ Update an MCP configuration by slug

Partially updates a slug-addressed configuration. Any field omitted from the body is left unchanged. Setting `is_default: true` demotes the caller's previous default in the same transaction. Owner only.

📄️ Delete an MCP configuration by slug

Deletes a slug-addressed configuration. Refuses to delete the caller's only remaining configuration. If the deleted configuration was the caller's default, the most recently updated remaining configuration is promoted to default in the same transaction. Owner only.

📄️ Get the caller's default MCP configuration (legacy)

Returns only the picker-shaped `config` payload (`{clusters[], external_apis[]}`) of the caller's default configuration, not the full summary. Preserved for callers that predate the slug-addressed routes; prefer `GET /mcp-configurations/{slug}` for new integrations.

📄️ Create an MCP configuration

Creates a new named configuration owned by the caller. The caller's first configuration is always flagged as the default, regardless of `is_default`, so that the `?config=<slug>`-omitted resolution path is always resolvable for new accounts. Requires the `mcp_config:write` access-token ability.

📄️ Replace the caller's default MCP configuration (legacy)

Overwrites the `config` payload of the caller's default configuration, or creates one (named `'Default'`, `visibility: 'private'`) if the caller has none yet. Preserved for callers that predate the slug-addressed routes (the web-app picker and mcp-base's `set_profile` tool); prefer `PUT /mcp-configurations/{slug}` for new integrations. Owner only.

📄️ Delete the caller's default MCP configuration (legacy)

Deletes the caller's default configuration. Unlike `DELETE /mcp-configurations/{slug}`, this legacy route has no last-configuration guard. Preserved for callers that predate the slug-addressed routes; prefer `DELETE /mcp-configurations/{slug}` for new integrations. Owner only.