Understanding connections
Learn the difference between an installation and personal access.
One installation, separate personal access
A connection is one configured upstream instance with its own authentication, tools, and policy boundary. An administrator manages the installation. Each person still needs team access and any required provider authorization.
Installation states
Check the installation state before expecting tools in a client.
- Draft: saved setup; normal client calls are blocked. Guided read-only setup tests run separately.
- Enabled: reviewed tools are available subject to each request’s access checks.
- Disabled: normal routing stops while configuration and history remain.
Frequently asked questions
Does enabling grant access to everyone?
No. Team scope, personal access, provider authorization, and policy still apply. An installation with no team assignment is organization-wide, subject to those checks.
Can the same provider have two connections?
Yes. Separate installations have separate IDs and access boundaries. Each enabled, verified production installation contributes to connection quantity.