Meta Api Mcp Server

io.github.savhascelik由 GitHub 账号 savhascelik 发布v1.0.1更新于 Oct 24, 2026

You can connect any API to LLMs. This enables AI to interact directly with APIs

已验证STDIO仅桌面效率与工作流开发者工具

概览

AI 生成的概览

一个本地 MCP 网关,把 JSON 配置或 Postman 集合中定义的任意 HTTP API 转成 AI 助手可调用的工具。

可以做什么
从本地 JSON 文件、文件夹、远程 URL 或配置列表加载 API 定义,把其中的端点暴露为带名称、描述和参数的 MCP 工具。自动把导出的 Postman 集合(v2.1.0 格式)转换为 MCP 工具,识别认证方式、路径与查询参数、请求头和 JSON 请求体。以 GET、POST、PUT、DELETE、PATCH 调用 HTTP 端点。通过一个服务器管理多个 API,并用环境变量中的 API Key 或 Bearer Token 完成认证。
适用场景
当希望助手访问某个 HTTP API 又不想专门编写 MCP 服务器时适用,也适合把已有的 Postman 集合直接变成工具。适合熟悉编辑 JSON 配置和环境变量的开发者。
运行要求
以 stdio 在本地运行;需全局安装 npm 包或从源码安装,因此需要 Node.js。必须提供 JSON API 配置(文件、文件夹、远程 URL 或 Postman 集合),例如通过 MCP_CONFIG_SOURCE 指定。API 凭据通过 YOUR_API_KEY 或配置中指定的环境变量传入;访问目标 API 和远程配置 URL 需要网络。
安装前请注意
服务器在环境变量中保存 API 凭据,并向配置所定义的任意端点发送请求,使用前应检查配置,尤其是从远程 URL 加载的配置。工具可发出 POST、PUT、PATCH 和 DELETE 请求,可能在目标服务上创建、修改或删除数据。来自不可信来源的配置可能指向非预期主机或泄露密钥。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Meta Api Mcp Server,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

Meta API MCP Server

A meta API Gateway server that works with the Model Context Protocol (MCP). You can connect any API to LLMs (Claude, GPT, etc.) through MCP. This enables AI assistants to interact directly with APIs and access real-world data sources.

Features

  • 🔄 Multi-API support: Manage multiple APIs through a single server
  • 🛠️ Easily add APIs with JSON configuration files
  • 📋 Automatically convert Postman Collections to MCP tools
  • 🔌 Comprehensive support for HTTP APIs (GET, POST, PUT, DELETE, PATCH)
  • 🔒 Various authentication methods (API Key, Bearer Token)
  • 📁 Load configurations from local files or remote URLs
  • 📑 Support for configuration file lists

API Editor Tool

A user-friendly editor tool has been developed to create or edit JSON configuration files:

MCP API Editor

Installation

Global Installation with NPM (Recommended)

bash
npm install -g meta-api-mcp-server

Installation from Source Code

bash
git clone https://github.com/savhascelik/meta-api-mcp-server.gitcd meta-api-mcp-servernpm install

Usage

As a Command Line Tool

bash
# Load from default api-configs/ foldermeta-api-mcp-server
# Specify a configuration file (in the directory where you run the server, there should be a folder with this name and structured json in it)meta-api-mcp-server path/to/config.json
# Load from a specific foldermeta-api-mcp-server path/to/configs/
# Load from a remote URLmeta-api-mcp-server https://example.com/api-config.json
# Load from a remote configuration listmeta-api-mcp-server https://example.com/config-list.json
# Load from a Postman Collection ( your filename must contain the word ‘postman’, I'll bind it to a variable when I have time )meta-api-mcp-server path/to/My-API.postman_collection.json

Using with Cursor or Other MCP Clients

To connect to an MCP client like Cursor, configure your mcp.json file as follows:

json
{  "mcpServers": {    "myApiServer": {       "command": "meta-api-mcp-server",      "args": [              ],      "env": {         "MCP_CONFIG_SOURCE":"api-configs/flexweather-endpoints.json",        "API_KEY": "your-api-key-here"      }    }  }}
json
{  "mcpServers": {    "myApiServer": {       "command": "meta-api-mcp-server",      "args": [        "server.js",        "path/to/api-config.json"      ],      "env": {        "EXAMPLE_API_KEY": "your-api-key-here"      }    }  }}
json
{  "mcpServers": {
    "flexweather": {       "command": "node",      "args": [        "server.js"              ],      "env": {        "MCP_CONFIG_SOURCE":"api-configs/flexweather-endpoints.json"      }    }  }}
json
{  "mcpServers": {     "lemonsqueezy": {       "command": "node",      "args": [        "server.js"              ],      "env": {        "MCP_CONFIG_SOURCE":"api-configs/lemon-squeezy-api.json",        "LEMON_SQUEEZY_API_KEY": ""            }    }  }}

Postman Collection Conversion

Using your existing Postman collections with Meta API MCP Server is now very easy! You can use hundreds of ready-made APIs without writing a single line of code.

  1. Export your Postman collection (in v2.1.0 format)
  2. Start Meta API MCP Server with the collection file:
bash
meta-mcp my-collection.postman_collection.json
  1. The server will automatically:

    • Analyze all endpoints
    • Detect the authentication method
    • Extract path/query parameters
    • Analyze request body structure
    • Create MCP tools
  2. Add your API key to the .env file (the server will tell you which environment variable to use)

Supported Postman Collection Features

  • ✅ Multi-level folder structure
  • ✅ Bearer token authentication
  • ✅ API Key authentication
  • ✅ Path parameters
  • ✅ Query parameters
  • ✅ Headers
  • ✅ JSON request body
  • ✅ Postman variables (like {{api_url}})

API Editor Tool

A user-friendly editor tool has been developed to create or edit JSON configuration files:

MCP API Editor

With this web tool, you can:

  • Create API configurations through a visual interface
  • Edit existing JSON configurations
  • Convert Postman collections to MCP-compatible configuration files
  • Validate configuration files
  • Export your configurations as JSON

Postman Collections: You can upload your existing Postman collections to the editor tool and automatically convert them to MCP-compatible configurations. This allows you to quickly use your existing collections instead of configuring APIs from scratch.

The editor makes it easy to manage tool names, parameters, and all other configuration options.

Project Structure

The codebase is organized in a modular way to facilitate maintenance and extension:

meta-api-mcp-server/├── serve.js├── api-configs/            # Default config directory└── package.json

API Configuration File Format

You can manually configure APIs using the following JSON format:

json
{  "apiId": "my-api",  "handlerType": "httpApi",  "baseUrl": "https://api.example.com",  "authentication": {    "type": "bearerToken",    "envVariable": "MY_API_TOKEN"  },  "endpoints": [    {      "mcpOperationId": "getUsers",      "description": "Get a list of users",      "targetPath": "/users",      "targetMethod": "GET",      "parameters": [        {          "name": "page",          "in": "query",          "required": false,          "type": "integer",          "description": "Page number"        }      ]    }  ]}

License

MIT

来源:README.md,提交 75e5010

工具

0
SourceWeft 尚未在沙箱中启动过该软件包,因此其工具未知。

版本历史

1
  1. v1.0.1最新Sep 16, 2026

评分

已满足适用检查项的 40%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

    请在仓库或注册中心条目中声明许可证。