Stand-up without the board
Before stand-up the lead asks what moved for the platform team since yesterday. Memtro lists the stories updated in that window with their state and owners, and reads the iteration's progress for the points still open.
Stories, epics and iterations answered from Shortcut, and updated when you ask.
Connect Shortcut with an API token and Memtro searches stories with Shortcut's own syntax, reads a story with its comments and tasks, reports epic and iteration progress, and translates teams, workflow states and members. The hourly sync writes each updated story into memory as an event and a ticket. When asked, and once an administrator has granted each action by name, it creates and updates stories, epics, iterations, labels and Docs, moves and reassigns stories, comments, manages tasks and links stories, all as you. Followers and owners are notified, and deleting a story or comment is permanent.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Shortcut tool, reads what it needs, and answers with the source cited.
These tools change something in Shortcut. 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.
Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Shortcut, choosing the same kinds; the tab shows Shortcut's own steps. Each event can start a job, with the event as its input. Shortcut signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Shortcut 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.
Which of Priya's stories are still not done?
What is left in the current iteration for the platform team?
How far along is the Checkout v2 epic, and who owns it?
Create a chore for the platform team called 'Rotate the staging certificates' and assign it to Sam
Move story 4127 to Ready for Review and comment that the fix is on staging
Before stand-up the lead asks what moved for the platform team since yesterday. Memtro lists the stories updated in that window with their state and owners, and reads the iteration's progress for the points still open.
Amy Foster pastes a Globex bug report and asks Memtro to file it and link it to the older duplicate. Memtro agrees the title with her, creates it as a bug in the mobile team's Ready for Development state with an owner, who is notified, links the two stories and returns the link.
The teams that lean on Shortcut most, a question each of them asks, and what they connect beside it.
A record in Shortcut 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 Shortcut open Settings → API Tokens, give the token a name and click Generate Token. It acts as you, so Memtro reads what you can see and anything it creates or changes is done by you
Copy the token: Shortcut shows it once. It allows 200 API requests per minute per token
In Memtro open Connections → Shortcut, paste the API token and connect. Stories updated in the last 7 days sync within the hour
Ask which of your stories are not done, or what is left in the current iteration
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Shortcut tools are the same everywhere.
Only when you ask, and only what it has been granted: create a story with a type, state, owners, epic and labels; update a story: move it to a state, reassign it, rename, re-estimate, change epic, iteration or labels, or archive it; delete a story permanently; comment on a story, or reply to a comment; edit a story comment; delete a story comment permanently; add a task to a story's checklist; tick off, reopen, edit or reassign a story's task; link two stories (blocks, duplicates, relates to); create an epic; update an epic: rename, change state, owners, teams or dates, or archive it; comment on an epic; create an iteration; create a label; create a Doc. 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. An hourly sync anchors recently changed Shortcut records into memory as entities.
API token. In Shortcut open Settings → API Tokens, give the token a name and click Generate Token. It acts as you, so Memtro reads what you can see and anything it creates or changes is done by you.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Shortcut, choosing the same kinds; the tab shows Shortcut's own steps. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.
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