mcpify
About
Turn any OpenAPI 3.x spec into a working MCP server in one command.
Details
- Author
- aloki-alok
- Categories
- Developer Tools
Jump to
Setup
Install mcpify in your MCP client (Claude Desktop, Cursor, Windsurf, and others).
Repository: https://github.com/aloki-alok/mcpify
Follow the installation instructions in the repository README, then restart your MCP client.
Turn any OpenAPI 3.x or Swagger 2.0 spec into a working MCP server in one command.
Point it at a spec (a file or a URL) and every API operation becomes an MCP tool. There is no code to generate and nothing to wire up: mcpify reads the spec, exposes one tool per operation, and proxies each tool call to the real API.
mcpify ls openapi.yaml # preview the tools a spec exposes mcpify openapi.yaml # serve it as an MCP server
curl -fsSL https://raw.githubusercontent.com/aloki-alok/mcpify/main/install.sh | sh
go install github.com/aloki-alok/mcpify@latest
Or grab a prebuilt binary from thereleases page, or build from source:
git clone https://github.com/aloki-alok/mcpify cd mcpify go build -o mcpify .
Preview what a spec turns into, without starting anything:
mcpify ls https://petstore3.swagger.io/api/v3/openapi.json
In a terminal this opens a short menu: run a local server and get a connect URL (the default, just press enter), print a client config to paste, or list the tools. When an MCP client spawns mcpify over a pipe, it serves stdio directly, so the same command works inside a client config. Pass--stdioto force stdio serving in a terminal too.
The MCP endpoint ishttp://localhost:8080/mcp. The root URL serves a short plain-text page describing the server, for anyone who opens it in a browser.
Forward auth and override the upstream base URL:
mcpify --base https://api.example.com -H "Authorization: Bearer $TOKEN" spec.json
With-H, the resolved secret still ends up on the command line, where process listings, shell history, and printed client configs can see it.--header-envkeeps it out of all three: mcpify reads the value from the named environment variable at startup, and configs carry the reference instead of the secret:
export API_TOKEN="Bearer ..." mcpify --header-env "Authorization=API_TOKEN" spec.json
Expose only read operations (GET and HEAD):
Cut down a large spec to the tools you actually want.--includekeeps operations whose tool name, operationId, or path match; without athis is a case insensitive substring check, with one it is apath.Matchglob (whole string, case sensitive,does not cross a/) against each of the three.--tagkeeps operations carrying that OpenAPI tag (case insensitive, exact match). Both are repeatable, and an operation is kept if it matches any--includeor any--tag:
mcpify --tag pet --tag store spec.yaml mcpify --include "Pet" spec.yaml mcpify --include order spec.yaml
Any client that launches a server over stdio works. For example:
{ "mcpServers": { "petstore": { "command": "mcpify", "args": ["--base", "https://api.example.com", "/path/to/openapi.json"] } } }
OpenAPI 3.0 and 3.1, in JSON or YAML. One operation maps to one tool. Request bodies are JSON. Templated server URLs resolve from their variable defaults, or override the base with--base. Auth is pass-through: the headers you supply are forwarded upstream.
Swagger 2.0 specs work too. mcpify converts them to the same tools you would get from a 3.x spec: the server URL comes fromschemes+host+basePath(preferring https), path, query, and header parameters map straight across, a body parameter's schema is flattened the same way, and$refs intodefinitionsare inlined. Operations that takeformData(file uploads and form fields) are skipped with a note, since mcpify only sends JSON bodies; the rest of the spec still serves.
This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.
Create crafted UI components inspired by the best 21st.dev design engineers.
Bring agent evaluations, observability, and synthetic test set generation directly into your IDE for free with Galileo's new MCP server
An MCP server to help AI assistants to answer questions and generate AccelByte Extend SDK code more effectively .
MCP server for AI Diagram Maker — generate beautiful software engineering diagrams directly inside Cursor, Claude Desktop, Claude Code, or any MCP-compatible AI agent
ALAPI MCP Tools,Call hundreds of API interfaces via MCP
AI-powered SVG animation generator that transforms static files into animated SVG components using the Allyson platform
MCP server that gives AI assistants on-demand access to 1,500+ amCharts docs, ~300 code examples, and 1000+ class API references.
APIMatic MCP Server is used to validate OpenAPI specifications using APIMatic. The server processes OpenAPI files and returns validation summaries by leveraging APIMatic’s API.
One shared context layer for AI agents and humans — live API specs, DB schemas, and versioned contracts across repos so every agent and teammate works from the same source of truth.
Build and deploy full-stack Next.js apps with 98 tools for React, AWS, and MongoDB
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
