Kanboard MCP server

What the model can do

Kanboard projects, tasks per project with column, assignee, due date and time, task search with Kanboard's query syntax, a task's comments and subtasks, and your overdue tasks; can also create, change, close, reopen or remove tasks, add, edit or remove comments, add or change subtasks, move a task on its board or to another project, copy a task, set a task's tags, link tasks, create, change, archive, reactivate or remove projects, add columns, categories and tags, and deactivate a user when you ask.

Reads

• kanboard_list_projectsKanboard projects this user is a member of: id (needed by every task tool), name, identifier, whether active, and the board link.
• kanboard_list_tasksTasks in one Kanboard project, open (active) by default or closed, with column, assignee id, due date, time and the start of the description.
• kanboard_search_tasksSearch tasks in one Kanboard project with Kanboard's query syntax: words in the title, or filters such as assignee:me, status:open, due:tomorrow…
• kanboard_get_taskOne Kanboard task in full with its comments and subtasks.
• kanboard_my_overdue_tasksThis user's overdue Kanboard tasks across projects: title, project, due date and assignee.
• kanboard_list_columnsThe columns of one Kanboard project's board, in order: id (for kanboard_move_task_position and create_task), title…
• kanboard_list_swimlanesThe swimlanes of one Kanboard project: id (for kanboard_move_task_position), name, position and whether active.
• kanboard_list_usersKanboard users: id (for assignees and owners), username, name, role and whether active.

Acts, when you ask

These change something in Kanboard. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• kanboard_create_taskCreate a task in a Kanboard project, with this connection's user as its creator.
• kanboard_add_commentAdd a comment to a Kanboard task, as this connection's user.
• kanboard_add_subtaskAdd a subtask (a checklist item) to a Kanboard task.
• kanboard_update_subtaskChange an existing Kanboard subtask: title, who does it, status (todo, in progress, done) or hours estimated or spent.
• kanboard_update_taskChange an existing Kanboard task: title, description, assignee, due date, priority or tags.
• kanboard_close_taskClose a Kanboard task (mark it done).
• kanboard_reopen_taskReopen a closed Kanboard task.
• kanboard_remove_taskREMOVE (delete) a Kanboard task with its comments, subtasks and files.
• kanboard_remove_commentREMOVE (delete) one comment from a Kanboard task.
• kanboard_move_task_positionMove a Kanboard task to another column, position or swimlane on its own project's board.
• kanboard_move_task_to_projectMove a Kanboard task out of its project into another project.
• kanboard_duplicate_task_to_projectCopy a Kanboard task into a project (the same or another).
• kanboard_update_commentReplace the text of a Kanboard comment this connection's user wrote.
• kanboard_create_projectCreate a Kanboard project (a new board with the default columns).
• kanboard_update_projectChange a Kanboard project's name, description, owner, identifier or dates.
• kanboard_disable_projectDisable (archive) a Kanboard project: it leaves the active boards but keeps every task.
• kanboard_enable_projectReactivate a disabled Kanboard project.
• kanboard_remove_projectREMOVE (delete) a Kanboard project with every task, comment, subtask and file in it.
• kanboard_add_columnAdd a column to the end of a Kanboard project's board.
• kanboard_create_categoryCreate a task category in a Kanboard project.
• kanboard_create_tagCreate a tag in a Kanboard project, for use on its tasks.
• kanboard_set_task_tagsSet a Kanboard task's tags.
• kanboard_create_task_linkLink two Kanboard tasks (for example one blocks the other).
• kanboard_disable_userDeactivate a Kanboard user so they can no longer sign in; their tasks and comments stay.

Connect it

First connect Kanboard on Dashboard → Connections, then add Memtro to your client once. The Kanboard tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Kanboard connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › 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

Questions

Is this an official Kanboard MCP server?

No. It is Memtro's MCP server with Memtro's Kanboard connector behind it: the connector reads Kanboard through its API with the credentials you connect on Dashboard → Connections, and Kanboard publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Kanboard?

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. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Work management

• Clio Manage MCP server
• Linear MCP server
• Jira MCP server
• Asana MCP server
• monday.com MCP server
• Airtable MCP server