Skip to main content
Glama

mcpify

Turn any REST API into an MCP server in one command. Point mcpify at an OpenAPI spec and every endpoint becomes a tool your AI agent (Claude, Cursor, Windsurf, …) can call — no glue code, no per-endpoint wrappers.

mcpify https://api.example.com/openapi.json

That's it. Every operation in the spec is now a live MCP tool.


Why

MCP is how AI agents call real tools. But wiring an existing API into MCP means hand-writing a tool wrapper for every endpoint — tedious and stale the moment the API changes. Almost every API already publishes an OpenAPI spec. mcpify reads that spec and generates the whole MCP server at runtime, so:

  • Zero per-endpoint code — N endpoints → N tools, automatically.

  • Always in sync — regenerate from the spec; no wrappers to maintain.

  • Auth-aware — pass an API key / bearer token once, applied to every call.

Related MCP server: APIFold

Install

pipx install mcpify-cli      # or: uvx mcpify-cli ...

Use

Preview the tools a spec produces (no server):

mcpify --list examples/petstore-mini.yaml

Run it as an MCP server (stdio):

mcpify https://petstore3.swagger.io/api/v3/openapi.json
mcpify ./openapi.yaml --base-url https://staging.internal.api
mcpify ./openapi.yaml --auth "Authorization: Bearer $TOKEN"   # or set MCPIFY_AUTH

Plug it into Claude

Add to your MCP client config (Claude Desktop / Claude Code mcp.json):

{
  "mcpServers": {
    "petstore": {
      "command": "mcpify",
      "args": ["https://petstore3.swagger.io/api/v3/openapi.json"]
    }
  }
}

Restart the client and ask: "list the available pets" — Claude calls the API directly.

How it works

  1. Load the OpenAPI 3.x document (URL or file, JSON or YAML).

  2. Walk every path/method into an Operation with a generated JSON input schema.

  3. Serve them over MCP; each tool call is mapped to a live HTTP request (path, query, header params and JSON bodies all handled) and the response is returned to the agent.

Supported

  • OpenAPI 3.x, JSON or YAML, from a URL or local file

  • GET / POST / PUT / PATCH / DELETE

  • Path, query, and header parameters; JSON request bodies

  • A single global auth header (API key or bearer token)

Roadmap

  • Per-operation filtering (--only, --tag) to expose a subset of a large API

  • $ref resolution for fully-expanded body schemas

  • Swagger 2.0 specs

  • SSE / HTTP transport in addition to stdio

PRs welcome.

License

MIT

Available Tools

3 tools
createPetD

Create a pet

Inputs: body (required).

getPetB

Get a pet by ID

Inputs: petId (required).

listPetsC

List all pets

Inputs: limit.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    C2.8/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a distinct purpose: create, get by ID, and list all pets. No ambiguity or overlap.

    Naming Consistency5/5

    All tools follow a consistent camelCase verb_noun pattern: createPet, getPet, listPets.

    Tool Count4/5

    Three tools is appropriate for a basic pet management scope, though slightly minimal.

    Completeness3/5

    Domain is pet management; missing update and delete operations are notable gaps for full lifecycle.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Automatically converts Swagger/OpenAPI specifications into MCP servers, enabling AI agents to interact with any REST API through natural language by exposing endpoints as AI-friendly tools.
      3
      -
    • A
      license
      A
      quality
      D
      maintenance
      Turn any REST API into a hosted MCP server. 18 free public servers (GitHub, Stripe, Slack, OpenAI, Notion, and more) — no setup required, bring your own API key.
      2
      13
      AGPL 3.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      Turns any OpenAPI specification into a fully working MCP server with a single command, enabling AI agents to call APIs without writing any glue code.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Turns any OpenAPI REST or GraphQL API into an MCP server, allowing AI assistants like Claude to interact with APIs without writing code.
      16 npm
      MIT