Skip to main content
Glama
NicolaSpadari

rest-api-mcp

by NicolaSpadari
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to rest-api-mcp

No user-submitted related servers found.

    Related Servers

    • auto-mcp-server

      alanbuxton
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables LLMs to interact with any REST API that has an OpenAPI specification by providing a lightweight MCP server that translates between natural language and API calls.
      MIT

    • swag2mcp

      mmadfox
      A
      license
      A
      quality
      A
      maintenance
      Turn any OpenAPI/Swagger/Postman spec into an MCP server — give your LLM live access to any API.
      19
      Apache 2.0

    • mcp-from-api

      naansari
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that exposes any REST API to LLMs through runtime discovery, providing tools to browse endpoints, fetch schemas, and apply business rules without hardcoding or schema duplication.
      MIT

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

    • OpenAPI MCP Server

      cloudwarriors-ai
      A
      license
      A
      quality
      D
      maintenance
      A generic MCP server that dynamically exposes any OpenAPI-documented REST API to LLMs by auto-discovering endpoints. It provides tools for exploring API capabilities and making authenticated requests directly through natural language interfaces.
      2
      5 npm
      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

    A3.8/5.0

    Scored across 5 tools

    Disambiguation2/5

    rest_describe and rest_types have nearly identical purposes (both generate TypeScript interfaces from response structure), causing serious overlap. rest_extract also executes a full request but only returns specific fields, further blurring the lines. Only rest_request and rest_set_token are clearly distinct.

    Naming Consistency4/5

    Names follow a consistent verb_noun pattern (rest_set_token, rest_request, rest_describe, rest_types, rest_extract). However, 'rest_types' breaks the verb pattern (it's a verb+noun when 'generate_types' would be clearer), and the verbs are somewhat generic, but overall consistent.

    Tool Count4/5

    With 5 tools, the count is appropriate for a REST API client MCP server. It covers token management, basic requests, structure discovery, type generation, and field extraction — a reasonable scope. Not over or under.

    Completeness3/5

    The tool set covers the main API interaction needs but has notable gaps: there is no tool for batch requests, no explicit schema validation or endpoint discovery without making a call, and no way to list available endpoints. An agent might need to make multiple calls to understand API structure.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources