# jhomen368/overseerr-mcp [Health: Active]

**Category:** 🔎 Search & Data Extraction  
**Repository:** https://github.com/jhomen368/overseerr-mcp  
**GitHub Stars:** 25  
**npm Downloads (last month):** 735  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/jhomen368-overseerr-mcp

## Description
Integrate AI assistants with Overseerr and the Seerr (the unified successor) for automated media discovery, requests, and management in Plex, Jellyfin, and Emby ecosystems.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "overseerr-mcp": {
    "command": "npx",
    "args": ["-y","@jhomen368/overseerr-mcp"],
    "env": {
      "SEERR_URL": "",
      "SEERR_API_KEY": ""
    }
  }
}
```

**Requires environment variables:** `SEERR_URL`, `SEERR_API_KEY` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What jhomen368/overseerr-mcp MCP server does

The jhomen368/overseerr-mcp MCP server exposes Seerr and Overseerr operations to MCP-compatible AI clients. It connects to an existing Seerr or Overseerr instance using its URL and API key, then lets an assistant search for media, submit requests, inspect request status, and retrieve media information.

Its scope covers both individual and batch workflows. Search can process multiple titles and includes a deduplication mode intended for checking large lists, with title normalization and franchise-aware results. Request operations support movies, TV shows, selected seasons, or all seasons, with validation and an optional dry-run path. Requests can also be listed, approved, declined, or deleted.

## How it works

The server translates MCP tool calls into operations against the configured Seerr or Overseerr API. Six tools are available: `search_media`, `request_media`, `manage_media_requests`, `get_media_details`, `get_services`, and `get_service_details`.

Caching is enabled by default and has separate settings for searches, media, requests, services, and service details. Batch-oriented operations reduce the number of calls needed for title checks and lookups. Request validation includes safeguards for multi-season selections; confirmation is enabled by default when a request exceeds 24 episodes.

The implementation can run as a local Node.js process using stdio, or as a Docker container using streamable HTTP. The container exposes port 8085 by default, with MCP available at `/mcp` and a health endpoint at `/health`.

## Setup and configuration

To run jhomen368/overseerr-mcp, provide a Seerr or Overseerr URL and an API key created in the instance's General settings. Node.js 18 or newer is required for the package or source-based setup. The documented package installation uses `npm install -g @jhomen368/overseerr-mcp`, followed by an MCP client configuration that launches it with `npx`.

Docker users can run the published image and map local port 8085 to the container. This is the documented route for remote HTTP access. Building from source requires cloning the repository, installing dependencies, running the build command, and starting `build/index.js`.

Use `SEERR_URL` and `SEERR_API_KEY` for current configuration. `OVERSEERR_URL` and `OVERSEERR_API_KEY` remain supported as deprecated alternatives for legacy deployments. Optional variables control caching, cache durations and size, multi-season confirmation, HTTP mode, and the listening port.

## Tools and capabilities

- `search_media`: searches one or many titles, with deduplication mode for larger lists and automatic title normalization.
- `request_media`: submits movie or TV requests, including chosen seasons or all seasons, with validation and dry-run support.
- `manage_media_requests`: lists requests, applies filters, reports summary statistics, and performs approval, decline, or deletion actions.
- `get_media_details`: retrieves media data in basic, standard, or full detail levels and supports batch lookups.
- `get_services`: discovers configured Radarr and Sonarr servers, including defaults and 4K status.
- `get_service_details`: returns server-specific quality profiles, root folders, and tags.

## Limitations and notes

The server depends on a reachable Seerr or Overseerr deployment and a valid API key. Network access, firewall rules, and credentials must be configured outside the MCP process. Although the project supports both product names, the legacy `OVERSEERR_*` variables are scheduled for removal in version 3.0.0, so new setups should use the `SEERR_*` names.

The available service-management information concerns Radarr and Sonarr configurations exposed through Seerr or Overseerr. Docker health checks confirm the HTTP service is reachable, but they do not validate the upstream API credentials.

_Full upstream README: https://allmcps.com/mcp/jhomen368-overseerr-mcp/readme_