Skip to main content
Glama
fikri2992

MCP API Server

by fikri2992

Related Servers

Alternatives to MCP API Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that exposes HTTP methods defined in an OpenAPI specification as tools, enabling interaction with APIs via the Model Context Protocol.
      8
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      An MCP server that enables LLMs to make arbitrary HTTP requests (GET, POST, PUT, DELETE, etc.) with custom headers, bodies, and cookies, supporting JSON and error handling.
      1
      2
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      A server that translates Model Context Protocol (MCP) tool callings to traditional HTTP API requests, allowing existing HTTP APIs to be integrated into MCP territory through configurable mappings.
      1
      Apache 2.0
    • A
      license
      D
      quality
      D
      maintenance
      A meta API Gateway server that works with the Model Context Protocol (MCP), enabling AI assistants to connect to any API and access real-world data sources through standardized MCP tools.
      70
      24 npm
      12
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol Server that enables LLMs to interact with and execute REST API calls through natural language prompts, supporting GET/PUT/POST/PATCH operations on configured APIs.
      262 PyPI
      6
      Apache 2.0

    TDQS

    A3.5/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool corresponds to a distinct HTTP method (DELETE, GET, POST, PUT), with no overlap in purpose. The descriptions clearly differentiate them by the type of request they make, eliminating any ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent 'api_' prefix followed by the HTTP method in lowercase (e.g., api_delete, api_get). This pattern is uniform across all tools, making them predictable and easy to understand.

    Tool Count5/5

    With 4 tools covering the core HTTP methods (DELETE, GET, POST, PUT), the count is well-scoped for a general-purpose API server. Each tool serves a clear, essential function without redundancy.

    Completeness5/5

    The tool set provides complete coverage for basic HTTP operations, allowing agents to perform CRUD-like actions (Create via POST, Read via GET, Update via PUT, Delete via DELETE). There are no obvious gaps for a server focused on making HTTP requests.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues