taskadence-mcp vs MCP Stdio
taskadence-mcp is an MCP server published by indrasol. Marketplaces we read that list it: 1 (PyPI (MCP servers)). MCP Stdio is an MCP server published by shigechika. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-07. 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 |  taskadence-mcp |  MCP Stdio |
|---|---|---|
| PyPI (MCP servers) | Listed Version: 2.0.0 Downloads/month (PyPI): 0 Downloads/week (PyPI): 133 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.45.2 Downloads/month (PyPI): 3 212 Downloads/week (PyPI): 283 Forks (GitHub): 2 Stars (GitHub): 9 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 | taskadence-mcp | MCP Stdio |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (worse) | 9 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 2 (better) |
| Last release (differs) | 2026-10-28 (better) | 2026-10-26 (worse) |
| Where it runs (differs) | On your machine (taskadence-mcp) | On your machine (mcp-stdio) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/indrasol/taskadence-python | github.com/shigechika/mcp-stdio |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-13 | 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
taskadence-mcp
The TasKadence MCP server for clients that start a local process: a stdio proxy to the remote server (uvx taskadence-mcp).
MCP Stdio
Stdio-to-HTTP gateway — connects MCP clients to remote HTTP MCP servers
How to run each
taskadence-mcp
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
MCP Stdio As a local MCP server: PyPI package
claude mcp add --transport stdio mcp-stdio -- uvx mcp-stdioCommands 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
Neither one's marketplaces publish the settings it asks for.
What it can do: taskadence-mcp · What it can do: MCP Stdio · Compare two other plugins
Package data comes from the Python Package Index (pypi.org). 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.