M Dev Tools
Let your coding agent query the m-dev-tools catalog to route intents, describe tools, and verify choices while you wire up a stack.
Overview
m-dev-tools-mcp is a MCP server for the Build phase that wraps the m-dev-tools catalog so agents can route_intent, describe, and verify developer utilities.
What is this MCP server?
- Three catalog tools: route_intent, describe, and verify against the m-dev-tools registry
- PyPI package m-dev-tools-mcp v0.2.4 with uvx runtime hint and stdio transport
- Reduces wrong-tool picks by verifying catalog entries before you commit dependencies
- stdio MCP fits local agent configs without hosting a separate HTTP service
- Wraps the upstream m-dev-tools catalog maintained on GitHub
- Server version 0.2.4 on PyPI (m-dev-tools-mcp)
- stdio transport with uvx runtime hint
- Three documented catalog operations: route_intent, describe, verify
What problem does it solve?
Agents recommend generic or outdated dev tools because they lack a structured, verifiable catalog at decision time.
Who is it for?
Indie builders who want MCP-backed catalog lookups while scaffolding agents, CLIs, or integration-heavy repos.
Skip if: Teams that only need one fixed stack with no tool discovery, or builders who want cloud provisioning rather than dev-tool routing.
What do I get? / Deliverables
Your agent can query and verify m-dev-tools entries in-session so dependency and CLI choices align with a maintained registry.
- Working stdio MCP connection to route_intent, describe, and verify
- Agent-callable answers grounded in the m-dev-tools catalog
- Fewer mistaken installs from unverified tool suggestions
Recommended MCP Servers
Journey fit
Dev-tool discovery and verification belongs in Build because it runs while you are choosing libraries, CLIs, and agent-side utilities—not during go-to-market. Agent-tooling is the canonical shelf: stdio MCP exposes route_intent, describe, and verify directly to Claude Code, Cursor, and Codex during implementation.
How it compares
MCP catalog bridge for dev utilities, not a cloud infrastructure or database server.
Common Questions / FAQ
Who is M Dev Tools-mcp for?
Solo builders and agent users who want Claude Code, Cursor, or Codex to query the M Dev Tools catalog instead of hallucinating tool names.
When should I use M Dev Tools-mcp?
Use it during Build when you are picking CLIs, libraries, or workflow tools and need route_intent, describe, or verify before you install.
How do I add M Dev Tools-mcp to my agent?
Add a stdio MCP entry pointing at the PyPI package M Dev Tools-mcp (uvx runtime hint v0.2.4) in your Claude Code or Cursor MCP config, then restart the agent.