MementoConnectors
Connect the tools you already work in — Notion, Linear, Jira and others — and the assistant can look things up there while it works: the ticket a note mentions, the spec page behind a decision. Connecting one is a click and the service’s own sign-in page. Every connection starts read-only.
Connecting a service
Open Settings → Connections and pick a service under Connect a service. Before anything happens, Memento shows you what the agent will be able to do with it, what turning on write access would add, and which address your agent’s sandbox will be allowed to reach. Continue, and you sign in on the service’s own page and approve access there — Memento never sees your password for it. You land back in Settings with the connection switched on for the space you were in.
The catalog currently includes:
- Notion, Jira & Confluence, Linear, monday.com, ClickUp and Todoist — pages, tickets and tasks.
- Granola, Fireflies.ai and Otter.ai — meeting notes and transcripts.
- Miro, Airtable and Sentry.
- GitHub, Google Calendar and Google Drive do not let apps register themselves, so they show as unavailable until the Memento operator has registered an app with them.
A connection belongs to you and is switched on per space: the toggle on each connection sets it for the space you are in, and Enable per space lists them all. A space only uses the connections you switched on for it.
Read-only until you say otherwise
A new connection gives the agent only the tools that read: search, open a page, list issues. Tools that change something in the service — create a page, update a ticket, send a message — are withheld from the agent entirely until you tick Allow write access on that one connection.
That switch matters more than it looks. Changes the agent makes inside your library go through Memento’s review step (see The assistant); changes it makes in a connected service do not — they happen there, directly. And what the agent reads in a service is written by whoever wrote it, so a page or a comment can contain instructions aimed at an AI. Read-only keeps that harmless. Turn on write access for services where you would be comfortable with the agent acting on its own.
Expand a connection’s tool list to see exactly which tools it offers and which count as reading. For catalog services Memento keeps its own reviewed list, and a tool it has not reviewed counts as writing. For a custom server, Memento goes by the labels the server puts on its own tools.
When a connection stops working
Sign-ins expire and get revoked. Memento renews them by itself before a run, but if the service refuses — you removed Memento’s access there, or an admin did — the connection shows Needs reconnect with the reason, never Connected. Runs carry on without it and say so in the assistant’s activity trace. Reconnect takes you through the sign-in again and keeps the connection’s settings.
Disconnecting
The bin icon disconnects: Memento deletes the stored sign-in and, where the service supports it, revokes it there too, so the old access stops working immediately. Where a service offers no way to revoke, Memento says so — remove Memento in that service’s own settings to be sure.
Custom servers
Anything that speaks the Model Context Protocol over HTTPS can be connected by its address under Custom MCP server. Give Memento the URL alone and it finds out how the server signs people in and opens that page; for a server that uses a fixed API token instead, paste the token and it is stored encrypted.
What connected services see
A connected service receives something only when a run actually uses one of its tools: the search terms or other input the agent chose for that call. What it sends back becomes part of the run, so it also reaches your AI provider. Sign-ins are stored encrypted, are never shown back to your browser and never enter your library. The details are in the privacy notice.