MCP Link - Convert Any OpenAPI V3 API to MCP Server

@automation-ai-labs

Repository Homepage

Basic information

About MCP Link - Convert Any OpenAPI V3 API to MCP Server

Convert Any OpenAPI V3 API to MCP Server

#mcp #agents #mcp-server

MCP Link - Convert Any OpenAPI V3 API to MCP Server config

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

{
  "mcpServers": {
    "@service-name": {
      "type": "http",
      "url": "http://localhost:8080/sse?s=[OpenAPI-Spec-URL]&u=[API-Base-URL]&h=[Auth-Header]:[Value-Prefix]"
    }
  }
}

MCP Link - Convert Any OpenAPI V3 API to MCP Server 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.

Fetch the live tool list directly from this server's endpoint using the button above.

Overview

What is MCP Link?

MCP Link automatically converts any OpenAPI V3 API into an MCP (Model Context Protocol) server. It is designed for developers who want to make existing RESTful APIs immediately compatible with AI Agent calling standards without modifying the original API.

How to use MCP Link?

Clone the repository, install Go dependencies with go mod download, and run the server via go run main.go serve --port 8080 --host 0.0.0.0. Use query parameters to configure conversion: s= for the OpenAPI spec URL, u= for the API base URL, h= for authentication header format, and f= for path filter expressions. A hosted version is available at mcp-link.vercel.app for quick testing.

Key features of MCP Link

Automatic MCP server generation from OpenAPI Schema
Seamless integration with existing AI Agent ecosystems
Complete and correct mapping of all API endpoints
Zero code modification required for the original API
Follows the open MCP specification for broad compatibility

Use cases of MCP Link

Convert a third‑party REST API (e.g., GitHub, Stripe) into an MCP server for AI assistants
Rapidly prototype AI‑Agent integrations for internal APIs without manual wrapper code
Migrate multiple legacy OpenAPI services to standard MCP interfaces in a single command

Frequently asked questions

How does MCP Link differ from manually creating MCP interfaces?

MCP Link automates the conversion process from OpenAPI schemas, ensuring full functionality mapping without time‑consuming and error‑prone manual implementation.

What runtime dependencies are required?

The server requires Go and its dependencies (downloaded via `go mod download`). No changes to the original API are needed.

Where does the MCP server run?

You can run it locally on the specified port and host, or use the hosted version at mcp-link.vercel.app without any installation.

What transport protocol does MCP Link use?

The server uses SSE (Server‑Sent Events); MCP client configuration points to an `sse` endpoint.

How is authentication handled?

Authentication is configured via the `h=` parameter in the format `header-name:value-prefix`. Examples include API keys, Bearer tokens, and custom headers.

Comments

More Developer Tools MCP servers

Routebase

Routebase keeps your API's design, docs, contract tests, mocks and monitoring in one living OpenAPI spec so they can't drift apart. Agents work on that same source of truth, under your team's permissions.

Kaiva Bridge

Kaiva Bridge turns your API, database or documents into a managed MCP server for Claude, ChatGPT, Cursor and VS Code. Point it at an OpenAPI or Swagger spec, an API docs link, a cURL command, a Postman collection, a Grap

Moxie Docs

Jackalope-Dev

Automated codebase documentation for GitHub: searchable docs, MCP context for AI agents, doc drift detection, and Friday Cleanup PRs.

Yocoolab

MCP server for AI Agents — exposes Yocoolab feedback threads and design selections as tools

Modelglass

Modelglass turns "which model should I use?" into a lookup instead of a guess. Seven tools give your agent live pricing across image, language, video, and audio models. Sourced and versioned, not scraped once and forgott