
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
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.
Installation
In SourceWeft
- Open Meta Api Mcp Server in the dashboard and add it to a workspace.
- 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:
Installation
Global Installation with NPM (Recommended)
Installation from Source Code
Usage
As a Command Line Tool
Using with Cursor or Other MCP Clients
To connect to an MCP client like Cursor, configure your mcp.json file as follows:
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.
- Export your Postman collection (in v2.1.0 format)
- Start Meta API MCP Server with the collection file:
-
The server will automatically:
- Analyze all endpoints
- Detect the authentication method
- Extract path/query parameters
- Analyze request body structure
- Create MCP tools
-
Add your API key to the
.envfile (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:
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:
API Configuration File Format
You can manually configure APIs using the following JSON format:
License
MIT
Source: README.md at commit 75e5010
Tools
0Version history
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.