Server profile

MCP Link

MCP Link converts OpenAPI V3 descriptions into MCP interfaces for existing REST APIs. Developers can expose API operations to agents without changing the original implementation and filter which routes are included.

Server facts

MCP Link

Tech

Runtime / language
goGo
Transports
stdio
Remote available
No
Authentication
Not specified

Activity

GitHub stars
625
Last commit
Data as of

Tags

  • Api Conversion
  • Endpoint Filters
  • Openapi
  • Rest Api

Overview

MCP Link turns an OpenAPI V3 description into an MCP interface for an existing API. Its purpose is to reduce the manual wrapper work normally required to expose web services to AI agents. Rather than implementing a separate integration around selected endpoints, users provide the specification location and the target service base URL. The project describes automatic mapping of API functionality while leaving the original API implementation unchanged. A hosted version is linked for trying conversions without a local installation, and the README includes examples for services such as GitHub, Notion, Slack, Figma, and Stripe. The actual exposed operations depend on the supplied API description.

For local use, the README shows downloading Go dependencies and starting the server with a chosen host and port. Clients connect to an SSE URL whose query parameters identify the specification, base URL, and authentication header format. A filter parameter controls endpoint inclusion and exclusion using path patterns and optional HTTP methods. Single and recursive wildcards support different path depths, and semicolons combine several filters. These controls are useful when an agent should see only part of an API rather than every documented route. OAuth flow support, resource interactions, and broader MIME handling appear under future development, not as established capabilities. No fixed MCP tool names are provided in the input.

Install & configure

Requirements

  • Go
  • A local repository checkout with dependencies downloaded
  • An OpenAPI V3 specification URL
  • The target API base URL
Documented launch / install command
go run main.go serve --port 8080 --host 0.0.0.0

Run go mod download in the checkout first. Configure the SSE URL with s for the specification, u for the API base URL, and h for authentication header formatting; f optionally filters routes. The README checkout directory example differs from the repository name.

Config file · macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

Windows: %APPDATA%\Claude\claude_desktop_config.json

Use Settings → Developer → Edit Config when available. Do not assume a Linux configuration path; check the client documentation for your platform. Remote servers use the app’s connector flow when supported, not the local stdio file shown here. Merge this example with existing settings; do not overwrite unrelated servers.

A supported configuration example is not available for this client and transport. Check the client documentation for its connection flow; do not substitute an undocumented JSON format.

Read the Claude Desktop setup guide

Config file · Project: .cursor/mcp.json

User: ~/.cursor/mcp.json

The project path is relative to the workspace root. The tilde denotes your user home directory. Use Cursor’s MCP settings to confirm which configuration and scope your installed version is reading. Merge this example with existing settings; do not overwrite unrelated servers.

Cursor configuration
{
  "mcpServers": {
    "mcp-link": {
      "url": "http://localhost:8080/sse?s=[OpenAPI-Spec-URL]&u=[API-Base-URL]&h=[Auth-Header]:[Value-Prefix]"
    }
  }
}

Read the Cursor setup guide

Config file · Workspace: .vscode/mcp.json

For user scope, use the “MCP: Open User Configuration” command if available. Do not guess a user configuration path across operating systems, profiles, containers, or remote workspaces; check the client documentation. Merge this example with existing settings; do not overwrite unrelated servers.

A supported configuration example is not available for this client and transport. Check the client documentation for its connection flow; do not substitute an undocumented JSON format.

Read the VS Code setup guide

Config file · macOS/Linux: ~/.codeium/windsurf/mcp_config.json

Windows: %USERPROFILE%\.codeium\windsurf\mcp_config.json

Open the MCP configuration through Windsurf’s settings when possible to confirm the active file. Paths can differ in managed or future releases; check the client documentation if this location is not present. Merge this example with existing settings; do not overwrite unrelated servers.

