Skip to main content
Glama
Meta API MCP Server

Meta API MCP Server

by savhascelik

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

Related MCP server: RL-MCP

API Editor Tool

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

MCP API Editor

Installation

npm install -g meta-api-mcp-server

Installation from Source Code

git clone https://github.com/savhascelik/meta-api-mcp-server.git
cd meta-api-mcp-server
npm install

Usage

As a Command Line Tool

# Load from default api-configs/ folder
meta-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 folder
meta-api-mcp-server path/to/configs/

# Load from a remote URL
meta-api-mcp-server https://example.com/api-config.json

# Load from a remote configuration list
meta-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:

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

    "flexweather": { 
      "command": "node",
      "args": [
        "server.js"
        
      ],
      "env": {
        "MCP_CONFIG_SOURCE":"api-configs/flexweather-endpoints.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:

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:

{
  "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

Available Tools

69 tools
addPetB

Add a new pet to the store

Inputs: petData (required).

Affiliates_ListallaffiliatesB

List all affiliates

Inputs: no named parameters.

Affiliates_RetrieveanaffiliateC

Retrieve an affiliate

Inputs: include, page[size], page[number], filter[status], +1 more.

cancelChargeB

Cancels an unresolved charge by its code or ID.

Inputs: charge_code_or_id (required).

Checkouts_CreateacheckoutC

Create a checkout

Inputs: body.

Checkouts_ListallcheckoutsC

List all checkouts

Inputs: no named parameters.

Checkouts_RetrieveacheckoutC

Retrieve a checkout

Inputs: page[size], page[number].

createChargeC

Creates a new charge object.

Inputs: chargeData (required).

createCheckoutC

Creates a new checkout object.

Inputs: checkoutData (required).

createPostC

Creates a new post.

Inputs: postData (required).

Customers_ListallcustomersA

List all customers

Inputs: no named parameters.

Customers_RetrieveacustomerC

Retrieve a customer

Inputs: no named parameters.

deletePostB

Deletes a specific post by its ID.

Inputs: postId (required).

DiscountRedemptions_ListalldiscB

List all discount redemptions

Inputs: no named parameters.

DiscountRedemptions_RetrieveadiC

Retrieve a discount redemption

Inputs: page[size], page[number], filter[discount_id].

Discounts_CreateadiscountC

Create a discount

Inputs: body.

Discounts_DeleteadiscountC

Delete a discount

Inputs: no named parameters.

Discounts_ListalldiscountsC

List all discounts

Inputs: no named parameters.

Discounts_RetrieveadiscountC

Retrieve a discount

Inputs: include, page[size], page[number], filter[store_id].

Files_ListallfilesC

List all files

Inputs: no named parameters.

Files_RetrieveafileD

Retrieve a file

Inputs: page[number].

findPetsByStatusB

Finds Pets by status

Inputs: status (required).

getCommentsForPostA

Retrieves all comments for a specific post.

Inputs: postId (required).

getPetByIdB

Find pet by ID

Inputs: petId (required).

getPostByIdB

Retrieves a specific post by its ID.

Inputs: postId (required).

get_v1_404D

404

Inputs: no named parameters.

HealthD

Health

Inputs: no named parameters.

LicenseKeyInstances_ListallliceB

List all license key instances

Inputs: no named parameters.

LicenseKeyInstances_RetrievealiD

Retrieve a license key instance

Inputs: page[size], page[number].

LicenseKeys_ListalllicensekeysA

List all license keys

Inputs: no named parameters.

LicenseKeys_RetrievealicensekeyC

Retrieve a license key

Inputs: include.

listChargesC

Retrieves a list of charge objects.

Inputs: limit, ending_before, starting_after.

listCheckoutsC

Retrieves a list of checkout objects.

Inputs: limit, ending_before, starting_after.

listEventsC

Retrieves a list of event objects.

Inputs: limit, ending_before, starting_after.

listPostsB

Retrieves a list of all posts.

Inputs: _limit.

OrderItems_ListallorderitemsB

List all order items

Inputs: no named parameters.

OrderItems_RetrieveanorderitemC

Retrieve an order item

Inputs: include, page[size], page[number], filter[order_id].

Orders_ListallordersB

List all orders

Inputs: no named parameters.

Orders_RetrieveanorderC

Retrieve an order

Inputs: include, page[size], page[number], filter[store_id], +2 more.

Prices_ListallpricesC

List all prices

Inputs: no named parameters.

Prices_RetrieveapriceC

Retrieve a price

Inputs: include.

Products_ListallproductsB

List all products

Inputs: no named parameters.

Products_RetrieveaproductC

Retrieve a product

Inputs: include, page[size], filter[store_id].

showChargeA

Retrieves the details of a charge by its code or ID.

Inputs: charge_code_or_id (required).

showCheckoutA

Retrieves the details of a checkout by its ID.

Inputs: checkout_id (required).

showEventB

Retrieves the details of an event by its ID.

Inputs: event_id (required).

Stores_ListallstoresC

List all stores

Inputs: no named parameters.

Stores_RetrieveastoreC

Retrieve a store

Inputs: no named parameters.

SubscripitonInvoices_ListallsubB

List all subscription invoices

Inputs: no named parameters.

SubscripitonInvoices_RetrieveasC

Retrieve a subscription invoice

Inputs: page[size], page[number], filter[status].

SubscripitonItems_ListallsubscrB

List all subscription items

Inputs: no named parameters.

SubscripitonItems_RetrieveasubsB

Retrieve a subscription items current usage

Inputs: no named parameters.

SubscripitonItems_UpdateasubscrC

Update a subscription item

Inputs: body.

Subscriptions_CancelaSubscriptiC

Cancel a Subscription

Inputs: no named parameters.

Subscriptions_ListallsubscriptiB

List all subscriptions

Inputs: no named parameters.

Subscriptions_RetrieveasubscripC

Retrieve a subscription

Inputs: include, page[size], page[number].

Subscriptions_UpdateasubscriptiC

Update a subscription

Inputs: body.

updatePostA

Updates an existing post using PUT (replaces the entire post).

Inputs: postId (required), updatedPostData (required).

UsageRecords_CreateausagerecordC

Create a usage record

Inputs: body.

UsageRecords_ListallusagerecordC

List all usage records

Inputs: no named parameters.

UsageRecords_RetrieveausagerecoC

Retrieve a usage-record

Inputs: no named parameters.

Users_RetrievetheauthenticateduB

Retrieve the authenticated user

Inputs: no named parameters.

Variants_ListallvariantsA

List all variants

Inputs: no named parameters.

Variants_RetrieveavariantD

Retrieve a variant

Inputs: include, page[size], page[number], filter[product_id].

Webhooks_CreateawebhookC

Create a webhook

Inputs: body.

Webhooks_DeleteawebhookA

Delete a webhook

Inputs: no named parameters.

Webhooks_ListallwebhooksA

List all webhooks

Inputs: no named parameters.

Webhooks_RetrieveawebhookC

Retrieve a webhook

Inputs: include, filter[store_id].

Webhooks_UpdateawebhookC

Update a webhook

Inputs: body.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    D1.9/5.0

    Scored across 69 tools

    Disambiguation2/5

    Multiple tools overlap in purpose, e.g., there are duplicate checkout tools with different naming ('listCheckouts' and 'Checkouts_Listallcheckouts'; 'createCheckout' and 'Checkouts_Createacheckout'). Tools for charges, orders, subscriptions, etc., exist but boundaries are unclear due to inconsistent naming and missing operations.

    Naming Consistency1/5

    Naming is highly inconsistent: mix of camelCase (listCharges), underscores with misspellings (SubscripitonItems_Updateasubscr), verbs like 'findPetsByStatus', and bare words like 'Health'. No consistent pattern exists.

    Tool Count1/5

    With 69 tools spanning many unrelated domains (payments, CMS, ecommerce, petstore, health, etc.), the tool count is excessive for a coherent server. A unified MCP server should focus on a single domain.

    Completeness2/5

    Coverage is inconsistent and incomplete. Some resources have CRUD (posts), but many only have list/retrieve (e.g., orders, stores, customers) with missing create/update/delete. Duplicate tools for checkouts further indicate poor completeness.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      C
      quality
      D
      maintenance
      A Model Context Protocol server that exposes over 200+ APIs from API.market as MCP resources, allowing large language models to discover and interact with various APIs through natural language commands.
      34
      35 npm
      4
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that provides AI models with structured access to external data and services, acting as a bridge between AI assistants and applications, databases, and APIs in a standardized, secure way.
      2
      -
    • F
      license
      C
      quality
      D
      maintenance
      A powerful gateway for the Model Context Protocol (MCP) that unifies AI toolchains by federating multiple MCP servers, wrapping REST APIs as MCP tools, and supporting multiple transport methods with an admin dashboard.
      1
      -