OpenAPI Link

by automation-ai-labs

255 stars
833 downloads
Not rated
GitHub Website

About

Transforms OpenAPI specifications into tool endpoints, enabling seamless interaction with any API described in OpenAPI format without custom adapter development.

Details

Author
automation-ai-labs
Repository
automation-ai-labs/mcp-link
GitHub stars
255
Downloads
833
License
MIT License
Categories
AI, Design, Developer Tools, File Management, Frontend, Security, Infrastructure, Finance

- Automatic Conversion: Generate complete MCP Servers based on OpenAPI Schema
- Seamless Integration: Make existing RESTful APIs immediately compatible with AI Agent calling standards
- Complete Functionality: Ensure all API endpoints and features are correctly mapped
- Zero Code Modification: Obtain MCP compatibility without modifying the original API implementation
- Open Standard: Follow the MCP specification to ensure compatibility with various AI Agent frameworks

Setting up with Highlight

This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:

  1. Download and install Highlight from highlightai.com/download
  2. Navigate to the plugins tab and select "Add Custom Plugin"
  3. Configure the plugin with the settings below
    Plugin Name OpenAPI Link
    Command (node, npx, python, etc.) node
    Arguments
    • Argument 1 main.js
    • Argument 2 serve
    • Argument 3 --port
    • Argument 4 8080
    • Argument 5 --host
    • Argument 6 0.0.0.0

    Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.

  4. Enable "Start Automatically" if you want the plugin to start when Highlight launches

From the repository


go mod download

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

These URLs allow any API with an OpenAPI specification to be immediately converted into an MCP-compatible interface accessible to AI Agents.

Claude Desktop / Cursor

Paste into your MCP client config file to install this server.

{
    "mcpServers": {
        "openapi link": {
            "command": "node",
            "args": [
                "main.js",
                "serve",
                "--port",
                "8080",
                "--host",
                "0.0.0.0"
            ],
            "env": {},
            "cwd": "mcp-openapi-to-mcp-adapter"
        }
    }
}

Macos

{
    "command": "node",
    "args": [
        "main.js",
        "serve",
        "--port",
        "8080",
        "--host",
        "0.0.0.0"
    ],
    "env": [],
    "cwd": "mcp-openapi-to-mcp-adapter"
}

Windows

{
    "command": "cmd",
    "args": [
        "/c",
        "node",
        "main.js",
        "serve",
        "--port",
        "8080",
        "--host",
        "0.0.0.0"
    ],
    "env": [],
    "cwd": "mcp-openapi-to-mcp-adapter"
}

Linux

{
    "command": "node",
    "args": [
        "main.js",
        "serve",
        "--port",
        "8080",
        "--host",
        "0.0.0.0"
    ],
    "env": [],
    "cwd": "mcp-openapi-to-mcp-adapter"
}
# MCP Link - Convert Any OpenAPI V3 API to MCP Server [![Join our Discord](https://img.shields.io/discord/1234567890?color=7289da&label=Discord&logo=discord&logoColor=white)](https://discord.gg/qkzfbqdSa9) ## 🧩 Architecture ![MCP Link](assets/diagrams.png) ## 🤔 Why MCP Link? There is a notable gap in the current AI Agent ecosystem: - Most MCP Servers are simple wrappers around Web APIs - Functionality interfaces may not be complete, depending on developer implementation - Manual creation of MCP interfaces is time-consuming and error-prone - Lack of standardized conversion processes MCP Link solves these issues through automation and standardization, allowing any API to easily join the AI-driven application ecosystem. ## 🌟 Key Features - **Automatic Conversion**: Generate complete MCP Servers based on OpenAPI Schema - **Seamless Integration**: Make existing RESTful APIs immediately compatible with AI Agent calling standards - **Complete Functionality**: Ensure all API endpoints and features are correctly mapped - **Zero Code Modification**: Obtain MCP compatibility without modifying the original API implementation - **Open Standard**: Follow the MCP specification to ensure compatibility with various AI Agent frameworks ## 🌐 Online Version Try our hosted version at [mcp-link.vercel.app](https://mcp-link.vercel.app) to quickly convert and test your APIs without installation. ## 🚀 Quick Start ### Installation ```bash # Clone repository git clone https://github.com/automation-ai-labs/mcp-link.git cd mcp-openapi-to-mcp-adapter # Install dependencies go mod download ``` ### Running ```bash # Specify port go run main.go serve --port 8080 --host 0.0.0.0 ``` ### Parameter Description - `s=` - URL of the OpenAPI specification file - `u=` - Base URL of the target API - `h=` - Authentication header format, in the format of `header-name:value-prefix` - `f=` - Path filter expressions to include or exclude API endpoints. Syntax: - `+/path/**` - Include all endpoints under /path/ - `-/path/**` - Exclude all endpoints under /path/ - `+/users/*:GET` - Include only GET endpoints for /users/{id} - Multiple filters can be separated by semicolons: `+/**:GET;-/internal/**` - Wildcards: `*` matches any single path segment, `**` matches zero or more segments ### Examples | _ | API | MCP Link URL | Authentication Method | |------|-----|-------------|---------| | ![Brave](https://img.logo.dev/brave.com) | Brave Search | https://mcp-link.vercel.app/links/brave | API Key | | ![DuckDuckGo](https://img.logo.dev/duckduckgo.com) | DuckDuckGo | https://mcp-link.vercel.app/links/duckduckgo | None | | ![Figma](https://img.logo.dev/figma.com) | Figma | https://mcp-link.vercel.app/links/figma | API Token | | ![GitHub](https://img.logo.dev/github.com) | GitHub | https://mcp-link.vercel.app/links/github | Bearer Token | | ![Home Assistant](https://img.logo.dev/home-assistant.io) | Home Assistant | https://mcp-link.vercel.app/links/homeassistant | Bearer Token | | ![Notion](https://img.logo.dev/notion.so) | Notion | https://mcp-link.vercel.app/links/notion | Bearer Token | | ![Slack](https://img.logo.dev/slack.com) | Slack | https://mcp-link.vercel.app/links/slack | Bearer Token | | ![Stripe](https://img.logo.dev/stripe.com) | Stripe | https://mcp-link.vercel.app/links/stripe | Bearer Token | | ![TMDB](https://img.logo.dev/themoviedb.org) | TMDB | https://mcp-link.vercel.app/links/tmdb | Bearer Token | | ![YouTube](https://img.logo.dev/youtube.com) | YouTube | https://mcp-link.vercel.app/links/youtube | Bearer Token | ### Usage in AI Agents ```json { "mcpServers": { "@service-name": { "url": "http://localhost:8080/sse?s=[OpenAPI-Spec-URL]&u=[API-Base-URL]&h=[Auth-Header]:[Value-Prefix]" } } } ``` These URLs allow any API with an OpenAPI specification to be immediately converted into an MCP-compatible interface accessible to AI Agents. ## 📋 Future Development - **MCP Protocol OAuthflow**: Implement OAuth authentication flow support for MCP Protocol - **Resources Support**: Add capability to handle resource-based API interactions - **MIME Types**: Enhance support for various MIME types in API requests and responses
No reviews yet — be the first

Sign in to leave a review

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.