Skip to main content
Glama
joseant1215

MCP API Engineering Lab

by joseant1215
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to MCP API Engineering Lab

No user-submitted related servers found.

    Related Servers

    • OpenAPI MCP

      pvliesdonk
      A
      license
      Not graded
      quality
      B
      maintenance
      A generic MCP server that builds its tools at runtime from any OpenAPI specification, enabling interaction with any REST API through natural language.
      MIT

    • my-mcp-server

      sp-acc
      F
      license
      Not graded
      quality
      C
      maintenance
      A playground MCP server that demonstrates exposing tools and resources to AI agents, enabling them to manage a simple user database with create and read operations.
      -

    • mcp-openapi-schema

      hannesj
      A
      license
      Not graded
      quality
      F
      maintenance
      A MCP server that exposes OpenAPI schema information to LLMs like Claude. This server allows an LLM to explore and understand large OpenAPI schemas through a set of specialized tools, without needing to load the whole schema into the context
      101 npm
      49
      MIT

    • miniMCP

      Lihn2254
      F
      license
      Not graded
      quality
      D
      maintenance
      A lightweight MCP server that connects a local AI model (Ollama) with custom CRUD tools for an in-memory database, enabling natural language database management.
      -
    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.7/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: get_database_schema retrieves schema, while the other five perform CRUD on API contracts. List, get, create, update, and delete are unambiguous.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern (list_, get_, create_, update_, delete_), and get_database_schema fits the same style. No mixed conventions.

    Tool Count5/5

    Six tools is well within the ideal range for a focused server. Each tool serves a clear purpose without unnecessary overlap or bloat.

    Completeness4/5

    The CRUD lifecycle for API contracts is fully covered (list, get, create, update, delete). However, update only modifies title/version, not arbitrary fields, and a validation tool is absent—minor gaps for full contract management.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources