Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
m-dev-tools avatar

M Dev Tools

  • Updated May 11, 2026
  • m-dev-tools/m-dev-tools-mcp

m-dev-tools-mcp is a MCP server that wraps the m-dev-tools catalog so agents can route_intent, describe, and verify developer utilities.

About

io.github.m-dev-tools/m-dev-tools-mcp is a Model Context Protocol server that exposes the m-dev-tools catalog to AI coding assistants. developers and small teams use it when an agent needs to match a task to the right CLI, library, or workflow utility instead of guessing from memory. The server surfaces route_intent for mapping what you want to do, describe for structured tool metadata, and verify for sanity-checking a candidate before install or config changes. It ships as a PyPI package runnable via uvx over stdio, which aligns with typical Claude Code and Cursor MCP setups. It is not a general web browser or database connector—it is a narrow developer-catalog bridge. For Skillselion readers, treat it as agent-side tooling during Build: register it once, then invoke catalog lookups inside the same session where you are editing repos, Dockerfiles, or package manifests.

  • 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

M Dev Tools by the numbers

  • Data as of Jul 7, 2026 (Skillselion catalog sync)
terminal
claude mcp add m-dev-tools-mcp -- uvx m-dev-tools-mcp

Add your badge

Show developers this MCP server is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Packagem-dev-tools-mcp
TransportSTDIO
AuthNone
Last updatedMay 11, 2026
Repositorym-dev-tools/m-dev-tools-mcp

What it does

Let your coding agent query the m-dev-tools catalog to route intents, describe tools, and verify choices while you wire up a stack.

Who is it for?

Best when you want MCP-backed catalog lookups while scaffolding agents, CLIs, or integration-heavy repos.

Skip if: Skip if you only need one fixed stack with no tool discovery, or developers and want cloud provisioning rather than dev-tool routing.

What you get

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

By the numbers

  • 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
README.md

m-dev-tools-mcp

MCP server for the m-dev-tools org catalog. Exposes three first-class agent tools:

  • route_intent(query) — plain-English intent → typed IDs (e.g. "parse JSON in M"module:m-stdlib#STDJSON)
  • describe(typed_id) — typed ID → pointer-blob (manifest URL, AGENTS.md URL, verification commands, …)
  • verify(repo) — list a repo's declared verification commands (does not execute them)

The server reads the catalog at https://github.com/m-dev-tools/.github over the network at call time; it is a thin wrapper, not a cache. See AGENTS.md for the contract and the AI users guide for the full walk-through.

mcp-name: io.github.m-dev-tools/m-dev-tools-mcp

Install

pip install m-dev-tools-mcp
# or:
uvx m-dev-tools-mcp
# or from a GitHub Release wheel:
pip install https://github.com/m-dev-tools/m-dev-tools-mcp/releases/download/v0.2.4/m_dev_tools_mcp-0.2.4-py3-none-any.whl

Point any MCP client at the m-dev-tools-mcp binary the install provides:

{
  "mcpServers": {
    "m-dev-tools": { "command": "m-dev-tools-mcp" }
  }
}

Or for clients that consult the public MCP registry:

io.github.m-dev-tools/m-dev-tools-mcp

Develop

make install        # creates .venv and installs editable + dev deps
make test           # pytest
make check          # lint + mypy + test + check-manifest + check-agents
make build          # → wheel-out/m_dev_tools_mcp-<ver>-py3-none-any.whl

More

  • Architecture: m-dev-tools/.github's docs/ai-discoverability/AI-discoverability-architecture.md
  • Plan + phases: docs/ai-discoverability/phases/
  • Release process: tag vX.Y.Z on main.github/workflows/release.yml builds the wheel, attaches it to a GitHub Release, publishes to PyPI via Trusted Publisher OIDC, and updates the MCP registry record via GitHub OIDC.

License

AGPL-3.0. Same license as every other m-dev-tools repo.

Recommended MCP Servers

How it compares

MCP catalog bridge for dev utilities, not a cloud infrastructure or database server.

FAQ

Who is M Dev Tools-mcp for?

Developers 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.

Developer Toolsintegrationsdevops

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.