mendapi MCP server

mendapi

Dependabot, but for every API you depend on.

We watch your upstream API providers for breaking changes, scan your codebase for impact, and open the fix PR before your integration breaks.

30 seconds to your first result

# In any repo — zero config, zero npm dependencies
npx mendapi sync                          # one network call: fetch the change feed
npx mendapi scan --out impact.json        # local only, from here on
npx mendapi fix --from-report impact.json

sync pulls the upstream API change feed into a local SQLite database. It is the only command that touches the network, and you run it once (then whenever you want fresher data).

scan reports every upstream breaking change that actually hits your code — file, line, and symbol — scored for confidence. fix drafts the migration as a reviewable diff, without touching a single file until you pass --apply. Neither reads or writes anything outside your machine.

Using an AI coding agent? One line plugs mendapi into Claude Code as an MCP server (Cursor and every other MCP client work too — details below):

claude mcp add mendapi -- npx mendapi mcp

Requires Node.js 22.13 or newer. Everything runs locally: the scanner, fixer, and review CLIs contain no network code at all.

Security model (read this first)

This tool is designed for teams that cannot let source code leave their machines. The security model is the product, not a FAQ entry:

1. Your code never leaves your machine. The scanner runs locally or in your CI. Nothing is uploaded by default — there is no network code in the scanner, fixer, or review CLIs at all (mechanically enforced by our test suite, which fails the build if any network primitive appears in those files).
2. Metadata-only reporting, opt-in only. If you ever choose to report results to a hosted dashboard, the payload builder (payload.js) is whitelist-constructed: provider names, SDK versions, file basenames, line numbers, and symbol names only. Code snippets are structurally impossible to include — the field does not exist in the payload schema. Reporting requires an explicit --report-to flag; it is never on by default.
3. Secrets are redacted in depth. Fifteen secret patterns (OpenAI, Stripe, AWS, GitHub, Slack, JWT, bearer tokens, generic key assignments, and more) are scrubbed from every field of any outbound payload, and a pre-transmission assertion throws if a forbidden key or unredacted secret survives.
4. Auditable by design. The CLI is open source so your security team can verify, line by line, exactly what is read and what (if anything) is sent.
5. Minimal GitHub permissions. Fix PRs use a GitHub App scoped to contents:read + pull_requests:write on repos you choose. Never admin.
6. Self-hosting available. Enterprise plans run the entire stack — change feed included — inside your firewall.

What it does

Three components form a closed loop:

Shortened. The full README is on GitHub.