io.github.dinof777/mission-control vs io.github.idjohnson/vikunjamcp
io.github.dinof777/mission-control is an MCP server published by dinof777. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.idjohnson/vikunjamcp is an MCP server published by idjohnson. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. 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 |  io.github.dinof777/mission-control | |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.0 No figure published Not marked · First seen |
Listed Version: 1.0.26 No figure published 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.dinof777/mission-control | io.github.idjohnson/vikunjamcp |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mission-control-six-kohl.vercel.app/api/mcp) | On your machine (docker.io/idjohnson/vikunjamcp:0.26) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 3, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/dinof777/mission-control | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 4 days ago, requires a key | no remote endpoint we check |
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.dinof777/mission-control
Read and write Mission Control state via MCP — projects, tasks, subtasks, templates, status updates.
io.github.idjohnson/vikunjamcp
An MCP server that provides access to Vikunja, a self-hosted task management solution.
How to run each
io.github.dinof777/mission-control As a remote MCP server
claude mcp add --transport http mission-control https://mission-control-six-kohl.vercel.app/api/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
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
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.dinof777/mission-control 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
The marketplaces of io.github.dinof777/mission-control publish no settings it asks for, so we do not compare settings.
What it can do: io.github.dinof777/mission-control · What it can do: io.github.idjohnson/vikunjamcp · 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.