MCP Link - Convert Any OpenAPI V3 API to MCP Server

1# MCP Link - Convert Any OpenAPI V3 API to MCP Server
2 
3[![Join our Discord](https://img.shields.io/discord/1234567890?color=7289da&label=Discord&logo=discord&logoColor=white)](https://discord.gg/qkzfbqdSa9)
4 
5## 🧩 Architecture
6 
7![MCP Link](assets/diagrams.png)
8 
9## 🤔 Why MCP Link?
10 
11There is a notable gap in the current AI Agent ecosystem:
12 
13- Most MCP Servers are simple wrappers around Web APIs
14- Functionality interfaces may not be complete, depending on developer implementation
15- Manual creation of MCP interfaces is time-consuming and error-prone
16- Lack of standardized conversion processes
17 
18MCP Link solves these issues through automation and standardization, allowing any API to easily join the AI-driven application ecosystem.
19 
20 
21## 🌟 Key Features
22 
23- **Automatic Conversion**: Generate complete MCP Servers based on OpenAPI Schema
24- **Seamless Integration**: Make existing RESTful APIs immediately compatible with AI Agent calling standards
25- **Complete Functionality**: Ensure all API endpoints and features are correctly mapped
26- **Zero Code Modification**: Obtain MCP compatibility without modifying the original API implementation
27- **Open Standard**: Follow the MCP specification to ensure compatibility with various AI Agent frameworks
28 
29 
30## 🌐 Online Version
31 
32Try our hosted version at [mcp-link.vercel.app](https://mcp-link.vercel.app) to quickly convert and test your APIs without installation.
33 
34 
35## 🚀 Quick Start
36 
37### Installation
38 
39```bash
40# Clone repository
41git clone https://github.com/automation-ai-labs/mcp-link.git
42cd mcp-openapi-to-mcp-adapter
43 
44# Install dependencies
45go mod download
46```
47 
48### Running
49 
50```bash
51# Specify port
52go run main.go serve --port 8080 --host 0.0.0.0
53```
54 
55 
56### Parameter Description
57 
58- `s=` - URL of the OpenAPI specification file
59- `u=` - Base URL of the target API
60- `h=` - Authentication header format, in the format of `header-name:value-prefix`
61- `f=` - Path filter expressions to include or exclude API endpoints. Syntax:
62  - `+/path/**` - Include all endpoints under /path/
63  - `-/path/**` - Exclude all endpoints under /path/
64  - `+/users/*:GET` - Include only GET endpoints for /users/{id}
65  - Multiple filters can be separated by semicolons: `+/**:GET;-/internal/**`
66  - Wildcards: `*` matches any single path segment, `**` matches zero or more segments
67 
68### Examples
69| _ | API | MCP Link URL | Authentication Method |
70|------|-----|-------------|---------|
71| ![Brave](https://img.logo.dev/brave.com) | Brave Search | https://mcp-link.vercel.app/links/brave | API Key |
72| ![DuckDuckGo](https://img.logo.dev/duckduckgo.com) | DuckDuckGo | https://mcp-link.vercel.app/links/duckduckgo | None |
73| ![Figma](https://img.logo.dev/figma.com) | Figma | https://mcp-link.vercel.app/links/figma | API Token |
74| ![GitHub](https://img.logo.dev/github.com) | GitHub | https://mcp-link.vercel.app/links/github | Bearer Token |
75| ![Home Assistant](https://img.logo.dev/home-assistant.io) | Home Assistant | https://mcp-link.vercel.app/links/homeassistant | Bearer Token |
76| ![Notion](https://img.logo.dev/notion.so) | Notion | https://mcp-link.vercel.app/links/notion | Bearer Token |
77| ![Slack](https://img.logo.dev/slack.com) | Slack | https://mcp-link.vercel.app/links/slack | Bearer Token |
78| ![Stripe](https://img.logo.dev/stripe.com) | Stripe | https://mcp-link.vercel.app/links/stripe | Bearer Token |
79| ![TMDB](https://img.logo.dev/themoviedb.org) | TMDB | https://mcp-link.vercel.app/links/tmdb | Bearer Token |
80| ![YouTube](https://img.logo.dev/youtube.com) | YouTube | https://mcp-link.vercel.app/links/youtube | Bearer Token |
81 
82### Usage in AI Agents
83 
84```json
85{
86  "mcpServers": {
87    "@service-name": {
88      "url": "http://localhost:8080/sse?s=[OpenAPI-Spec-URL]&u=[API-Base-URL]&h=[Auth-Header]:[Value-Prefix]"
89    }
90  }
91}
92```
93 
94These URLs allow any API with an OpenAPI specification to be immediately converted into an MCP-compatible interface accessible to AI Agents.
95 
96## 📋 Future Development
97 
98- **MCP Protocol OAuthflow**: Implement OAuth authentication flow support for MCP Protocol
99- **Resources Support**: Add capability to handle resource-based API interactions
100- **MIME Types**: Enhance support for various MIME types in API requests and responses
101