# Connect your apps once, for every agent Guide · Peter Larsen · written 2026-09-02 Unforgetter does not connect to your email, calendar or Slack, on purpose. This guide explains why, and shows how to give all your agents the same app connections through one gateway, so you set up each account once instead of once per agent. Canonical: https://unforgetter.com/blog/connect-your-apps-once People ask whether Unforgetter connects to Gmail, Slack, Notion or their calendar. It does not, and this is a design decision rather than a gap. This guide explains the decision and then shows the pattern that makes it painless: one connector gateway that every agent shares. ## Two different jobs Reading your apps and remembering what you concluded are different jobs, and mixing them makes both worse. Reading is a stream: every email, every meeting, every commit, most of it irrelevant to any particular task. Your agents are already good at this. Claude, ChatGPT, Cursor and Grok Bot all reach external apps through connectors or MCP servers, and they get better at it every month. Remembering is a residue: the decision that came out of the thread, the correction you made after the meeting, the idea you turned down. It is small, it changes slowly, and it has to be the same in every agent you open. That is what Unforgetter holds. Keeping the stream out keeps the memory small, current and yours. ## If Google Drive is already connected You can already ask your AI to find and read Drive files through a working connection. Unforgetter can supply the saved context around those files: project names, decisions, corrections and working preferences. For example, the team might call a spreadsheet “the influencer overview” and agree to use its September tab for reporting. If that decision is available in memory, the agent can use it to guide a search and interpret the results. It must still read the document for current figures. This is an illustrative benefit; we have not measured improved Drive search quality. Both capabilities must reach the same conversation. Installing Unforgetter does not automatically add memory to ordinary ChatGPT chats or reuse ChatGPT’s Google authorisation. Keep a working app connection and verify the memory integration in your chosen client during setup. **Update, 24 September 2026:** Alpha16 also includes a separate, read-only Drive integration for approved team folders in the local companion setup. It needs its own Google consent and reads documents on demand. It does not index Drive or copy document contents into memory. The complete customer team workflow is still being verified. See [app connections and current limitations](https://unforgetter.com/docs#connected-apps). ## The per-agent problem The reason connectors feel painful is not the connecting. It is doing it once per agent. Three Gmail accounts and four agents is twelve authorisations, twelve places a token lives, twelve things to revoke when you rotate a password. Add a second calendar and a client's Slack and the number stops being funny. Every agent you try next starts the count again. ## The pattern: one gateway, every agent Set up each app once in a gateway that speaks MCP. Point every agent at the gateway. When you add an account, every agent gets it. When you revoke one, every agent loses it. Your agents see one endpoint; the gateway does the rest. Two products we have looked at do exactly this. Neither is an endorsement, and Unforgetter has no commercial relationship with either; they are listed because people ask. Details checked 2 September 2026. **Rube, by Composio** ([rube.app](https://rube.app)). Hosted. One endpoint, `https://rube.app/mcp`, gives an MCP client access to several hundred apps; Composio handles the OAuth flows and keeps the connectors current. Setup guides exist for Claude Desktop, Claude Code, Cursor and ChatGPT's developer mode. Good fit if you want to connect once and never think about it. **Executor** ([executor.sh](https://executor.sh)). Open source, MIT licensed, with a hosted cloud and a self-hosted option. Built as an MCP gateway: multiple accounts of the same service side by side (a work and a personal Gmail, a staging and a production Stripe), and a policy per tool: always allowed, needs approval, or blocked. Secrets are injected at call time and never enter the model's context. Good fit if you have several accounts per service, or want the policy layer and the option to run it yourself. Others exist. Whatever you pick, check four things: several accounts per service, approval per tool for anything that writes, where the credentials live, and how you revoke. ## How it fits with Unforgetter In your agent's MCP configuration the gateway and Unforgetter sit side by side. The gateway provides app access; Unforgetter provides the published memory. An illustrative workflow, once capture and publication are connected, looks like this. You ask Claude to prepare Thursday's client meeting. Claude asks Unforgetter for the current memory on that client: what was agreed, what is still open, how you like briefings written. Claude then reads the last week of email and the calendar through the gateway. It writes the briefing. At the end of the session it proposes one line back to Unforgetter: the client confirmed the scope change on Tuesday. Nothing from the inbox is copied into the memory; only the conclusion is. The next day you open another connected agent for work on that client. Once the change is published, it can retrieve the updated scope from the shared memory. It never saw the email, and does not need to. ## What to keep out of the memory A good rule: if it is a fact about the world that any agent could look up again, it belongs in the app and reaches the agent through the gateway. If it is a fact about what you decided or how you work, it belongs in the memory. The memory is for the things that would otherwise have to be re-explained. If you already use a gateway, connecting Unforgetter beside it takes the same shape as any other MCP server; the guided setup in the [private alpha](https://unforgetter.com/private-alpha) walks through it. A gateway is optional. You can keep your agent’s existing app connections and add Unforgetter alongside them.