Agents act where the company already works — Slack, email, calendar, issue trackers, code — and anything else through MCP.
Built-in integrations
- Slack: agents are reachable teammates — they read channels, reply in threads, react, upload files, open DMs. An incoming Slack message routes to the right agent, and the answer goes back to the originating thread.
- Google — Gmail, Calendar and Drive: one click from the desktop app, no Google Cloud setup (see Google below).
- Jira and Confluence: through the Atlassian connector of the connector library, with your Atlassian account. In Jira: fetch, search (JQL), create, update, and transition issues. In Confluence: read, create, and update pages and whiteboards. You choose your Atlassian site on Atlassian's page; there is no domain, email or API token to type. An agent you had set up with a Jira API token keeps Jira ticked in Settings → Connectors and uses it as soon as you connect your account. If you connected Atlassian before Confluence was added, the connector shows Not connected once: connect it again to get Confluence.
- GitHub: follow pull requests and CI runs (the watchdog wakes an agent when a check completes or a PR merges), and react to repository events. GitHub access works through your machine's local
ghCLI — there is no separate connection to set up beyond a one-timegh auth login(see Best practices). - Sentry: production errors become work items an agent can pick up and fix.
Google: Gmail, Calendar and Drive
Connect a Google account from the card an agent shows in a conversation when it needs one, or from Settings → Connectors in the desktop app. Google's own consent page opens in your browser; there is no Google Cloud project to create and no client ID or secret to paste.
- What the agent can do: Gmail — search, read, send, reply (to the original sender or to the recipients you name) and forward, save a draft (a new email or a reply in its conversation) in your Drafts for you to review and send yourself, download the attachments of an email into the conversation's working folder, and attach files from that folder to an email it sends, replies with, forwards or drafts (up to 25 MB in total, a forward carrying the original attachments unless you ask otherwise); Google Calendar — list, create, update and cancel events; Google Drive — search, list and read files (Docs and Slides as text, Sheets as CSV) in your My Drive and in the shared drives you are a member of, list those shared drives, download a file into the conversation's working folder so the agent can open it with its own tools (a PDF, an image or an Office document as it is, up to 25 MB; a Google Doc, Sheet or Slides deck as a Word, Excel or PowerPoint file and a Google Drawing as a PNG image, up to 10 MB, the most Google converts), and work on your existing files and folders there: create a folder or upload a file (up to 5 MB) into a folder you name, update a file in place rather than adding a second one with the same name (Google keeps the previous version in the file's version history), and rename, move or copy a file. An upload with no folder named goes into a tamag0 folder at the root of your Drive, created once and reused. The agent can do in Drive only what your own access allows: in a shared drive, adding, updating and renaming need the Contributor role or higher, moving a file inside the drive needs Content manager, and moving it out of the drive needs Manager; a Google Workspace administrator can restrict more. When Google refuses, the agent tells you why and what it takes. It never deletes, trashes or shares a file.
- Sensitive actions ask first: sending, replying to, forwarding or drafting an email, changing a calendar event, and creating, uploading, updating, renaming, moving or copying in Drive ask for your consent in a conversation you are taking part in, and are refused in a run where nobody can answer — unless you allowed them for that conversation or turned off permission prompts. Reading, and downloading into the conversation's working folder, never asks.
- What Google grants is what you get: Google's page lets you untick a service. The card then shows which services are granted and which are not; reconnect and tick the missing one to grant it. If you connected Google before the agent could work on your existing Drive files, Drive shows as not granted until you allow it again, from the card or from Settings → Connectors.
- One connection per work context, then the agents you choose: a Google connection is yours, made once per work context — home, or one client context — and every agent you tick for Google in that context uses it; an agent you have not ticked does not use it. Connecting from a conversation's card at home also ticks that agent. A client context is connected from a conversation of that client, or from Settings → Connectors with that client selected; agents are ticked there separately. A connection is never used in another context, and when none of your agents works for a client any more, its connection there is removed. Within its context, a connection is used only in your own threads with the agent — your conversations with it, the personal threads it opens with itself, and the runs of your scheduled tasks — and never in a conversation shared with another agent, such as a thread while another agent takes part in it, a conversation between agents, a Slack exchange or a mission conversation where a client's people talk to the agent; scheduled tasks follow the same rule: the agent creates and manages them only in your own threads.
- It stays on your computer: the authorization is kept on the desktop, in your operating system's secret store (macOS Keychain, Windows credential protection, GNOME Keyring or KWallet on Linux), and Google is called from your computer. Without such a store the desktop refuses to connect — on Linux, see Linux keyring.
- Disconnect removes it from one context only: disconnecting removes your connection in that context; other contexts keep theirs, and the agents you ticked stay ticked for the next connection. Your Google account keeps the authorization it gave tamag0 until you remove it from your Google account's connected apps, which removes it everywhere at once.
- When Google withdraws the access (password change, revocation from your account, expiry), the card says the access was cut and offers Reconnect; other contexts are unaffected.
Email intelligence
Beyond raw email access, agents track business email: senders are classified automatically, threads needing a response are tracked and reminded, newsletter knowledge is extracted, and emails are mapped to the right project domain by pattern — so "waiting on a reply about the Acme contract" is something your agent knows.
Events and routing
External events (Slack, GitHub, Sentry, email) flow into a prioritized queue with per-company routing rules deciding which agent handles what — urgent events first, retries handled automatically.
Extensible through MCP
Any Model Context Protocol server adds new tools to an agent, from tested connectors to third-party or in-house servers over stdio, HTTP or SSE, with OAuth-based authentication supported. They all live in Settings → Connectors: you connect each one once per work context and choose which agents use it — see Connectors.
A company admin can also publish a server for everyone from Company → Configuration of the web console. Anyone else proposes one and an admin accepts or rejects it there, after seeing the server's full setup; admins can add servers there themselves, and the form takes only header and environment variable names, never their values. Every member computer then receives it, including newly invited agents before their first conversation starts. Passwords, API keys and OAuth secrets are never shared: whoever shares a server keeps using it without signing in again, and every other member enters their own values, which stay on their computer.
Tool access is managed per tool from the connector's Tool permissions, with sensitive outbound actions requiring human consent (see Security).
Connector library
The desktop app lists ready-made connectors in Settings → Connectors → Discover. Each one is the publisher's own MCP server, hosted on the publisher's domain. Before listing it, the tamag0 team signs in, lists its tools and renews the access. Memo Bank still awaits a full sign-in, tool-listing and access-renewal check with a bank account. GitLab and Zapier are the other exceptions: their sign-in and access renewal were tested, but their MCP server refused the session for the test accounts, so their tools were not listed. You connect with your own account on the publisher's page; there is no client ID, secret or API key to paste.
The library currently holds: Airtable, Atlassian (Jira and Confluence), Attio, Datadog, Dealroom, Dropbox, Evertrace, GitLab, Granola, Linear, Memo Bank, Miro, monday.com, Notion, PayPal, Pennylane, Qonto, Semrush, Sentry, Stripe and Zapier.
With a client selected, the choices differ and the order is reversed: connect first, then tick the agents — see Add a connector at a client. At Home:
- Open Discover and pick a connector.
- Set it up for yourself: tick the agents that use it (the list shows when you have more than one). If you are not an admin and your colleagues need it too, also tick Also propose to the company; an admin approves it before they see it. A company admin first answers For whom?: For you leads to the same choices, while For all of the company adds it for everyone, who then find it in Added and connect it with their own account.
- Choose Connect. The publisher's page opens in your browser; sign in and approve the access. An admin who chose For all of gets Add for the company instead, which adds the connector without connecting it.
What a connector can do is what the publisher grants your account: the sign-in asks for the permissions the publisher offers, and each agent sees only what your account sees. Its tools still ask before running until you allow them, tool by tool, from Tool permissions in the connector's menu.
The connection stays signed in: tamag0 renews the access in the background, so you do not sign in again the next day. The sign-in stays on your computer. If the publisher withdraws the access (revoked from your account, or expired for good), the connector shows Access cut and Reconnect brings it back. A conversation that is already running when the access is renewed can report that the service is unavailable; your next message in it works again.
Some publishers also require something on their side: GitLab, for example, answers only for accounts in a group where its MCP server is enabled. If Zapier refuses the session after you sign in, check your Zapier account first; the tamag0 team has not established why it refused the test account.
Memo Bank requires a desktop release with support for its OAuth sign-in method (client_secret_basic); older releases cannot connect it. It exposes accounts, transactions and supporting documents, including attaching documents, but cannot initiate payments or modify transactions. Non-admin Memo Bank users need authorization from a Memo Bank admin (Memo Bank guide).
For a service missing from the list, Add an MCP server takes its address or command.
Connect Slack
The built-in Slack integration above makes agents reachable in Slack. Slack's own MCP server is something else: with it, an agent searches and reads your Slack workspace with your own Slack access, from any conversation.
Slack only lets its own apps sign in, so a company connects it once, through a Slack app of its own:
- A Slack admin creates the app in your Slack workspace: MCP enabled, PKCE, token rotation, user scopes only, and the redirect URL
http://localhost:3118/callback(any free port works, as long as step 2 uses the same one). The app needs no client secret. - A company admin declares it once in tamag0: in the desktop app, open Settings → Connectors and choose Add an MCP server. Enter a name (for example
slack) and the URLhttps://mcp.slack.com/mcp, tick OAuth 2.0, then enter the app's client ID, the callback port (3118) and the scopes your agents need, separated by spaces — for examplechannels:history search:read.public. Leave the client secret empty, tick Add for all of your company, then choose Add. List only what you need: with no scopes, the sign-in asks for everything Slack offers, including posting messages and writing files. - Each colleague connects from Settings → Connectors, where Slack is already listed under Shared in your company: Connect on its row opens Slack's consent page, approved with their own Slack account, and they tick the agents that use it.
The connection then stays signed in: tamag0 renews Slack's access in the background, so nobody signs in again every day. Each sign-in stays on its owner's computer; the company shares the client ID, the port and the scopes, never an access.
If Slack withdraws the access (revoked from Slack, or the renewal expired), the row shows Access cut and Reconnect brings it back with the same settings.