midas-mcp

MCP stdio proxy for MIDAS. Lets a local AI assistant (Claude Code / IDE) drive a remote MIDAS instance as tools. Stateless — it forwards each tool call to MIDAS's REST API; the remote MIDAS is the single source of truth.

Install (one command, no clone)

claude mcp add -s user midas -- npx -y @attract.alex.kim/midas-mcp

That registers the proxy once for your machine. npx fetches it from npm and caches it.

Point it at a project's MIDAS

A developer may have many projects, each with its own MIDAS. The proxy reads the instance from the project it is launched in — drop a .midas.json at the project root:

{ "url": "https://midas-project-a.example.com", "user": "ivan" }

Fields: url (required), user (recorded on approve/reject), token (optional Bearer — inert until REST auth is added). The proxy walks up from the current directory to find the nearest .midas.json. You can commit it into each project repo.

Override per launch with env: MIDAS_URL, MIDAS_USER, MIDAS_TOKEN (env wins over the file).

Tools

midas_ask, midas_reply, midas_get_conversation, midas_create_task, midas_get_task, midas_list_approvals, midas_approve, midas_reject, midas_onboarding_scan.

Security

The MIDAS REST API is unauthenticated today — keep the remote instance on a private network / VPN.

Build (maintainers)

npm install && npm run build → bundles nestjs/src/mcp/* into dist/index.js (@modelcontextprotocol/sdk inlined, zero runtime deps). npm publish to release.