Where is it written down
A new starter asks how holiday requests work at Acme. Memtro searches Slite, finds the leave policy note under People, reads its full text and answers from it, noting that the note was marked verified last month.
Ask where something is documented in Slite, and whether that note is still verified.
Connect Slite with your personal API key and Memtro searches notes by words, lists recently edited notes or a note's children, and reads a note's full text with its review state. The key sees what you see in Slite, private notes included. It reads on demand and there is no hourly sync. When you ask, and once an administrator has granted the action by name, it can create and rewrite notes, verify them or flag them outdated, archive them and hand them to a new owner, all as you. Deleting a note also deletes every note under it, irreversibly.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Slite tool, reads what it needs, and answers with the source cited.
These tools change something in Slite. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Once Slite is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
Where is our expenses policy documented?
Which onboarding notes are marked outdated?
What changed in the wiki this week?
Create a note under Customer notes summarising today's Northwind call
Flag the old VPN setup note as outdated because we moved to the new provider
A new starter asks how holiday requests work at Acme. Memtro searches Slite, finds the leave policy note under People, reads its full text and answers from it, noting that the note was marked verified last month.
Hannah Brooks updates the travel policy and asks Memtro to put the new version in Slite. Memtro replaces the note's content with the text she approved and marks it verified until next year, so everyone who opens it sees the badge.
The teams that lean on Slite most, a question each of them asks, and what they connect beside it.
A record in Slite is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
In Slite open the Organisation menu (top left) → Settings → API, click Create a new key and follow the instructions. Copy it: Slite shows it only once
The key is personal, so Memtro sees what you can see in Slite, private notes included, and every change it makes is made as you
In Memtro open Connections → Slite, paste the API key and connect
Ask where the expenses policy is documented
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Slite tools are the same everywhere.
Only when you ask, and only what it has been granted: create a note (in your personal channel unless a parent note is given); edit a note's title or replace its content; mark a note Verified, optionally until a date; flag a note as Outdated with a reason; archive or restore a note; hand a note to another owner (a user or a group); delete a note and all its children (permanent). Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
API key. In Slite open the Organisation menu (top left) → Settings → API, click Create a new key and follow the instructions. Copy it: Slite shows it only once.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time