Vikunjamcp

io.github.idjohnsonPublished by GitHub account idjohnsonv1.0.26Updated Oct 24, 2026

An MCP server that provides access to Vikunja, a self-hosted task management solution.

VerifiedSTDIODesktop onlyProductivity & Workflow

Server details

Identifier: io.github.idjohnson/vikunjamcp
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account idjohnson for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.idjohnson%2Fvikunjamcp.svg)](https://sourceweft.com/mcp/io.github.idjohnson%2Fvikunjamcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

An MCP server that lets an assistant read and manage tasks in a self-hosted Vikunja task management instance.

What you can do: This server connects an assistant to Vikunja, a self-hosted task management solution, so tasks and related project data can be accessed through MCP tools. The manifest does not list individual tools, so the exact set of operations is not documented here. It runs locally over stdio and talks to a Vikunja instance you provide.
When to use it: Useful if you already run Vikunja and want an assistant to work with your tasks and projects without leaving the chat. It is not for people who do not have a Vikunja instance, since it only connects to one you supply.
Requirements: A local container runtime to run the Docker image, plus a reachable Vikunja instance. Required settings: VIKUNJA_URL, VIKUNJA_USERNAME, and the secret VIKUNJA_PASSWORD. Desktop only; no remote or web endpoint is offered.

Before you install

The server needs your Vikunja account credentials, including the secret VIKUNJA_PASSWORD, so treat that value as sensitive and prefer a dedicated account. Depending on the tools it exposes, it may create, change, or delete tasks and projects in your instance; the manifest does not document which operations are available.

Installation

In SourceWeft

Open Vikunjamcp in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v1.0.26LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
License10 pts
Declare a license in the repository or the registry entry.