Skip to main content
Glama
Mooooooon

hltv-csgo-mcp

by Mooooooon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to hltv-csgo-mcp

No user-submitted related servers found.

    Related Servers

    • liquipedia-dota2-mcp

      Mooooooon
      A
      license
      A
      quality
      C
      maintenance
      Read-only MCP server for sourced Dota 2 tournament, team, player, schedule, and result data from Liquipedia, with revision-level metadata and caching.
      5
      6 npm
      1
      MIT

    • ValorLens

      saphire112211
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for Valorant esports analytics that exposes structured metrics and database query tools, enabling AI-assisted match analysis, player profiling, scouting reports, and coaching insights.
      Apache 2.0

    • nba-mcp

      ufo2243
      A
      license
      A
      quality
      C
      maintenance
      MCP server for NBA live data and stats, providing read-only tools to query live scores, box scores, player info, standings, and more from NBA.com.
      15
      16 npm
      1
      MIT

    • Valorant MCP Server

      SeijiMatsumoto
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server for Valorant match analysis. Enables fetching player stats, match history, agent performance, and more via Henrik's Valorant API.
      -
    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

    A4.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a distinct purpose: search entities, list matches, and get match details. There is no overlap or ambiguity in their intended use. The descriptions clearly separate the search/filter/get workflow.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern: search_hltv_entities, list_hltv_matches, get_hltv_match. The verb clearly indicates the action and the noun indicates the resource, making the pattern predictable.

    Tool Count4/5

    Three tools is on the lower end but still appropriate for a focused HLTV match data server. The set covers the core workflow of search, list, and detail without feeling excessive. A few more tools could be justified, but the current count is reasonable.

    Completeness4/5

    The tools cover the primary workflow: finding entities, listing matches, and retrieving match details. Missing are direct event or player detail endpoints, but search_hltv_entities provides entity discovery. The core match lifecycle appears adequately covered with minor gaps.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources