MCPForge

One CLI, five stages

Point MCPForge at any OpenAPI/Swagger spec and it runs the whole lifecycle: inspect the tools, scan for security, test every tool against the live API, add usage metering, generate a deployable server, and serve it locally.

It works with any API in any language and emits a standard MCP server any agent can use — no lock-in, you own the output.

Low-noise & honest

The security scan is deliberately quiet — it flags only genuinely actionable findings, not the wall of false positives other scanners produce.

The test stage calls every tool with sample inputs synthesized from its schema, then reports honestly what works: pass, needs-auth, expected-4xx, or a real failure.

Own the output

The generate and monetize stages write files you own — a self-contained MCP server plus a drop-in usage meter you can deploy and bill anywhere.

Every stage operates on one normalized model of the API, which keeps each stage simple and the input universal.

Built on a clean core

Any OpenAPI 2 or 3 spec — JSON or YAML, file or URL — compiles down to one clean tool model. New stages plug into the same model, so the tool grows without growing messy.

Written in TypeScript as an ESM CLI, MCPForge ships as a tiny dependency-light package on npm and runs with a single npx command.

Live on npm

MCPForge is published as @muhammad-adil-code/mcp-forge — installable globally or runnable with npx, verified working end-to-end against a live API.

The whole lifecycle

From spec to a tested, secure, monetizable, deployable MCP server — inspect, scan, test, monetize, generate, and serve, all in one CLI you own.