Skip to main content
Glama
Ahmedelmonady

Gameball MCP Server

Related Servers

Alternatives to Gameball MCP Server

No user-submitted related servers found.

    Related Servers

    • F
      license
      A
      quality
      C
      maintenance
      MCP server for GoHighLevel documentation, enabling agents to search docs, list endpoints, and fetch focused API details without loading large files.
      7
      1
      -
    • F
      license
      A
      quality
      C
      maintenance
      A read-only MCP server that exposes Automeli's public API documentation (v2 canonical, v1 frozen) to LLMs via fetch and cache over www.automeli.com artifacts. It enables listing, searching, and retrieving endpoints, OpenAPI specs, error explanations, code snippets, and end-to-end flow guides.
      7
      -
    • F
      license
      B
      quality
      D
      maintenance
      Provides access to all 471+ DigitalOcean API endpoints through an MCP server that dynamically extracts them from the OpenAPI specification, enabling search, filtering, and direct API calls with proper authentication.
      6
      1
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server for API discovery and execution with a token-efficient search -> execute workflow over OpenAPI, Google Discovery, and optional native GraphQL and gRPC sources.
      69 npm
      12
      Apache 2.0

    TDQS

    C2/5.0

    Scored across 40 tools

    Disambiguation3/5

    Many tools target distinct resources (balance, tier progress, referrals, activities), but overlaps exist: getCustomer vs getCustomerDetails, removeCustomerTags vs removeCustomerTag, and the docs-lookup-topic/search-docs and get-doc/get-tutorial pairs could confuse agents.

    Naming Consistency2/5

    The tool set mixes two conventions: docs tools use hyphenated lowercase with a docs- prefix (e.g., docs-lookup-topic), while API tools use camelCase verbs (e.g., createCustomer, getCustomer). Pluralization is also inconsistent (removeCustomerTags vs removeCustomerTag).

    Tool Count2/5

    40 tools is excessive for a single server, especially with ~15 getCustomer* variations. This makes selection harder and suggests tools could be consolidated into parameterized endpoints.

    Completeness3/5

    The server covers a broad range of Gameball operations (customers, orders, campaigns, referrals), but lacks obvious operations like updating a customer or fetching a single order. Documentation tools are comprehensive, but the API surface is not fully CRUD-complete.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues