MCPify CLI
A CLI compiler that reads app code, API specs and database schemas and generates a ready MCP server with tool permission checks.
- 107 ★ on the repository
- Last commit
Extended access
Why this level
- By default the generator registers the server into agent clients on its own, and the created tools act with your app rights.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/mcpifyDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- By default the generator registers the server into agent clients on its own, and the created tools act with your app rights.
This is third-party code. Review the repository files before installing.
What it does
MCPify turns an existing app into a tool set for an agent. The `npx mcpify-cli analyze ./my-app` command runs a pipeline: backend analysis, optional OpenAPI, Prisma, Drizzle and Mongoose parsing, event and webhook discovery, UI action extraction, workflow detection, permission classification and MCP server generation into a `.mcpify` folder. Other commands: `swagger <file>` turns an OpenAPI spec into tools, `frontend` extracts UI actions, `audit` runs a static safety check of discovered tools with no files written, `simulate` runs an AI check when `ANTHROPIC_API_KEY` is set, `interactive` asks about analyzers. The `--clients` flag picks registration into `codex`, `claude-code`, `claude-desktop` or `vscode`.
Who it is for. Developers who want to give an agent access to their own app without hand-writing MCP boilerplate.
Good fit when
- The app has an OpenAPI spec and ready MCP tools are wanted from it.
- Prisma schemas sit nearby and data actions should be exposed to an agent.
- Before handing tools to an agent a static permission audit is run.
- Hand-maintained tool descriptions that drift from the API are a nuisance.
Not a fit when
- The app belongs to someone else without the owner permission: the tool generates actions over its interface.
- A vetted ready integration with a known service is needed rather than generation.
- The environment does not allow automatic writes to client configs.
Example request
Analyze this project, generate an MCP server from OpenAPI and Prisma, but do not register it in clients before I read the audit.Limitations
By default `--clients` is `all`, so after generation MCPify registers the server into Codex, Claude Code, Claude Desktop and VS Code on its own. Turn that off with `--no-install`. The generated server acts with the rights of your app, so run `audit` and read the permission classification before connecting. Improving descriptions through `--ai-enhance` and `simulate` need `ANTHROPIC_API_KEY` and send tool descriptions to Anthropic. Generation quality depends on code structure, and the author presents the project as early.
How to disable. Remove the server entry from each client config and the `.mcpify` folder from the project. Unset `ANTHROPIC_API_KEY` from the environment.
FAQ
How do I run it without installing?
With `npx mcpify-cli analyze ./my-app`. No package install is needed.
Where does the output go?
Into a `.mcpify` folder next to the project; `--output` changes it. The generated `AGENTS.md` explains connecting a client.
What does `audit` do?
It statically checks discovered tools and workflows and writes nothing to disk.
Is an Anthropic key needed?
Only for `--ai-enhance` and `simulate`. Other steps work without a key.
How do I build from source?
Clone the repository, run `npm install` and `npm run build`, then `npm run mcpify -- analyze <path>`.
Discussion
No questions or reviews yet.
Related
CLI toolsA plugin with skills for building TypeScript MCP servers and MCP apps: the agent scaffolds, edits, debugs and verifies them
A CLI that builds a ready-made TypeScript MCP server from an OpenAPI 3 spec, with tools, validation and auth generated for you
An MCP server that lets an agent read files, search code and run commands in a workspace
OpenMCP turns any OpenAPI specification into an MCP server and lets you choose which tools the agent sees
A transparent proxy between an AI client and an MCP server: shows every JSON-RPC frame in the terminal, checks a capture in CI and exports spans
A CLI creates a TypeScript MCP server scaffold, adds components and checks schema descriptions before client connection
README in short
The README sets the task of an app compiler and covers an overview, features, running via `npx`, each CLI command and the architecture.