# Connectors

> One place in the desktop app for the services your companions use: tested connectors, the ones your company shares, and the MCP servers you add by hand. You connect each service once, with your own account, then choose which companions use it.

## Settings → Connectors

**Settings → Connectors** has two views:

- **Added** — your connectors, their state, and the companions that use them, in three groups: shared in your company (added by an admin), added by you, and custom MCP servers (added by hand).
- **Discover** — the tested connectors. Each shows who publishes it and what it is for; adding one never asks for an address.

A connector that needs you — its access was cut, or a companion you ticked cannot use it yet — comes first in its group, and a dot on **Connectors** and **Added** tells you so from anywhere in Settings. The others follow, the ones your companions use most first, in the context you are looking at.

## Connect once, then choose your companions

A connection belongs to you, not to a companion: you connect a service once per work context, and every companion you tick uses that same connection. Google works the same way: it sits among the connectors you added, connected once per work context, and turned on for the companions you tick. What it lets companions do is described in [Integrations](https://tamag0.ai/docs/integrations.md).

- **Connect**: open the connector in Discover and choose **Connect**; the publisher's page opens in your browser. A connector that asks for a key instead asks for it once, and the key stays on your computer.
- **Choose the companions**: click the companions on a connector's row to tick or untick them. A ticked companion receives the connector's tools in its context — the row says how many and how much context they take; the others do not see them. Unticking a companion disconnects nothing.
- **Nothing connects by itself**: a connector you or an admin adds is only available until you connect it and tick a companion, and no sign-in window opens on its own.
- **From a conversation**: when a companion needs a connector, it shows a card. **Connect _name_** connects it and turns it on for that companion; **Turn on for _companion_** turns on a connector you already connected, in one click and without a browser. At home, for a tested connector you have not added yet, **Add _name_** adds it for you, turns it on for that companion and opens its sign-in. While a sign-in waits for your browser, **Cancel** stops it, from the card or from its row in Settings → Connectors; nothing is saved. A connector that needs values is never filled in from a conversation: the card sends you to Settings → Connectors.
- **Disconnect** removes your account from that connector. A connector shared in your company stays in the list, for you and your colleagues. At Home, a connector you added yourself also leaves the list, and its connections at your clients go with it. At a client, **Disconnect from _client_** removes only that client's connection; your Home connection is not touched. Google is the exception to the Home rule: it never leaves the list, so **Disconnect** removes your Google connection in that context only, the connections in your other contexts stay, and the companions you ticked stay ticked, ready for the next connection. Nothing is revoked at the publisher: remove the access from your account there to withdraw it everywhere.

## Home and client contexts

If you work for clients, a **Context** selector appears at the top of the screen: Home, or one client.

- At a client, you find your Home connectors **without** any of their connections: each starts not connected and with no companion ticked there. Your Home sign-ins and keys are never reused for that client.
- You connect a connector **for that client** — with the account the client gave you, a key typed for that client, or, for a server that needs neither, by confirming its address or command — once, whatever the number of your companions placed there. Connecting turns no companion on; you tick the companions placed at that client separately.
- A key written into a server's address or command is the exception: confirming it keeps that key, so what your companions read or write for that client goes through the account the key belongs to, the same as at Home. The confirmation tells you so (**This address contains a key.**).
- In a conversation for a client, the card shows the two steps in order: **Connect for _client_**, then **Turn on for _companion_**, which is available once that client's connection exists.
- You add connectors at Home only; a connector you add there appears at every client, not connected.
- When your last placement at a client ends, the connections you made for that client are deleted from your computer.

## Shared conversations

Each connection has its own **Allow in shared conversations** box, unchecked by default. In a conversation with another companion or with someone outside your own conversations, a companion uses only the connectors you allowed there: what others ask then goes through your account. Otherwise the companion says it does not use that service in this conversation, the same way whatever the reason, so nobody learns about your settings. Google is never used in a shared conversation: its box stays greyed and unticked.

## Your company's connectors

- **Propose to your company**: when you add a connector, tick **Also propose to _company_**, or choose **Propose to _company_** in its row's menu later. An admin approves it before your colleagues see it; meanwhile you keep using it. Once it is approved, the companions you ticked keep using it.
- **Admins** choose **For all of _company_** instead: the connector is added for everyone without connecting anyone. Each person then connects their own account and picks their own companions. Nobody uses anyone else's account, and passwords, keys and secrets are never shared.
- **Remove for all of _company_** (admins only, in the connector's menu, confirmed in place) removes it for everyone; each computer drops it, with its connections, at its next sync. It can be added again from Discover.

## Custom MCP servers

For a service that is not in Discover, add a [Model Context Protocol](https://modelcontextprotocol.io/) server yourself: **Add an MCP server** asks for its name and its address (HTTP or SSE) or its command (stdio), with optional OAuth 2.0 sign-in, then which companions use it. **Import from the Claude configuration** and **Advanced configuration (JSON)** stay available under the form.

A custom server's menu offers **Edit** (address, command and headers — not its name, its companions or its shared-use box), **Tool permissions** (allow, ask or deny, tool by tool, with sensitive outbound actions asking for consent — see [Security](https://tamag0.ai/docs/security.md)) and **Delete**.

## Related

- [Integrations](https://tamag0.ai/docs/integrations.md)
- [Cross-workspace assignments](https://tamag0.ai/docs/cross-workspace-missions.md)
- [Security](https://tamag0.ai/docs/security.md)