mcpField
M
m-dev-tools

m-dev-tools

Local
github.comDeveloper Tools1Updated 13w ago
RepositoryVisit website

About m-dev-tools

m-dev-tools is an MCP server that provides access to the m-dev-tools organization catalog. It helps agents map natural-language intent to typed IDs, retrieve catalog pointers, and inspect a repository’s declared verification commands without running them.

Key features

  1. 01Route natural-language intent to typed IDs
  2. 02Retrieve manifest and AGENTS.md pointers
  3. 03List repository verification commands
  4. 04Read catalog data over the network at call time

Use cases

  1. 01Find a catalog module from a plain-English task
  2. 02Retrieve guidance and manifest links for a typed ID
  3. 03Check a repository's declared verification commands
  4. 04Look up current catalog entries during agent work

MCP support

The MCP server exposes three tools: `route_intent`, `describe`, and `verify`. It fetches the catalog over the network when called rather than using a local cache.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "m-dev-tools-m-dev-tools": {
      "command": "uvx",
      "args": [
        "m-dev-tools-mcp"
      ]
    }
  }
}
Run commanduvx m-dev-tools-mcp

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
pypim-dev-tools-mcp0.2.4

Tools

3

Saved tool list · updated 3w ago

ParameterTypeRequiredDescription
querystringYes

Details

From the project README

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.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.