Skip to main content
Glama
grobinson3108

MCP Server: SaaS Gateway

by grobinson3108
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to MCP Server: SaaS Gateway

No user-submitted related servers found.

    Related Servers

    • OpenAPI MCP Server

      luciVuc
      A
      license
      Not graded
      quality
      D
      maintenance
      A generic MCP server that dynamically converts OpenAPI-defined REST APIs into tools for LLMs like Claude. It supports multiple authentication methods and transport protocols, enabling seamless interaction with any OpenAPI-compliant API.
      8 npm
      MIT

    • MCP Data Gateway

      Chawengwit
      F
      license
      Not graded
      quality
      D
      maintenance
      A unified data gateway MCP server that enables Claude to interact with multiple external REST and GraphQL APIs through OAuth 2.0 authentication.
      -

    • life-agent-mcp

      cbolden15
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables turning any personal-assistant REST backend into Claude-ready tools via a single MCP server, providing 38 tools for communications, finance, health, and more.
      MIT

    • InfraClaude

      batu-sonmez
      A
      license
      B
      quality
      D
      maintenance
      An MCP server that enables Claude to manage infrastructure across Kubernetes, Docker, Prometheus, and Terraform through natural language. It provides over 42 specialized tools with a safety-first design, including risk-based command classification and audit logging.
      43
      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.5/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one fetches a resource by ID, the other lists all apps configured in the gateway. There is no overlap in functionality.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun pattern using snake_case (example_get_resource, gateway_list_apps), maintaining predictable naming.

    Tool Count3/5

    With only 2 tools, the server is at the low end of the borderline range. While not extreme, it feels thin for a SaaS gateway that would typically require more operations.

    Completeness2/5

    The tool set is missing essential CRUD operations for resources, app management (create, update, delete), and configuration details. Agents would fail when trying to perform common gateway tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources