durin
Book A Demo
Knowledge base
Connections & MCP

Understanding connections

Understand Durin connection states, team access and provider authorization before enabling tools for people in your organization.

Everyone1 min readUpdated

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 qualifying installation contributes to connection quantity; Custom MCP servers your organization runs itself are excluded.

Try Durin with your MCP workflow.

Book a demo to explore agent access, policy checks, approvals, and audit records with our team.

Book a demo

Choose which optional purposes this browser allows. Cookies that keep the site working, keep you signed in and remember this choice are always on, as is the referral cookie a referral link sets for up to 90 days. Your choice is stored in a first-party cookie for 180 days. Saving a choice that turns analytics off reloads this page if analytics was running on it. Read the privacy notice.