MCP 服务器

MCP Link - Convert Any OpenAPI V3 API to MCP Server

Okay, here's the translation of "Convert Any OpenAPI V3 API to MCP Server" into Chinese, along with a few options depending on the nuance you want to convey: **Option 1 (Most Literal and General):** * **将任何 OpenAPI V3 API 转换为 MCP 服务器** * (Jiāng rènhé OpenAPI V3 API zhuǎnhuàn wéi MCP fúwùqì) This is a direct translation and suitable for most contexts. It's clear and understandable. **Option 2 (More Technical and Emphasizing the Conversion Process):** * **把任意 OpenAPI V3 API 转换成 MCP 服务器** * (Bǎ rènyì OpenAPI V3 API zhuǎnhuàn chéng MCP fúwùqì) This is very similar to Option 1, but using "把" (bǎ) can subtly emphasize the action of converting. "任意" (rènyì) is a slightly more formal way of saying "any" than "任何" (rènhé). **Option 3 (Focusing on Enabling an API as an MCP Server):** * **使任何 OpenAPI V3 API 能够作为 MCP 服务器运行** * (Shǐ rènhé OpenAPI V3 API nénggòu zuòwéi MCP fúwùqì yùnxíng) This option emphasizes the *result* of the conversion, which is that the API can now function as an MCP server. It's a bit longer but more descriptive. **Option 4 (Concise and Common in Technical Contexts):** * **OpenAPI V3 API 到 MCP 服务器转换** * (OpenAPI V3 API dào MCP fúwùqì zhuǎnhuàn) This is a more concise, noun-phrase version, common in titles or headings. It translates to "OpenAPI V3 API to MCP Server Conversion." **Which option is best depends on the specific context:** * For general communication, **Option 1** is a good choice. * If you want to emphasize the *process* of conversion, **Option 2** is suitable. * If you want to highlight the *functionality* gained after conversion, **Option 3** is better. * For a title or heading, **Option 4** is often preferred. Therefore, without more context, I recommend **Option 1: 将任何 OpenAPI V3 API 转换为 MCP 服务器** as the most generally applicable translation.

automation-ai-labs

开发者工具

访问服务器

README

MCP Link - 将任何 OpenAPI V3 API 转换为 MCP 服务器

🧩 架构

MCP Link

🤔 为什么选择 MCP Link？

当前的 AI Agent 生态系统中存在一个明显的差距：

大多数 MCP 服务器只是 Web API 的简单包装
功能接口可能不完整，具体取决于开发人员的实现
手动创建 MCP 接口既耗时又容易出错
缺乏标准化的转换流程

MCP Link 通过自动化和标准化解决了这些问题，使任何 API 都可以轻松加入 AI 驱动的应用程序生态系统。

🌟 主要特性

自动转换：基于 OpenAPI Schema 生成完整的 MCP 服务器
无缝集成：使现有的 RESTful API 立即与 AI Agent 调用标准兼容
完整功能：确保正确映射所有 API 端点和功能
零代码修改：无需修改原始 API 实现即可获得 MCP 兼容性
开放标准：遵循 MCP 规范，确保与各种 AI Agent 框架的兼容性

🌐 在线版本

访问 mcp-link.vercel.app 尝试我们的托管版本，无需安装即可快速转换和测试您的 API。

🚀 快速开始

安装

# 克隆仓库
git clone https://github.com/automation-ai-labs/mcp-link.git
cd mcp-openapi-to-mcp-adapter

# 安装依赖
go mod download

运行

# 指定端口
go run main.go serve --port 8080 --host 0.0.0.0

参数说明

s= - OpenAPI 规范文件的 URL
u= - 目标 API 的基本 URL
h= - 身份验证标头格式，格式为 header-name:value-prefix
f= - 用于包含或排除 API 端点的路径过滤表达式。语法：
- +/path/** - 包含 /path/ 下的所有端点
- -/path/** - 排除 /path/ 下的所有端点
- +/users/*:GET - 仅包含 /users/{id} 的 GET 端点
- 多个过滤器可以用分号分隔：+/**:GET;-/internal/**
- 通配符：* 匹配任何单个路径段，** 匹配零个或多个段

示例

API	MCP Link URL	身份验证方法
Brave Search	https://mcp-link.vercel.app/links/brave	API 密钥
DuckDuckGo	https://mcp-link.vercel.app/links/duckduckgo	无
Figma	https://mcp-link.vercel.app/links/figma	API 令牌
GitHub	https://mcp-link.vercel.app/links/github	Bearer 令牌
Home Assistant	https://mcp-link.vercel.app/links/homeassistant	Bearer 令牌
Notion	https://mcp-link.vercel.app/links/notion	Bearer 令牌
Slack	https://mcp-link.vercel.app/links/slack	Bearer 令牌
Stripe	https://mcp-link.vercel.app/links/stripe	Bearer 令牌
TMDB	https://mcp-link.vercel.app/links/tmdb	Bearer 令牌
YouTube	https://mcp-link.vercel.app/links/youtube	Bearer 令牌

在 AI Agents 中使用

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