Skip to main content
Glama
Work90210

APIFold

by Work90210
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to APIFold

No user-submitted related servers found.

    Related Servers

    • mcpify

      Amanbig
      A
      license
      C
      quality
      C
      maintenance
      Turn any REST API into an MCP server in one command. Point mcpify at an OpenAPI spec and every endpoint becomes a tool your AI agent (Claude, Cursor, Windsurf) can call — zero glue code, always in sync with the spec.
      3
      5
      MIT

    • api-to-mcp

      sgaluza
      A
      license
      Not graded
      quality
      D
      maintenance
      Turns any OpenAPI REST or GraphQL API into an MCP server, allowing AI assistants like Claude to interact with APIs without writing code.
      11 npm
      MIT

    • simple-mcp

      datj9
      A
      license
      Not graded
      quality
      C
      maintenance
      Turns any API into a curated MCP server from a single config file, enabling interaction with APIs through MCP clients like Claude Desktop.
      7 npm
      MIT

    • akyn-ai

      IlyesTal
      A
      license
      A
      quality
      D
      maintenance
      Turn any data source into an MCP server in 5 minutes. Build knowledge bases that AI assistants like Claude and Cursor can query directly.
      2
      5 npm
      22
      MIT

    • mcpify

      qualuo
      A
      license
      Not graded
      quality
      C
      maintenance
      Turns any OpenAPI specification into a fully working MCP server with a single command, enabling AI agents to call APIs without writing any glue code.
      9 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 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one lists all available servers (discovery), while the other retrieves a specific connection endpoint (retrieval). No functional overlap exists between listing a catalog and fetching a specific URL.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun pattern using snake_case (get_server_endpoint, list_servers). The verb choices ('get' vs 'list') accurately reflect the read operations and maintain predictable conventions.

    Tool Count3/5

    With only 2 tools, the surface feels minimal/thin despite the server connecting to 18 different API proxies. While functional for pure discovery (list + get), the count is borderline for the implied richness of the domain.

    Completeness4/5

    Covers the core read-only lifecycle for a directory service: discovery (list) and connection (get endpoint). Minor gap in filtering/search capabilities for the 18 servers, though listing all is acceptable at this scale.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources