Status for the sponsor
Before the steering meeting the project manager asks where the Acme migration stands. Memtro lists its open work packages by status, names the three past their due date and their assignees, and quotes the last comment on each.
Ask which OpenProject work packages are open, overdue or changed this week.
Connect OpenProject with your host name and an API token and Memtro reads projects, work packages with type, status, assignee and dates, their comments and history, and time entries. The token carries all of its user's permissions. The hourly sync writes work packages that changed into memory. When you ask, and once an administrator has granted them by name, it can create, change, relate and comment on work packages, log and correct time, add watchers, manage versions, projects and meetings, and lock or reinstate users. Most writes email nobody. Deleting a work package, time entry or whole project is permanent.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right OpenProject tool, reads what it needs, and answers with the source cited.
These tools change something in OpenProject. 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 OpenProject, choosing the same kinds; the tab shows OpenProject's own steps. Each event can start a job, with the event as its input, and can be remembered where you choose. OpenProject signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce OpenProject 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 work packages in the Platform project are overdue?
What changed on work package 1432 since Monday?
How many hours did the team log on the Northwind rollout last month?
Comment on work package 1432 that the vendor confirmed the date
Mark work package 1520 as blocked by 1432 and add Priya as a watcher
Before the steering meeting the project manager asks where the Acme migration stands. Memtro lists its open work packages by status, names the three past their due date and their assignees, and quotes the last comment on each.
Dan Fletcher asks Memtro to push the BigCo cutover work package to 2 December and note why. With the actions granted, Memtro changes the due date and adds the comment as the token's user, both sent with notifications off, so nobody is emailed.
The teams that lean on OpenProject most, a question each of them asks, and what they connect beside it.
A record in OpenProject 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.
An administrator allows API tokens in OpenProject under Administration → API and webhooks
As a dedicated OpenProject user, a member of only the projects Memtro should see, open avatar → My account → Access tokens → API → Generate. The token carries all of that user's permissions, so its role decides which granted actions can work
In Connections → OpenProject in Memtro type the Host name only, with no https://, path or port (Cloud is <name>.openproject.com), add the sub-path if any, and paste the API token
Ask which work packages changed in the Platform project this week
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The OpenProject tools are the same everywhere.
Only when you ask, and only what it has been granted: create a work package in a project; comment on a work package; log time on a work package; change a work package's subject, description, status, assignee, priority or dates; delete a work package; relate two work packages (blocks, follows, duplicates and so on); remove a relation between work packages; add a watcher to a work package; remove a watcher from a work package; correct a logged time entry; delete a logged time entry; edit a comment on a work package; create a version; change a version's name, dates, status or sharing; create a project; rename, re-describe, archive or unarchive a project; delete a project and everything in it (permanent); create a meeting; lock a user account; unlock a user account. 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 OpenProject records into memory as entities.
Host and API token. An administrator allows API tokens in OpenProject under Administration → API and webhooks.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in OpenProject, choosing the same kinds; the tab shows OpenProject'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