DocumentationGovernance Center
Connectors
Under Connectors you provide custom MCP connectors for your whole team in anymize, with a shared connection or with each member's own credentials.
4 Min
What this page is for
Some firms have a system for which we have no ready-made connector: their own case management, a industry application, an internal portal. As long as it follows the MCP protocol, you connect it here once, and afterwards the whole team can use it in chat.
The difference from a personal connector is responsibility. Here the admin configures once what then applies to everyone, instead of twelve people entering the same server address twelve times.
What a connector fetches goes to the AI model anonymized: the client address from case management becomes a placeholder before anything leaves the firm.
Two kinds of provisioning
| Provisioning | How it works | When you use it |
|---|---|---|
| Shared | Your connection - address and credentials - applies to everyone on the team. | A system with one shared login, for example an internal portal. |
| Own credentials | The connector is available to everyone, but each member enters their own API key. | A system where each person has their own account. |
For a shared connection that is not yet established, the card shows “Connection pending”. A click on “Update credentials” completes it - depending on the connector via sign-in with the provider or by entering a key.
Settings per connector
A click on “Manage” opens the connector settings. That is where the three controls that matter for governance sit.
| Setting | What it does |
|---|---|
| Available for | Whole team or only certain groups. Without groups created yet, a note tells you to create some first. |
| Always ask on write access | The model must get the user's confirmation before every writing or changing action. |
| Available tools | Turn off individual connector tools, for example risky write actions. Each tool is marked as Read or Write. |
On top of that, the general “Connector access” rule from the Compliance page applies: it decides which connectors may be used at all, and can also be set per group.
May employees create their own connectors?
By default, yes. Anyone who wants can set up their own MCP connector with any server address. For many firms that is the most uncomfortable open door, because data could go to an address nobody has reviewed.
If you do not want that, set “Forbid custom connectors” on the Compliance page. Connectors you provide here for the team stay unaffected; only unilateral creation goes away.
What the employee sees
- A provided connector appears in their connector overview, marked as a team connector.
- With “Own credentials” they are asked once to enter their own API key. Until then they cannot use the connector.
- If the connector is only granted to certain groups, the others never see it.
- If “Always ask on write access” is set, the assistant pauses before every changing action and waits for confirmation.
This page exists only with a team, and inside a team only for Owners and Admins. A solo account sees the entry greyed out with “Team plan only”; a regular member does not see it and lands on the Compliance page if they open the URL directly.