English Français العربية

m-dev-tools

Official registry Security

MCP server wrapping the m-dev-tools catalog: route_intent, describe, verify.

Source code Website Documentation

What can you do with m-dev-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)

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

PYPI package m-dev-tools-mcp
Claude Code 
claude mcp add m-dev-tools -- uvx m-dev-tools-mcp==0.2.4
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "m-dev-tools": {
            "command": "uvx",
            "args": [
                "m-dev-tools-mcp==0.2.4"
            ]
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. m-dev-tools-mcp
  2. Install
  3. Develop
  4. More
  5. License

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.

Frequently asked questions

What is m-dev-tools?

MCP server wrapping the m-dev-tools catalog: route_intent, describe, verify.

How do I install m-dev-tools?

It runs on your machine. In Claude Code: claude mcp add m-dev-tools -- uvx m-dev-tools-mcp==0.2.4. For other clients, paste the JSON configuration from this page into their MCP settings.

Does m-dev-tools need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is m-dev-tools open source?

Yes. Its code is on GitHub under the AGPL-3.0 license.

Who maintains m-dev-tools?

It is published by m-dev-tools. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.