lutris-source-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LUTRIS_SOURCE_MCP_POLICY_BLOCKLIST | No | Comma-separated list of blocked release groups (e.g., fitgirl) | |
| LUTRIS_SOURCE_MCP_PROWLARR_API_KEY | Yes | API key for Prowlarr | |
| LUTRIS_SOURCE_MCP_PROWLARR_BASE_URL | Yes | Base URL of Prowlarr server | |
| LUTRIS_SOURCE_MCP_POLICY_MAX_SIZE_GB | No | Maximum torrent size in gigabytes | |
| LUTRIS_SOURCE_MCP_POLICY_MIN_SEEDERS | No | Minimum number of seeders required | |
| LUTRIS_SOURCE_MCP_QBITTORRENT_BASE_URL | Yes | Base URL of qBittorrent Web UI | |
| LUTRIS_SOURCE_MCP_QBITTORRENT_PASSWORD | Yes | Password for qBittorrent Web UI | |
| LUTRIS_SOURCE_MCP_QBITTORRENT_USERNAME | Yes | Username for qBittorrent Web UI | |
| LUTRIS_SOURCE_MCP_POLICY_ALLOW_INDEXERS | No | Comma-separated list of allowed indexers; empty allows all | |
| LUTRIS_SOURCE_MCP_POLICY_FREELEECH_ONLY | No | Set to 'true' to only consider freeleech torrents from Gazelle indexers | |
| LUTRIS_SOURCE_MCP_QBITTORRENT_DOWNLOAD_DIR | No | Download directory for qBittorrent (optional, default may be from config file) |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pipeline_healthA | Verify Prowlarr + qBittorrent reachability and surface config. mutates: false |
| setupC | Write the TOML config file (first-run setup). mutates: true |
| prepare_install_sourceA | Search Prowlarr, hand off the best candidate to qBittorrent, poll until complete (5-min stall timeout, configurable), classify the tree, and return a path lutris-mcp's install_from_yaml or install_from_directory consumes directly. mutates: true |
| cancel_pipelineC | Cancel an in-flight torrent. mutates: true |
| stop_seedingC | Stop seeding without deleting on-disk files. mutates: true |
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 has a clearly distinct purpose: cancel_pipeline stops a torrent, pipeline_health checks connectivity, prepare_install_source handles full search and download, setup writes config, and stop_seeding stops seeding without deletion. No ambiguity between them.
Tools use snake_case and mostly follow a verb_noun pattern (e.g., cancel_pipeline, prepare_install_source). However, 'setup' is a single verb and 'pipeline_health' is noun_noun, introducing minor inconsistency.
With 5 tools, the set is well-scoped for a source management server. Each tool covers an essential operation without bloat or deficiency.
The tool surface covers core workflows: setup, health check, download/prepare, cancellation, and seeding control. Minor gaps like listing pipelines or updating config exist but are not critical for the intended use.