io.github.idjohnson/vikunjamcp vs Microsoft Todo
io.github.idjohnson/vikunjamcp is an MCP server published by idjohnson. Marketplaces we read that list it: 1 (Official MCP Registry). Microsoft Todo is an MCP server published by pipeworx-io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Microsoft Todo | |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.26 No figure published Not marked · First seen |
Listed Version: 0.2.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | io.github.idjohnson/vikunjamcp | Microsoft Todo |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 0 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release (differs) | Not published | 2026-10-29 |
| Where it runs (differs) | On your machine (docker.io/idjohnson/vikunjamcp:0.26) | Remote server (gateway.pipeworx.io/microsoft-todo/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 1 | 1, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/pipeworx-io/mcp-microsoft-todo |
| Changes in the last 7 days (differs) | 0 | 4 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Answered with HTTP 404 (5 days ago) |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
io.github.idjohnson/vikunjamcp
An MCP server that provides access to Vikunja, a self-hosted task management solution.
Microsoft Todo
Microsoft To Do (Microsoft 365) MCP Pack
How to run each
io.github.idjohnson/vikunjamcp As a local MCP server: Docker image
claude mcp add --env "VIKUNJA_PASSWORD=<YOUR_VIKUNJA_PASSWORD>" --env "VIKUNJA_URL=<YOUR_VIKUNJA_URL>" --env "VIKUNJA_USERNAME=<YOUR_VIKUNJA_USERNAME>" --transport stdio vikunjamcp -- docker run -i --rm -e VIKUNJA_PASSWORD -e VIKUNJA_URL -e VIKUNJA_USERNAME docker.io/idjohnson/vikunjamcp:0.26Requires: VIKUNJA_PASSWORD (secret), VIKUNJA_URL, VIKUNJA_USERNAME
Microsoft Todo As a remote MCP server
claude mcp add --transport http microsoft-todo https://gateway.pipeworx.io/microsoft-todo/mcpRequires: PIPEWORX_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Microsoft Todo has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only io.github.idjohnson/vikunjamcp asks for
VIKUNJA_PASSWORD (secret)VIKUNJA_URLVIKUNJA_USERNAME
Only Microsoft Todo asks for
PIPEWORX_API_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: io.github.idjohnson/vikunjamcp · What it can do: Microsoft Todo · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.