Windsurf configuration
{
  "mcpServers": {
    "mcp-link": {
      "serverUrl": "http://localhost:8080/sse?s=[OpenAPI-Spec-URL]&u=[API-Base-URL]&h=[Auth-Header]:[Value-Prefix]"
    }
  }
}

Read the Windsurf setup guide

Config file · Project scope: .mcp.json at the repository root

The project file uses mcpServers. For user scope, use claude mcp add --scope user rather than assuming .mcp.json in your home directory is the user configuration. Check the client documentation for managed settings and storage details. Merge this example with existing settings; do not overwrite unrelated servers.

Claude Code configuration
{
  "mcpServers": {
    "mcp-link": {
      "type": "sse",
      "url": "http://localhost:8080/sse?s=[OpenAPI-Spec-URL]&u=[API-Base-URL]&h=[Auth-Header]:[Value-Prefix]"
    }
  }
}

Read the Claude Code setup guide

Examples are translated from the published configuration. Supply your own credentials and verify requirements in the upstream README. Remote connectors are shown only where a supported configuration format is known.

Tools

No individual tool names were confirmed in the source material. Check the repository for its current tool list.

Names, permissions, and defaults can change. Check the current upstream documentation before granting access.

Use cases

  • Expose an existing REST API to an MCP-compatible agent
  • Prototype an integration from an OpenAPI V3 specification
  • Restrict exposed API routes by path and HTTP method
  • Test API conversion with the linked hosted interface

Strengths

  • Uses existing API descriptions instead of hand-written wrappers
  • Does not require changes to the source API implementation
  • Supports include and exclude filters for endpoints

Limitations

  • Requires an OpenAPI specification and API base URL
  • OAuth flow and resource support are listed as future work

Frequently asked questions

No. The README describes conversion without modifying the API implementation.

They are generated from the supplied OpenAPI schema; the README does not enumerate fixed tool names.

Yes. Filters support HTTP-method constraints as well as path patterns.

It is listed in the future-development section rather than the current feature list.

Independent listing, not an affiliation or security review. Grant the least access needed and verify the upstream instructions before running code.

Related MCP servers

Supergateway

MCP Gateways & Proxies

Supergateway bridges MCP transports so stdio servers can reach network clients and remote services can appear locally over stdio. It supports SSE, WebSockets, and Streamable HTTP modes through command-line configuration.

Unla MCP Gateway

MCP Gateways & Proxies

Unla is a Go gateway that exposes existing APIs and MCP servers through MCP endpoints using configuration. It includes a management interface, recoverable sessions, multi-tenant support, and deployment options for containers or Kubernetes.

mcp-proxy

MCP Gateways & Proxies

mcp-proxy bridges MCP transport mismatches between clients and servers. It can connect a stdio client to a remote SSE or Streamable HTTP server, or expose local stdio servers through network endpoints.

mcpo

MCP Gateways & Proxies

mcpo makes MCP tools available through an OpenAPI-compatible HTTP server. It is for agents and applications that consume OpenAPI endpoints rather than communicating with MCP servers directly.

MCPHub

MCP Gateways & Proxies

Organize multiple MCP servers behind shared HTTP or SSE endpoints. MCPHub adds a management dashboard, group-level visibility controls, semantic routing, authentication, and a terminal interface.

ContextForge

MCP Gateways & Proxies

ContextForge registers and proxies tools, agents, and APIs behind a unified gateway. It targets teams that need discovery, authentication, observability, and policy controls across MCP, A2A, REST, and gRPC services.

MCP Proxy Server

MCP Gateways & Proxies

MCP Proxy Server combines multiple MCP backends behind one HTTP entrypoint. It aggregates tools, prompts, and resources while connecting to stdio, SSE, or streamable HTTP servers.

MCP Hub

MCP Gateways & Proxies

MCP Hub coordinates multiple MCP servers behind one client endpoint. It provides a REST management API and web UI, with server lifecycle controls, authentication handling, and live capability updates.