Clearing the backlog
On Friday the operations lead asks what is overdue. Memtro reads this user's overdue tasks across projects and lists five with their project and due date, two of them in the Northwind fit-out board.
Ask what is overdue on your Kanboard boards, and what sits in each column.
Connect Kanboard with your host name, a username and a personal access token and Memtro reads projects, tasks with column, assignee, due date and time, a task's comments and subtasks, and your overdue tasks. It works as that user, with all of the user's access, and there is no hourly sync. When you ask, and once an administrator has granted them by name, it can create, change, move, copy, close and reopen tasks, comment, add subtasks and tags, create, change or archive projects and columns, and deactivate a user. Removing a task, a comment or a whole project is permanent.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Kanboard tool, reads what it needs, and answers with the source cited.
These tools change something in Kanboard. 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 Kanboard, choosing the same kinds; the tab shows Kanboard's own steps. Each event can start a job, with the event as its input. Kanboard sends a secret with every delivery, and one without it is refused.
Events and webhooksOnce Kanboard 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 my tasks are overdue?
What is in the Work in progress column of the Website board?
What subtasks are left on the Acme launch task?
Move the Acme launch task to Done and close it
Copy the Northwind onboarding task into the Globex project
On Friday the operations lead asks what is overdue. Memtro reads this user's overdue tasks across projects and lists five with their project and due date, two of them in the Northwind fit-out board.
Dan Fletcher asks Memtro to close the finished invoice run task, move the payroll check back to In progress and assign it to Priya Sharma. With the actions granted, Memtro does each as the connected Kanboard user, and everyone on the board sees the changes.
The teams that lean on Kanboard most, a question each of them asks, and what they connect beside it.
A record in Kanboard 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.
Create a dedicated Kanboard user for Memtro, a member of only the projects it should see, and make a personal access token from the user's profile. Project changes need the project manager role
Use that username, not jsonrpc. Servers with a custom API authentication header cannot connect, and three failed logins lock the account
In Connections → Kanboard in Memtro type the Host name only, with no https://, path or port, add the sub-path if any, then the Username and Personal access token
Ask which of your tasks are overdue
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Kanboard tools are the same everywhere.
Only when you ask, and only what it has been granted: create a task in a project; add a comment to a task; add a subtask to a task; change a subtask's title, assignee, status or time; change a task's title, description, assignee, due date, priority or tags; close a task; reopen a closed task; remove a task; remove a comment; move a task to another column, position or swimlane; move a task to another project; copy a task into another project; edit the text of your own comment; create a project; change a project's name, description, owner, identifier or dates; archive (disable) a project; reactivate a disabled project; remove a project and everything in it; add a column to a board; create a category in a project; create a tag in a project; set a task's tags; link two tasks; deactivate a Kanboard user. 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.
Host, username and personal access token. Create a dedicated Kanboard user for Memtro, a member of only the projects it should see, and make a personal access token from the user's profile. Project changes need the project manager role.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Kanboard, choosing the same kinds; the tab shows Kanboard'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