Vikunja MCP server

What the model can do

Vikunja projects and tasks (due dates, priority, assignees, labels, done state) across projects with Vikunja's filters, a task's comments, labels and users; can also create, change, copy, link and delete tasks, move them between kanban columns, add or delete comments, assign or unassign people, create, attach or detach labels, create, change, archive, share and delete projects, and add kanban columns when you ask.

Reads

• vikunja_list_projectsVikunja projects the token's user can see: id (needed to list or create tasks), title, identifier, parent project and description.
• vikunja_list_tasksVikunja tasks across every project the user can see, or one project: title, key, done, due date, priority, assignees…
• vikunja_get_taskOne Vikunja task in full (description up to 4,000 characters) with its comments.
• vikunja_find_usersFind Vikunja users by name or username, for their user id (to assign them).
• vikunja_list_labelsLabels the user can see, with ids, titles and colours, for labelling a task.
• vikunja_list_project_viewsThe views of one Vikunja project (list, gantt, table, kanban) with their ids, and for a kanban view its buckets (columns) with ids, titles and limits.

Acts, when you ask

These change something in Vikunja. 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.

• vikunja_create_taskCreate a task in a Vikunja project.
• vikunja_add_assigneeAssign a person to a Vikunja task.
• vikunja_remove_assigneeREMOVE a person from a Vikunja task's assignees.
• vikunja_create_labelCreate a new Vikunja label, owned by the token's user.
• vikunja_add_labelAttach an existing label to a Vikunja task.
• vikunja_remove_labelREMOVE a label from a Vikunja task (the label itself is kept).
• vikunja_add_commentAdd a comment to a Vikunja task, as the token's user.
• vikunja_update_taskChange an existing Vikunja task: title, description, due date, priority, percent done, or mark it done or not done.
• vikunja_delete_taskDELETE a Vikunja task with its comments and attachments.
• vikunja_delete_commentDELETE one comment from a Vikunja task.
• vikunja_create_projectCreate a Vikunja project, owned by the token's user, optionally under a parent project.
• vikunja_update_projectChange a Vikunja project: title, description, identifier, colour, parent project, or archive or unarchive it…
• vikunja_delete_projectDELETE a Vikunja project together with all its sub-projects and every task in them.
• vikunja_duplicate_taskCopy a Vikunja task into the same project with its labels, assignees, attachments and reminders, linked to the original by a "copied from" relation.
• vikunja_add_task_relationLink two Vikunja tasks: subtask, parenttask, related, duplicateof, duplicates, blocking, blocked, precedes, follows, copiedfrom or copiedto…
• vikunja_remove_task_relationRemove a link between two Vikunja tasks (the tasks themselves are kept).
• vikunja_move_task_to_bucketMove a Vikunja task to another column (bucket) of a project's kanban view (ids from vikunja_list_project_views).
• vikunja_create_bucketAdd a column (bucket) to a Vikunja project's kanban view, optionally with a limit on how many tasks it may hold.
• vikunja_share_projectChanges access.
• vikunja_unshare_projectChanges access.

Connect it

First connect Vikunja on Dashboard → Connections, then add Memtro to your client once. The Vikunja 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 Vikunja 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 tasks are due in the next seven days?
• › What high-priority tasks are still open in the Office move project?
• › What are the comments on the printer replacement task?
• › Assign Priya Nair to the supplier contracts task
• › Share the Office move project with Tom Reyes as read only

Questions

Is this an official Vikunja MCP server?

No. It is Memtro's MCP server with Memtro's Vikunja connector behind it: the connector reads Vikunja through its API with the credentials you connect on Dashboard → Connections, and Vikunja 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 Vikunja?

Only when you ask, and only what it has been granted: create a task in a Vikunja project, optionally assigned and labelled; add a comment to a task; change a task's title, description, due date, priority, progress or done state; delete a task; delete a comment on a task; assign a person to a task; remove a person from a task's assignees; create a label; attach a label to a task; remove a label from a task; create a project; rename, re-describe, move, archive or unarchive a project; delete a project with its sub-projects and tasks (trash, permanent after 30 days); copy a task; link two tasks (subtask, blocking, related, duplicate and so on); remove a link between two tasks; move a task to another kanban column; add a kanban column; share a project with a user (read, write or admin); remove a user's access to a project. 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