mcp-link

MCP Link is a converter and adapter that exposes any OpenAPI v3 specification as an MCP-compatible server. It automatically generates an MCP interface for each endpoint defined in your API, so AI agents can discover, authenticate, and call those endpoints using the MCP protocol without modifying your original API implementation. The tool is designed to map OpenAPI paths, methods, and parameters into MCP endpoints, preserving operation semantics and supporting common authentication schemes as described by the OpenAPI spec. You can point MCP Link at any public or private OpenAPI document, and it will emit an MCP-facing interface that AI agents can consume via the generated MCP URL.

To use it, start the MCP Link server and provide the required OpenAPI spec URL and the target API base URL through the provided CLI flags. The server will then expose an MCP-compatible interface that AI agents can access. Check the Quick Start examples in the README for the correct URL shapes and parameter formats. The core idea is that the MCP Link service acts as a bridge: it reads the OpenAPI contract, creates a faithful MCP mapping, and serves that mapping to agents without requiring code changes to either the API or the agent runtime.

Prerequisites:

• Go 1.18+ installed on your system
• Git installed
• Access to the OpenAPI spec you want to convert (local path or URL)

Installation steps:

1. Clone the repository: git clone https://github.com/automation-ai-labs/mcp-link.git cd mcp-link

2. Install dependencies (Go modules will be resolved automatically): go mod download

3. Run the MCP Link server (example): go run main.go serve --port 8080 --host 0.0.0.0

4. Verify the server is running by visiting the configured URL or by checking logs. If you want to build a binary first, you can run: go build -o mcp-link ./... ./mcp-link serve --port 8080 --host 0.0.0.0

Tips and common considerations:

• MCP Link expects a valid OpenAPI v3 document. If your OpenAPI spec uses components security schemes, ensure the server supports the corresponding authentication headers described in the spec (the MCP mapping will reflect these where possible).
• The Quick Start includes a sample usage snippet showing how agents can reference the MCP endpoint via an sse-based URL pattern. You can adapt the host/port as needed for deployment environments (e.g., behind a reverse proxy or in a container).
• If you modify the OpenAPI spec, restart the MCP Link server to refresh the MCP mapping so agents see updated endpoints and parameters.
• When using with private APIs, ensure network access and credentials are supplied in the appropriate OpenAPI security definitions and/or host headers as part of the mapping.