MCP Server Connection

MCP Server Connection is the wizard that creates or edits the servers that MCP Server Mesh then lists — registration, not inventory. It runs as a full page at /mcp-connect/new and /mcp-connect/:id/edit (an earlier version lived in a modal; the modal is still used for the quick-edit affordance from the Mesh table). The base flow the product promises is "60 seconds, three fields" — server type, name, endpoint — with transport, auth type, and policy mode tucked behind a collapsed Advanced section that defaults to sensible values (HTTP, API key, auto-discover on, observe mode).

Selecting a vendor tile (GitHub, Postgres, AWS, Snowflake, Iceberg, or Custom) prefills the endpoint and, for AWS/Snowflake/Iceberg, reveals a structured credentials block instead of the legacy single opaque token. These vendor tiles are UX shortcuts for typing a known endpoint and credential shape — FaburAI does not ship vendor-specific MCP adapters; Custom accepts any MCP-compliant endpoint the same way the other tiles do under the hood. As the user types an endpoint, the form debounces 600ms and calls a reachability probe that does a plain TCP dial against the host and port — it confirms the URL resolves and is reachable, not that anything MCP-shaped is listening on the other end. An unreachable result is a warning, not a block: the connector can still be saved, and discovery retries once the endpoint comes up. New connections are capped at one MCP server for trial tenants; paid tenants have no cap enforced at this layer.

Structured credentials submitted through a vendor tile are persisted to the server's row and, when a Kubernetes client is available, synced best-effort into a K8s Secret that the vendor's MCP pod reads from — creating it if absent, merging new keys into it if it exists so operator-set keys the wizard doesn't manage survive. Values are AES-256-GCM encrypted before they reach the Secret whenever the DP has an encryption key configured; a missing key or missing cluster access is logged and skipped rather than failing the save, so the database row is always the source of truth even if the Secret sync lags or never runs. In edit mode, leaving a credential field blank means "keep the stored value," not "clear it" — only non-empty fields are sent.