m-dev-tools vs md.install/try
m-dev-tools is an MCP server published by m-dev-tools. Marketplaces we read that list it: 1 (Official MCP Registry). md.install/try is an MCP server published by install.md. 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 |  m-dev-tools |  md.install/try |
|---|---|---|
| Official MCP Registry | Listed Version: 0.2.4 Downloads/month (PyPI): 49 Downloads/week (PyPI): 22 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 0.1.1 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 | m-dev-tools | md.install/try |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 1 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (m-dev-tools-mcp) | Remote server (install.md/mcp/try) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/m-dev-tools/m-dev-tools-mcp | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 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
m-dev-tools
MCP server wrapping the m-dev-tools catalog: route_intent, describe, verify.
md.install/try
Create guides as MCP servers to instruct coding agents to use your software (library, API, etc).
How to run each
m-dev-tools As a local MCP server: PyPI package
claude mcp add --transport stdio m-dev-tools-mcp -- uvx m-dev-tools-mcpmd.install/try As a remote MCP server
claude mcp add --transport http try https://install.md/mcp/tryCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only md.install/try 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
Neither one's marketplaces publish the settings it asks for.
What it can do: m-dev-tools · What it can do: md.install/try · 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.