Connecting an account is different from using its permissions

A business may connect GitHub, Cloudflare, a database, a CRM and a payment provider to the same workspace. At first it looks like a settings problem: save a token, test the connection and show a green checkmark.

But having a connection and deciding who may act through it are different things.

When someone starts a GitHub installation from an Aurekai account, the returning installation should be attached to that exact account. An older installation in the same browser or organization isn't automatically the one they chose.

The account keeps the installation reference and available capabilities. The credential owner keeps the secret. When work needs to happen, the receiving application asks for the appropriate scoped access.

An external API may support deleting a resource or spending money. That says the provider can perform the operation, not that this account approved it. A model can suggest an action; the account and institutional owners still decide whether to execute it.

We separate external provider descriptions, installed capabilities, account context, financial admission and the execution boundary for that reason. MCP makes tools easier to discover and use, while preserving those distinctions.

The Bonfÿre MCP interface guide^{[1]Bonfÿre MCP interface guide} describes the system. It matters most for agencies and organizations that manage several customers whose permissions must never get mixed together.