MCP server wrapping the m-dev-tools catalog: route_intent, describe, verify.
Use this profile to copy client config, check auth requirements, review tools and resources, and compare related MCP servers before adding it to an AI client.
uvx m-dev-tools-mcpAdd this server entry to the mcpServers object in your Claude Desktop config, then restart the app.
{
"mcpServers": {
"io-github-m-dev-tools-m-dev-tools-mcp": {
"command": "uvx",
"args": [
"m-dev-tools-mcp"
]
}
}
}~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonNo remote HTTP endpoint is advertised. Use the package or stdio setup shown in Install.
m-dev-tools is an MCP server for MCP server wrapping the m-dev-tools catalog: route_intent, describe, verify.. It supports STDIO transport.
Use the generated config in Install. This server runs with uvx m-dev-tools-mcp; add any required environment variables before starting your client.
Choose the Claude Desktop tab in Install and copy the config for uvx m-dev-tools-mcp. Add required environment variables before starting Claude Desktop.
Choose the Claude Code tab in Install and copy the config for uvx m-dev-tools-mcp. Add required environment variables before starting Claude Code.
Choose the Codex tab in Install and copy the config for uvx m-dev-tools-mcp. Add required environment variables before starting Codex.
Choose the Cursor or VS Code tab in Install and copy the config for uvx m-dev-tools-mcp. Add required environment variables before starting Cursor or VS Code.
m-dev-tools uses STDIO transport. Use the package or command config in Install.
m-dev-tools inventory is listed when the MCP endpoint exposes tools, resources, or prompts. Some servers require auth first.
m-dev-tools does not advertise a verified auth requirement. If discovery fails, it may still need provider login, an API key, a bearer token, or a session header.
| Package | Registry | Version | Inputs |
|---|---|---|---|
m-dev-tools-mcpstdio | pypi | 0.2.4 | None advertised |