Overseerr MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OVERSEERR_URL | Yes | Your Overseerr instance URL (e.g., https://overseerr.example.com) | |
| OVERSEERR_API_KEY | Yes | Your API key from Overseerr Settings → General |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_mediaA | Search movies/TV with single/batch/dedupe modes. Dedupe returns actionable status for batch processing. Status: NOT_FOUND | ALREADY_AVAILABLE | ALREADY_REQUESTED | SEASON_AVAILABLE | SEASON_REQUESTED | AVAILABLE_FOR_REQUEST |
| request_mediaA | Request media with auto-confirm for TV ≤24 eps. Single/batch with validation. Confirm: Movies auto | TV ≤24 eps auto | TV >24 eps needs confirmed:true TV needs seasons (array or "all"). "all"=no specials; [0,1,2]=with specials |
| manage_media_requestsB | Manage requests: get/list/approve/decline/delete. Supports filters and batching. Filters: all|pending|approved|available|processing|unavailable|failed |
| get_media_detailsB | Get media details. Single/batch with level control (basic/standard/full). Media/season status: 1=UNKNOWN, 2=PENDING, 3=PROCESSING, 4=PARTIALLY_AVAILABLE, 5=AVAILABLE, 7=DELETED (Seerr). Code 6 is BLOCKLISTED in Seerr or DELETED in legacy Overseerr. Request statuses use a separate enum. |
| get_servicesA | List configured Radarr/Sonarr servers. Returns ID, name, isDefault, 4K status, active defaults (directory, profile, tags). |
| get_service_detailsB | Get quality profiles, root folders, tags, and language profiles (Sonarr) for a Radarr/Sonarr server. |
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 6 tools
Each tool targets a distinct resource and action: service configuration details, service listing, request management, media search, media request submission, and media status retrieval. No two tools have overlapping purposes; an agent can confidently select the correct tool for a given task.
All tool names follow a consistent verb_noun pattern (e.g., get_service_details, manage_media_requests, search_media, request_media). The naming is uniform and predictable, making it easy to infer functionality from the name alone.
With 6 tools, the server is well-scoped for its purpose of managing media requests on Overseerr. Each tool serves a distinct function, and the count is neither too sparse nor bloated, providing a focused yet complete surface.
The tool set covers the full media request workflow: searching for media, requesting media, managing requests (get/list/approve/decline/delete), and retrieving detailed status for both services and media. No obvious gaps exist for the stated domain, and the inclusion of batch operations and status enums enhances capability.