Triage before lunch
The support lead asks which Northwind issues were updated since yesterday. Memtro lists six with tracker, status and assignee, and quotes the newest note on each, flagging one bug that is still unassigned at urgent priority.
Ask which Redmine issues are open, who has them and what changed.
Connect Redmine with your host name and an API access key and Memtro reads projects, issues with tracker, status, assignee and dates, notes and history, time entries, members, versions and search. Memtro talks to your own server. The hourly sync writes issues that changed into memory. When you ask, and once an administrator has granted them by name, it can create and change issues, add notes and watchers, log time, manage versions and projects, publish news and add members. Redmine emails people under its own settings, and deleting an issue, version or project is permanent.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Redmine tool, reads what it needs, and answers with the source cited.
These tools change something in Redmine. 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 Redmine, choosing the same kinds; the tab shows Redmine's own steps. Each event can start a job, with the event as its input. Redmine signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Redmine 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 open bugs in the Support project have no assignee?
What notes were added to issue 8812 this week?
How many hours did Dan Fletcher log in October?
Add a note to issue 8812 that the fix ships on Thursday
Close issue 8790 and assign it back to Priya Nair
The support lead asks which Northwind issues were updated since yesterday. Memtro lists six with tracker, status and assignee, and quotes the newest note on each, flagging one bug that is still unassigned at urgent priority.
Priya Nair asks Memtro to add a note to the Acme login issue that a patch is on staging, and to add Tom Reyes as a watcher. Memtro adds both as her connection's user, and Redmine emails the watchers and the assignee under its own settings.
The teams that lean on Redmine most, a question each of them asks, and what they connect beside it.
A record in Redmine 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 ticks Administration → Settings → API → Enable REST web service in Redmine
Create a dedicated Redmine user for Memtro, a member of only the projects it should see, with roles that allow only the changes you will grant, and copy its key from My account → API access key → Show
In Connections → Redmine in Memtro type your Host name only, with no https://, path or port, add the sub-path if any, and paste the API access key
Ask which open issues in the Support project have no assignee
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Redmine tools are the same everywhere.
Only when you ask, and only what it has been granted: create an issue in a project; add a note to an issue; log time on an issue; change an issue's subject, description, status, priority or assignee; delete an issue; delete a time entry; correct a logged time entry; relate two issues (blocks, precedes, duplicates and so on); remove a relation between issues; add a watcher to an issue; remove a watcher from an issue; create a version; change a version's name, due date, status or sharing; delete a version; create a project; change a project's name, description or homepage; archive or unarchive a project; delete a project and everything in it (permanent); publish a news item in a project; add a member to a project with roles; remove a member from a project. 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 Redmine records into memory as entities.
Host and API access key. An administrator ticks Administration → Settings → API → Enable REST web service in Redmine.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Redmine, choosing the same kinds; the tab shows Redmine'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