Lutris MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LUTRIS_DB_PATH | No | Path to Lutris SQLite database | ~/.local/share/lutris/pga.db |
| LUTRIS_GAMES_CONFIG_DIR | No | Path to game YAML configs | ~/.config/lutris/games |
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 |
|---|---|
| list_gamesC | List and filter games in the Lutris library with pagination |
| get_gameC | Get full details for a specific game including categories and YAML config |
| add_gameC | Add a new game to the Lutris library |
| update_gameC | Update fields on an existing game |
| remove_gameB | Remove a game from the Lutris database (does not delete files) |
| list_categoriesB | List all categories with game counts |
| create_categoryC | Create a new game category |
| assign_categoryC | Add a game to a category |
| unassign_categoryC | Remove a game from a category |
| search_service_gamesB | Search games from external services (Steam, GOG, etc.) synced in Lutris |
| get_library_statsB | Get aggregate statistics about the Lutris game library |
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 11 tools
Each tool has a clearly distinct purpose with no ambiguity. Tools like add_game, remove_game, and update_game handle different lifecycle stages, while category management tools (create_category, assign_category, unassign_category) are separate from game operations. The search_service_games tool is distinct from list_games, targeting external services versus the local library.
All tools follow a consistent verb_noun naming pattern (e.g., add_game, list_categories, update_game). The naming is uniform across all 11 tools, using clear action verbs paired with specific nouns, making it easy to predict functionality without any deviations in style.
With 11 tools, the count is well-scoped for managing a game library and categories. Each tool serves a clear purpose, such as CRUD operations for games and categories, plus utilities like search and stats, avoiding redundancy while covering the domain comprehensively.
The tool set provides complete coverage for the Lutris game management domain. It includes full CRUD for games (add, get, update, remove) and categories (create, list, assign/unassign), plus utilities for searching external services and library statistics, leaving no obvious gaps for agent workflows.