media-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LIDARR_URL | No | Base URL of the Lidarr instance. From Lidarr › Settings › General. | http://localhost:8686 |
| RADARR_URL | No | Base URL of the Radarr instance. From Radarr › Settings › General. | http://localhost:7878 |
| SONARR_URL | No | Base URL of the Sonarr instance. From Sonarr › Settings › General. | http://localhost:8989 |
| SABNZBD_URL | No | Base URL of the SABnzbd instance. From SABnzbd › Config › General. | http://localhost:8080 |
| LIDARR_API_KEY | No | Lidarr API key. From Lidarr › Settings › General. If unset, Lidarr tools are disabled. | |
| MEDIA_MCP_HOST | No | Host to bind when using `streamable-http`. Use `0.0.0.0` for LAN access. | 127.0.0.1 |
| MEDIA_MCP_PORT | No | Port to bind when using `streamable-http`. | 8765 |
| RADARR_API_KEY | No | Radarr API key. From Radarr › Settings › General. If unset, Radarr tools are disabled. | |
| SONARR_API_KEY | No | Sonarr API key. From Sonarr › Settings › General. If unset, Sonarr tools are disabled. | |
| SABNZBD_API_KEY | No | SABnzbd API key. From SABnzbd › Config › General. If unset, SABnzbd tools are disabled. | |
| MEDIA_MCP_TIMEOUT | No | HTTP timeout in seconds. | 30 |
| MEDIA_MCP_ENV_FILE | No | Path to an alternative env file. | ./.env |
| MEDIA_MCP_READ_ONLY | No | Set to `true` to hide every tool that changes something. | false |
| MEDIA_MCP_TRANSPORT | No | Transport to use: `stdio` or `streamable-http`. | stdio |
| MEDIA_MCP_BEARER_TOKEN | No | Bearer token required for LAN access. Generate one with `uv run media-mcp new-token`. Without a token, the server refuses to listen beyond localhost. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Tools for a home media stack. Tool names are prefixed by service: sonarr_* (TV), radarr_* (movies), lidarr_* (music), sabnzbd_* (download client). Only configured services are available; call media_services to see which. To add media, look it up first (e.g. sonarr_lookup_series) and pass the returned id to the add tool.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| media_servicesA | Which media services are configured, and whether write tools are enabled. |
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 1 tool
With only one tool there is no risk of selecting the wrong one, so ambiguity is essentially eliminated. However, the description is a question rather than an action, leaving it slightly unclear whether the tool merely reports configuration or also enumerates services/write capabilities.
The single name 'media_services' is a noun phrase rather than a verb_noun action pattern (e.g. list_media_services, get_config). It is readable and unambiguous, but with one tool no consistent convention can be established.
A server named media-mcp with exactly one tool is a poor scope fit; the only capability is a configuration/diagnostic check. The server implies media operations (list, upload, search, manage), which a single tool cannot represent.
The surface exposes no media lifecycle operations at all — no listing, retrieval, upload, or write actions, even though the tool references 'write tools' that don't exist here. Agents hitting this server for media work have no functional path forward.