Skip to main content
Glama
molavec

MCP YAML API

by molavec
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to MCP YAML API

No user-submitted related servers found.

    Related Servers

    • MCP-OpenAPI

      rmasters
      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

    • Swagger MCP Server

      dcolley
      A
      license
      Not graded
      quality
      D
      maintenance
      A server that enables interaction with any API that has a Swagger/OpenAPI specification through Model Context Protocol (MCP), automatically generating tools from API endpoints and supporting multiple authentication methods.
      191 npm
      116
      Apache 2.0

    • mcp-server-llmling

      phil65
      A
      license
      Not graded
      quality
      C
      maintenance
      A server for the Machine Chat Protocol (MCP) that provides a YAML-based configuration system for LLM applications, allowing users to define resources, tools, and prompts without writing code.
      6
      MIT

    • 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

    • mcpbridge

      kchaturanga
      A
      license
      Not graded
      quality
      D
      maintenance
      Turns a YAML config file into an MCP server, enabling database queries, REST API calls, and knowledge base access without coding.
      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

    B3.4/5.0

    Scored across 7 tools

    Disambiguation3/5

    The tools have overlapping purposes that could cause confusion, particularly between getUsers, getUsersWithQueryParameters, and getUserWithPathParameters, which all retrieve user data but with different parameters. However, the descriptions clarify the distinctions, such as pagination vs. ID-based retrieval, helping to mitigate misselection.

    Naming Consistency4/5

    The naming is mostly consistent with a verb_noun pattern (e.g., createUser, deleteUser), but there are minor deviations in the longer names like getUsersWithQueryParameters and getUserWithPathParameters, which include additional descriptors. Overall, the pattern is readable and predictable.

    Tool Count5/5

    With 7 tools, the count is well-scoped for a user management API, covering essential CRUD operations and additional query functionalities. Each tool serves a distinct purpose, making the set appropriately sized for the domain.

    Completeness5/5

    The tool set provides complete CRUD coverage for user management, including create, read (with variations for listing and specific retrieval), update, replace, and delete. There are no obvious gaps, and the surface supports full lifecycle operations without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources