Turn any REST API into an MCP server in one command

@Amanbig

Basic information

About Turn any REST API into an MCP server in one command

Point mcpify at any OpenAPI spec and every endpoint becomes a tool your AI agent (Claude, Cursor, Windsurf) can call — zero glue code, zero per-endpoint wrappers, always in sync with the spec. Supports GET/POST/PUT/PATCH/DELETE, auth headers, and both URL and local file specs.

#openapi #rest-api #claude #cursor #python #developer-tools

Turn any REST API into an MCP server in one command config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "mcpify": {
      "command": "mcpify",
      "args": [
        "https://your-api.com/openapi.json"
      ]
    }
  }
}

Turn any REST API into an MCP server in one command tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Turn any REST API into an MCP server in one command?

It transforms any REST API that has an OpenAPI specification into a Model Context Protocol (MCP) server. Every endpoint becomes a tool that AI agents like Claude, Cursor, and Windsurf can call directly — no glue code or per-endpoint wrappers needed, and it stays in sync with the specification.

How to use Turn any REST API into an MCP server in one command?

Point mcpify at any OpenAPI specification (via URL or local file) and run a single command. The generated MCP server exposes all endpoints as tools, supporting GET, POST, PUT, PATCH, DELETE, and authentication headers.

Key features of Turn any REST API into an MCP server in one command

Zero glue code or per‑endpoint wrappers
Automatically stays in sync with the spec
Supports all HTTP methods (GET, POST, PUT, PATCH, DELETE)
Handles authentication headers
Loads specs from URLs or local files

Use cases of Turn any REST API into an MCP server in one command

Integrate a legacy REST API into an AI agent without writing any code
Let Claude or Cursor call any API endpoint as a tool
Keep AI tools automatically up‑to‑date with a changing API specification
Quickly wrap internal or third‑party REST APIs for MCP‑compatible agents

Frequently asked questions

What HTTP methods does MCPify support?

It supports GET, POST, PUT, PATCH, and DELETE.

Can I use authentication headers?

Yes, it supports authentication headers as defined in the OpenAPI spec.

How does it stay in sync with the API?

It reads the OpenAPI specification directly, so any changes to the spec are automatically reflected without manual updates.

Which AI agents can use the resulting MCP server?

It is designed for agents that support the Model Context Protocol, including Claude, Cursor, and Windsurf.

What formats can the OpenAPI spec be in?

It can load the specification from a URL or a local file.

Comments

More Developer Tools MCP servers

Eddyter AI Rich Text Editor MCP

EddyterAI

Set up and manage the Eddyter AI rich text editor by talking to your AI agent — for Claude, Cursor, Codex and other MCP tools. A Model Context Protocol server that lets AI tools add Eddyter to a React, Next.js, Vite or R

Casefile

azimov777

One case file per task — shared by every session, agent and person that touches it. Self-hosted MCP server and live board. MIT.

Perfex CRM

themesic

Turn Perfex CRM into an AI-ready workspace. This MCP server exposes your full REST API to Claude, ChatGPT and any AI agent, so leads, invoices and tasks are one prompt away.

CircleCI MCP Server

CircleCI

Manage CI/CD pipelines, debug failed builds, and optimize test suites directly from your AI agents - no terminal required. The CircleCI MCP Server is a remote server hosted by CircleCI that connects AI tools and agents

SSH MCP Server

hypnosis

SSH MCP server for AI agents: remote commands, file transfer, log search and server audits through OpenSSH.