io.github.SuperAngryMonkey/kairos vs io.github.starecz/karea-mcp
io.github.SuperAngryMonkey/kairos is an MCP server published by SuperAngryMonkey. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.starecz/karea-mcp is an MCP server published by starecz. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). 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 | ||
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.0 Downloads/month (PyPI): 285 Downloads/week (PyPI): 30 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.14.0 Downloads/month (npm): 1 567 Downloads/week (npm): 714 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 0.14.0 Downloads/month (npm): 1 567 Downloads/week (npm): 714 Forks (GitHub): 0 Stars (GitHub): 1 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.SuperAngryMonkey/kairos | io.github.starecz/karea-mcp |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 0 (worse) | 1 (better) |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | Not published | 2026-10-24 |
| Where it runs (differs) | On your machine (kairos-mcp) | On your machine (karea-mcp) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 4, secrets among them: 0 | 2, secrets among them: 1 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/superangrymonkey/kairos | github.com/starecz/karea-mcp |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
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.SuperAngryMonkey/kairos
Microsoft Planner MCP: create tasks and buckets, list plans and tasks, complete tasks.
io.github.starecz/karea-mcp
Karea task manager - 9 tools covering 70 actions, for Claude Code, Cursor, and other MCP clients.
How to run each
io.github.SuperAngryMonkey/kairos As a local MCP server: PyPI package
claude mcp add --env "KAIROS_CLIENT_ID=<YOUR_KAIROS_CLIENT_ID>" --transport stdio kairos -- uvx kairos-mcp
Requires: KAIROS_CLIENT_ID
io.github.starecz/karea-mcp As a local MCP server: npm package
claude mcp add --env "KAREA_API_KEY=<YOUR_KAREA_API_KEY>" --transport stdio karea-mcp -- npx -y karea-mcp
Requires: KAREA_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
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.SuperAngryMonkey/kairos asks for
KAIROS_CLIENT_IDKAIROS_CONFIG_DIRKAIROS_DEFAULT_PLANKAIROS_TENANT_ID
Only io.github.starecz/karea-mcp asks for
KAREA_API_KEY (secret)KAREA_URL
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: io.github.SuperAngryMonkey/kairos · What it can do: io.github.starecz/karea-mcp · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.