qui-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| QUI_URL | Yes | qui host, optionally including a reverse-proxy base path; /api is appended automatically | |
| QUI_API_KEY | No | API key sent as X-API-Key; omit only when qui authentication is intentionally disabled |
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 |
|---|---|
| qui_systemD | qui system operations on qui. Pass
|
| qui_cross_seedA | qui cross seed operations on qui. Pass
|
| qui_torrentsB | qui torrents operations on qui. Pass
|
| qui_torznabD | qui torznab operations on qui. Pass
|
| qui_instancesB | qui instances operations on qui. Pass
|
| qui_dir_scanA | qui dir scan operations on qui. Pass
|
| qui_rssA | qui rss operations on qui. Pass
|
| qui_automationsB | qui automations operations on qui. Pass
|
| qui_backupsB | qui backups operations on qui. Pass
|
| qui_categories_tagsB | qui categories tags operations on qui. Pass
|
| qui_orphan_scanC | qui orphan scan operations on qui. Pass
|
| qui_torrent_creatorB | qui torrent creator operations on qui. Pass
|
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 12 tools
The 12 tools are organized around fairly distinct functional domains (torrents, RSS, torznab, backups, etc.), so misselection is rare. The main ambiguity is `qui_system`, which acts as a catch-all for auth, licenses, arr instances, notifications, and settings, and could be confused with `qui_instances` when an agent is looking for instance management.
All tools follow a consistent lowercase `qui_<domain>` pattern, and the underlying operations use a uniform CRUD-style naming convention such as `create_*`, `list_*`, `update_*`, and `delete_*`. There is no mixing of naming styles or unpredictable casing.
Twelve tools is within the ideal 3-15 range, and each tool maps to a meaningful resource area of the qui application. Even though several tools expose a large number of sub-operations, the tool count itself is well-scoped for the server's broad purpose.
The surface covers CRUD and lifecycle operations across most major domains: instances, torrents, cross-seed, torznab, RSS, automations, backups, scanning, categories, and tags. A few direct actions like explicit torrent deletion are only available through generic bulk-action endpoints, but overall the coverage is strong with few dead ends.