m-dev-tools MCP server
✓ VerifiedEnables AI agents to discover, describe, and verify tools within the m-dev-tools catalog using intent routing and manifest lookups.
Also known as m-dev-tools/m-dev-tools-mcp, m-dev-tools-mcp
- Stars
- 1
- Tools
- 3
- Downloads, 30 days
- 87
- Latest version
- 0.2.4
- Last commit
- Aug 3, 2026
- License
- AGPL-3.0
What is m-dev-tools MCP?
m-dev-tools enables AI agents to discover, describe, and verify tools within the m-dev-tools catalog using intent routing and manifest lookups. It exposes 3 tools, such as route_intent, describe, verify.
Summary generated from the project's README
About m-dev-tools MCP server
Helping AI agents navigate and validate a specific catalog of development tools is the primary function of m-dev-tools. Developers using MCP clients can connect to this server to allow their agents to find the correct modules for specific tasks through natural language queries. The server acts as a thin wrapper that fetches data directly from the m-dev-tools organization catalog over the network during runtime rather than relying on a local cache.
Agents interact with the catalog using three specific tools: route_intent for converting plain-English requests into typed IDs, describe for retrieving manifest URLs and verification commands via a typed ID, and verify for listing declared verification commands within a repository. This setup requires no local database since it reads the catalog at call time. Users can install the package via pip or uvx and configure their client to point to the m-dev-tools-mcp binary.
What you can do with it
- 1Translate natural language to tool IDsAsk an agent to find the specific module ID needed to parse JSON in the M language.
- 2Retrieve tool documentation and manifestsRequest the manifest URL and verification commands for a specific typed tool ID.
- 3Audit repository verification commandsCheck which verification commands a specific repository has declared without actually running them.
Written from the project's README. Every use case is checked against a quote from it.
How to install m-dev-tools MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall m-dev-tools MCP in Claude Code
$ claude mcp add m-dev-tools-mcp -- uvx m-dev-tools-mcpInstall m-dev-tools MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"m-dev-tools-mcp": {
"command": "uvx",
"args": [
"m-dev-tools-mcp"
]
}
}
}Install m-dev-tools MCP in VS Code
.vscode/mcp.json
{
"servers": {
"m-dev-tools-mcp": {
"type": "stdio",
"command": "uvx",
"args": [
"m-dev-tools-mcp"
]
}
}
}Install m-dev-tools MCP in VS Code CLI
$ code --add-mcp '{"name":"m-dev-tools-mcp","type":"stdio","command":"uvx","args":["m-dev-tools-mcp"]}'Install m-dev-tools MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"m-dev-tools-mcp": {
"command": "uvx",
"args": [
"m-dev-tools-mcp"
]
}
}
}Install m-dev-tools MCP in Codex
$ codex mcp add m-dev-tools-mcp -- uvx m-dev-tools-mcpInstall m-dev-tools MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.m-dev-tools-mcp] command = "uvx" args = ["m-dev-tools-mcp"]
Install m-dev-tools MCP in Gemini CLI
$ gemini mcp add -s user m-dev-tools-mcp uvx -- m-dev-tools-mcpInstall m-dev-tools MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"m-dev-tools-mcp": {
"command": "uvx",
"args": [
"m-dev-tools-mcp"
]
}
}
}m-dev-tools MCP tools 3
Detected from the READMEroute_intentdescribeverify
| route_intent | — | |
| describe | — | |
| verify | — |
Automated checks
Ran Nov 15, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachablem-dev-tools/m-dev-tools-mcp is public and reachablegithub.com/m-dev-tools/m-dev-tools-mcp ↗Pass
- Package names this repository as its sourcem-dev-tools-mcp names m-dev-tools/m-dev-tools-mcp as sourcepypi.org/project/m-dev-tools-mcp/ ↗Pass
- Build provenance (Sigstore attestation)Sigstore attestation for m-dev-tools-mcppypi.org/project/m-dev-tools-mcp/ ↗Pass
- Open source license (OSI)AGPL-3.0spdx.org/licenses/AGPL-3.0.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-08-03github.com/m-dev-tools/m-dev-tools-mcp ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from m-dev-tools-mcpPass
- No critical advisory in the package or its dependencies30 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model3 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNo tool named like delete, drop or execPass
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubm-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.mdURL, 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.Zonmain→.github/workflows/release.ymlbuilds 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.
m-dev-tools MCP questions
How do I add m-dev-tools MCP to Claude Code?
Run claude mcp add m-dev-tools-mcp -- uvx m-dev-tools-mcp in your terminal. Add --scope user to make it available in every project.
How do I add m-dev-tools MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does m-dev-tools MCP provide?
It exposes 3 tools, including route_intent, describe, verify.
What tools does the server provide?
The server exposes three primary tools: route_intent for mapping plain-English queries to typed IDs, describe for retrieving manifest and verification details, and verify for listing a repository's declared verification commands.
Does the server cache the catalog locally?
No, the server is a thin wrapper that reads the catalog from GitHub over the network at the time of the call.
Does the verify tool execute commands?
No, the verify tool only lists the declared verification commands for a repository without running them.