Meta Api Mcp Server

io.github.savhascelikPublished by GitHub account savhascelikv1.0.1Updated Oct 24, 2026

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

Overview

AI-generated overview

A local MCP gateway that turns any HTTP API, defined in JSON configs or Postman collections, into tools an AI assistant can call.

What you can do
Load API definitions from local JSON files, folders, remote URLs or configuration lists, and expose their endpoints as MCP tools with names, descriptions and parameters. Convert exported Postman collections (v2.1.0) into MCP tools automatically, detecting auth, path and query parameters, headers and JSON request bodies. Call HTTP endpoints with GET, POST, PUT, DELETE and PATCH. Manage several APIs through one server and authenticate with API keys or bearer tokens read from environment variables.
When to use it
Useful when you want an assistant to reach a specific HTTP API without writing a dedicated MCP server, or when you already have a Postman collection you want to expose as tools. Suited to developers comfortable editing JSON configuration and environment variables.
Requirements
Runs locally over stdio; install the npm package globally or from source, so Node.js is needed. A JSON API configuration file, folder, remote URL or Postman collection must be supplied, for example via MCP_CONFIG_SOURCE. API credentials are passed through environment variables such as YOUR_API_KEY or the variable named in the configuration; network access is needed for the target APIs and any remote config URLs.
Before you install
The server holds API credentials in environment variables and sends requests to whatever endpoints the configuration defines, so review configs before use, especially ones loaded from remote URLs. Tools can issue POST, PUT, PATCH and DELETE calls, which may create, change or delete data on the target service. Configurations from untrusted sources could point at unintended hosts or expose secrets.

Installation

In SourceWeft

  1. Open Meta Api Mcp Server in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

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

Source: README.md at commit 75e5010

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.