Monday planning
The project lead asks what is left on the Acme onboarding board. Memtro reads the Deck cards by column and answers with six open cards, two due on Friday, one assigned to Priya Sharma and three still unassigned in the backlog.
Ask what is on a Deck board, find a file, or read a Nextcloud note.
Connect Nextcloud with your login name and an app password and Memtro reads notes from the Notes app, Deck boards and cards with due dates, labels and assignees, your activity stream and a file search. The app password carries all of its user's rights. The hourly sync writes notes, Deck cards and activity into memory. When you ask, and once an administrator has granted them by name, it can create, change and delete notes, and create, change, comment on, assign, label, archive and delete Deck cards. Assigning or @mentioning someone notifies them. It can also create, clone or delete boards.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Nextcloud tool, reads what it needs, and answers with the source cited.
These tools change something in Nextcloud. 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, choose the kinds you want, and Memtro registers its address with Nextcloud for you. Each event can start a job, with the event as its input. Nextcloud sends a secret with every delivery, and one without it is refused.
Events and webhooksOnce Nextcloud 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.
What is on the Deck board for the website relaunch?
Which Deck cards are due this week, and who is assigned?
Find the Brightwave Ltd contract file in Nextcloud
Archive the Deck card for the old Northwind pilot
Assign the Acme logo card to Priya and move its due date to Friday
The project lead asks what is left on the Acme onboarding board. Memtro reads the Deck cards by column and answers with six open cards, two due on Friday, one assigned to Priya Sharma and three still unassigned in the backlog.
Dan Fletcher asks Memtro to assign the Northwind contract review card to Priya Sharma and set it due on Thursday. With the actions granted, Memtro changes the due date, assigns her, and Deck notifies her of the assignment.
The teams that lean on Nextcloud most, a question each of them asks, and what they connect beside it.
A record in Nextcloud 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 Nextcloud open Personal settings → Security → Devices & sessions, name an app password Memtro and copy it. It carries all of its user's rights, so consider a dedicated user with access to only what it should touch
Notes needs the Notes app 3.3 or later and Deck needs Deck 1.0 or later, enabled by an administrator
Open Connections → Nextcloud in Memtro, add your Login name and the App password, and type the Host name only, no https://, path or port, on a public DNS name with a publicly trusted certificate
Ask what is on the Deck board for the website relaunch
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Nextcloud tools are the same everywhere.
Only when you ask, and only what it has been granted: create a note in the Notes app; create a card on a Deck board; replace a note's title, body or category; delete a note; change a Deck card's title, description or due date; archive a Deck card; delete a Deck card; comment on a Deck card (people @mentioned are notified); assign a user to a Deck card (they are notified) or unassign them; add a label to a Deck card or remove it; unarchive a Deck card; create a Deck board, or add a column (stack) or a label to a board; clone a Deck board; delete a Deck board (restorable until Deck's trash retention passes) or restore a deleted one. 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 Nextcloud records into memory as entities.
Host, login name and app password. In Nextcloud open Personal settings → Security → Devices & sessions, name an app password Memtro and copy it. It carries all of its user's rights, so consider a dedicated user with access to only what it should touch.
Yes. Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Nextcloud for you. 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