Skip to main content
Glama
savhascelik

Meta API MCP Server

by savhascelik
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Meta API MCP Server

No user-submitted related servers found.

    Related Servers

    • MCPilot

      ferrary7
      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
      -

    • MCP API Server

      fikri2992
      A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI assistants to make HTTP requests (GET, POST, PUT, DELETE) to external APIs through standardized MCP tools.
      4
      2
      MIT

    • RL-MCP

      rlefko
      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
      -

    • anyapi-mcp-server

      quiloos39
      A
      license
      Not graded
      quality
      D
      maintenance
      A universal MCP server that connects any REST API to AI assistants via OpenAPI or Postman specifications. It enables dynamic tool creation with GraphQL-style field selection and automatic schema inference for efficient data retrieval.
      8 npm
      6
      -

    • API-Market MCP Server

      Noveum
      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
      14 npm
      4
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources