Skip to main content
Glama
aserper

Jellyseerr MCP Server

by aserper

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
JELLYSEERR_URLYesThe URL of your Jellyseerr instance
JELLYSEERR_API_KEYYesYour Jellyseerr API key
JELLYSEERR_TIMEOUTNoRequest timeout in seconds15

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
pingA

Cheap MCP liveness check; does not probe backends.

get_servicesA

List configured services and effective write permissions; no secrets.

search_mediaC

Search Seerr/Jellyseerr by text query.

get_requestB

Inspect an existing Seerr request by its request ID.

request_mediaA

Create a Seerr request (preserves its approval workflow). Movie or TV TMDB ID; TV seasons default to [1]. Requires Seerr writes.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 5 tools

Disambiguation5/5

Each tool targets a distinct operation: creating a request, health check, listing services, searching, and inspecting a single request. There is no meaningful overlap between any pair.

Naming Consistency4/5

request_media, get_services, search_media, and get_request follow a clear verb_noun pattern. The lone 'ping' is a bare verb, a minor deviation but a conventional one for a liveness check.

Tool Count5/5

Five tools is a well-scoped set for a Jellyseerr integration, covering the essential search/request/inspect flow plus diagnostics without redundant entries. Every tool earns its place.

Completeness3/5

The surface covers search, create, and single-request inspection, but notable operations are missing: listing/filtering requests, cancelling or deleting a request, and approving/declining pending requests. Agents hit dead ends for anything beyond one-at-a-time request handling.

Maintenance

ActivityMaintained
ResponsivenessNo issues