home / mcp / mcp link mcp server

MCP Link MCP Server

Converts OpenAPI v3 APIs into MCP-compatible endpoints for AI Agents with optional hosted or local deployment

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "automation-ai-labs-mcp-link": {
      "url": "https://mcp-link.vercel.app"
    }
  }
}

You can convert any OpenAPI v3 API into a MCP Server instance that AI Agents can call, either by running a local server or using the hosted version. This enables seamless integration of RESTful APIs into the MCP ecosystem without modifying the original API implementation.

How to use

Choose between the hosted version and a local deployment. The hosted version lets you quickly create an MCP-compatible interface for your API, while a local server gives you full control and runs on your own infrastructure.

If you want to connect via a client to a hosted MCP, use the hosted URL as the MCP endpoint in your client configuration. You can also run a local MCP server and point your client at your own instance. A typical client configuration references an MCP URL and submits requests that the MCP Server translates into calls to your OpenAPI-defined API.

How to install

Prerequisites: ensure you have Go installed on your system and Git for cloning repositories.

1) Clone the project repository.

# Clone repository
git clone https://github.com/automation-ai-labs/mcp-link.git
cd mcp-openapi-to-mcp-adapter

# Install dependencies
go mod download

2) Run the MCP Server locally on your machine. You can choose a port and host for the server.

# Specify port
go run main.go serve --port 8080 --host 0.0.0.0

Configuration and usage notes

Parameter meanings you will use when configuring the MCP interface for your client:

s = URL of your OpenAPI specification file
u = Base URL of the target API
h = Authentication header format in the form header-name:value-prefix
f = Path filter expressions to include or exclude API endpoints

Examples and quick reference

If you want to connect to a local MCP server from a client, you can point the client to the local endpoint you started in the previous step.

If you want to use the hosted version, you can reference its URL as the MCP endpoint to enable quick testing and conversion of your API.

Troubleshooting and tips

Ensure the OpenAPI specification is reachable at the provided s URL and that the API base URL (u) is correct. If authentication is required, verify that the h header format matches what your API expects. If you modify endpoint visibility with f filters, confirm that the syntax includes include (+) and exclude (-) patterns as described.

Notes and known considerations

You can take advantage of the hosted version for rapid testing or run a local MCP server for production deployments. No changes to the original API implementation are required to achieve MCP compatibility.