faceit-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FACEIT_API_KEY | Yes | Your FACEIT API key for accessing the FACEIT Data API |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| faceit_find_playerA | Look up a FACEIT player by their exact nickname to get their player_id and basic profile info. Use this first before other tools that require a player_id. |
| faceit_get_player_statsA | Get a player's lifetime CS2 stats on FACEIT (K/D, ADR, win rate, headshot %, etc.) using their player_id. |
| faceit_get_match_historyA | Get a player's recent CS2 match history (list of match ids, results, timestamps) on FACEIT. |
| faceit_get_match_statsA | Get detailed per-round, per-player stats for a specific FACEIT match (kills, ADR, KAST, headshots, rounds, etc). Use a match_id from faceit_get_match_history. |
| faceit_get_match_detailsA | Get general details for a specific FACEIT match: teams, players, competition info, status, results. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool targets a distinct resource and action: player lookup, player stats, match history, match stats, and match details. The descriptions clearly differentiate match stats (per-round/per-player numbers) from match details (general info), so an agent can reliably choose the right tool.
All tools follow a faceit_<verb>_<noun> pattern with snake_case. The only deviation is 'find_player' using 'find' instead of 'get', but this is minor and the pattern remains predictable across the set.
Five tools is well-scoped for a focused FACEIT CS2 stats server. Each tool covers a necessary lookup or retrieval step without redundancy, and the count is squarely in the ideal 3-15 range.
The tool surface covers the core read-only workflow: finding a player, retrieving their stats, listing match history, and then fetching both summary and detailed stats for a match. There are no obvious dead ends for typical use cases; the missing operations are not essential for this domain.