MCP Link

Converts any OpenAPI V3 REST API specification into a working MCP server automatically, enabling AI agents to call any REST API through MCP without writing custom integration code.

Evaluated Mar 06, 2026 (0d ago) vlatest

Homepage ↗ Repo ↗ Developer Tools openapi rest-api api-bridge go automation github slack stripe notion

⚙ Agent Friendliness

/ 100

Can an agent use this?

🔒 Security

/ 100

Is it safe for agents?

⚡ Reliability

/ 100

Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality

Documentation

Error Messages

Auth Simplicity

Rate Limits

🔒 Security

TLS Enforcement

Auth Strength

Scope Granularity

Dep. Hygiene

Secret Handling

MCP server linking/chaining tool. Connects MCP servers together. Security depends on linked servers. Prevent circular chains. Validate tool outputs before passing to next server.

⚡ Reliability

Uptime/SLA

Version Stability

Breaking Changes

Error Recovery

Best When

You have a REST API with an OpenAPI V3 spec and want to give an AI agent access to it immediately without building a custom MCP server. Especially powerful for well-documented public APIs.

Avoid When

Your API uses OAuth 2.0 authorization code flow, requires interactive auth, or relies on resource-based interactions not expressible in OpenAPI. Also avoid for APIs without a spec.

Use Cases

• Instantly make any OpenAPI V3 API (GitHub, Slack, Stripe, Notion, Figma, YouTube) accessible to Claude without custom code
• Build AI agent workflows that call multiple REST APIs through a unified MCP interface
• Selectively expose a subset of API endpoints to an agent using path filtering expressions
• Rapidly prototype AI integrations against internal APIs that have OpenAPI specs
• Replace manual curl/fetch calls in agent workflows with structured MCP tool calls

Not For

• APIs without an OpenAPI V3 specification (OpenAPI V2/Swagger requires conversion first)
• APIs requiring OAuth interactive flows (not currently supported)
• APIs with complex MIME types or multipart file uploads (limited MIME support noted)

Interface

REST API

GraphQL

gRPC

MCP Server

Yes ↗

SDK

Webhooks

Authentication

Methods: api_key bearer_token custom_headers

OAuth: No Scopes: No

Auth configured via the 'h=' header parameter at server startup. Supports API keys, bearer tokens, and arbitrary header-based auth. OAuth interactive flows explicitly listed as a current limitation.

Pricing

Model: open_source

Free tier: Yes

Requires CC: No

Open source (Go). Costs depend on the upstream APIs being proxied.

Agent Metadata

Pagination

cursor

Idempotent

Partial

Retry Guidance

Not documented

Known Gotchas

⚠ OAuth interactive flows not supported — APIs requiring browser-based auth cannot be used
⚠ No resource-based interaction handling (a noted current limitation)
⚠ Limited MIME type support may break file upload or binary response endpoints
⚠ Path filtering uses wildcard expressions — misconfiguration could expose unintended endpoints to the agent
⚠ Requires Go build environment to install (no pre-built binaries mentioned)

Alternatives

mcp-graphql custom-mcp-server langchain-api-tools

Full Evaluation Report

Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for MCP Link.

$99

API endpoint ↗ Agent guide ↗ Report inaccuracy

Scores are editorial opinions as of 2026-03-06.