meta-api-mcp-server — Claude Code MCP server: any API as a tool
Turns outside HTTP APIs into callable tools for an AI assistant, driven by a JSON file or a Postman collection. Handy when the agent needs live data from another service.
claude mcp add meta-api-mcp-server -e YOUR_API_KEY=<YOUR_API_KEY> -- npx -y meta-api-mcp-serverWhat meta-api-mcp-server does
This MCP server maps API endpoints onto tools the assistant can call on its own. You describe an API in JSON: base URL, auth method, endpoint list with parameters. GET, POST, PUT, DELETE and PATCH all work, and auth covers API keys and bearer tokens. One process serves several APIs at once, with configs read from a local file, a folder, a remote link or a list of configs.
A Postman collection saves you the hand-writing. Export it as v2.1.0 and point the server at the file, provided its name includes postman. It walks the endpoints, works out the auth scheme, pulls path and query parameters, inspects the request body and builds the tools. Your key then goes into .env, and the server tells you which variable name it expects. Visual editing of configs is done in MCP API Editor.
Global install runs through npm install -g meta-api-mcp-server, so Node.js and npm need to be present. In mcp.json you set the launch command plus the key variables; calls to the target API will fail without a working key, since the remote service rejects them.
What it helps with
- expose your own API endpoints as tools for an AI assistant
- wire up an existing Postman collection without writing code
- serve several external APIs from one MCP process
- set API key or bearer token auth in the config
- pull an API config from a remote URL instead of a local file
Example prompts for the agent
- Fetch page 2 of users from my API
- Build MCP tools from
My-API.postman_collection.json - Load the config at
api-configs/flexweather-endpoints.jsonand call the weather forecast
How to install meta-api-mcp-server
Platform CLI
claude mcp add meta-api-mcp-server -e YOUR_API_KEY=<YOUR_API_KEY> -- npx -y meta-api-mcp-serverReplace <…> with your own values
Platform CLI
codex mcp add meta-api-mcp-server --env YOUR_API_KEY=<YOUR_API_KEY> -- npx -y meta-api-mcp-serverReplace <…> with your own values
Config file
{
"mcpServers": {
"meta-api-mcp-server": {
"command": "npx",
"args": [
"-y",
"meta-api-mcp-server"
],
"env": {
"YOUR_API_KEY": "<YOUR_API_KEY>"
}
}
}
}Replace <…> with your own values
Config file
{
"servers": {
"meta-api-mcp-server": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"meta-api-mcp-server"
],
"env": {
"YOUR_API_KEY": "<YOUR_API_KEY>"
}
}
}
}Replace <…> with your own values
Platform CLI
gemini mcp add -e YOUR_API_KEY=<YOUR_API_KEY> meta-api-mcp-server npx -y meta-api-mcp-serverReplace <…> with your own values
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about meta-api-mcp-server
How to install meta-api-mcp-server in Claude Code?
Run claude mcp add meta-api-mcp-server -e YOUR_API_KEY=<YOUR_API_KEY> -- npx -y meta-api-mcp-server. Alternatively use claude mcp add --env YOUR_API_KEY=<YOUR_API_KEY> --transport stdio meta-api-mcp-server -- npx -y meta-api-mcp-server.
What does meta-api-mcp-server do?
It bridges an AI assistant and external HTTP APIs, reading a JSON endpoint description and exposing those endpoints as MCP tools.
Does it support Postman collections?
Yes, exported in v2.1.0 format. The server parses endpoints and parameters itself, and the filename has to contain the word postman.
