Compose MCP vs m-dev-tools
Compose MCP is an MCP server published by smartmemory.ai. Marketplaces we read that list it: 1 (Official MCP Registry). m-dev-tools is an MCP server published by m-dev-tools. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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 |  m-dev-tools | |
|---|---|---|
| Official MCP Registry | Listed Version: 0.7.2 Downloads/month (npm): 2 070 Downloads/week (npm): 94 Not marked · First seen |
Listed Version: 0.2.4 Downloads/month (PyPI): 49 Downloads/week (PyPI): 11 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 | Compose MCP | m-dev-tools |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 1 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@smartmemory/compose-mcp) | On your machine (m-dev-tools-mcp) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/m-dev-tools/m-dev-tools-mcp |
| Changes in the last 7 days | 0 | 0 |
| 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
Compose MCP
Typed feature management for compose projects: roadmap, changelog, artifacts, journal.
m-dev-tools
MCP server wrapping the m-dev-tools catalog: route_intent, describe, verify.
How to run each
Compose MCP As a local MCP server: npm package
claude mcp add --transport stdio compose-mcp -- npx -y @smartmemory/compose-mcpm-dev-tools As a local MCP server: PyPI package
claude mcp add --transport stdio m-dev-tools-mcp -- uvx m-dev-tools-mcpCommands 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: Compose MCP · What it can do: m-dev-tools · 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.