AI Connect
How AI systems reach your tools, and how FaburAI draws that boundary.
This page is under review.
- AI-authored curated content. Every claim is anchored to a derived fact, but the wording, emphasis, and pedagogy are unreviewed product judgment.
AI Connect is the front door. It is where you declare which MCP servers exist, how to authenticate to them, and which callers are allowed into the mesh at all.
- Two jobs live here that are easy to confuse:
- Connectivity — registering a server, configuring its endpoint and credentials, and confirming your Data Plane can actually reach it.
- Identity binding — resolving *who* is calling. An AI Actor may be an agent, a model, an application, or a role. Until an actor has an identity, policy has no subject to match on.
Discovery runs on connect and on refresh, and it is what populates the AI Catalog. Credentials never live in the corpus or the UI: they are encrypted at rest and synchronised into your cluster as Kubernetes Secrets.
The distinction that matters: AI Connect decides what may enter the mesh. AI Control decides what it may then do.
Provenance
This page is derived from the following implementation sources.
docs/corpus/narrative/concept-ai-connect.md
Last verified at commit b61836e.