What is the key difference between Overseerr MCP and Lilbee?

Overseerr MCP belongs to the Search & Data Extraction category with local stdio execution, while Lilbee belongs to the Search & Data Extraction category with local stdio execution.

How do I install Overseerr MCP or Lilbee in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Overseerr MCP and Lilbee free or paid?

Overseerr MCP operates under a Free / Open Source model (API Key required). Lilbee operates under a Free / Open Source model (API Key required).

Which MCP server has more tools and community activity?

Overseerr MCP lists 6 tools with 2 views and 23 GitHub stars. Lilbee lists 5 tools with 1 views and 54 GitHub stars.

Can I use both Overseerr MCP and Lilbee together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Overseerr MCP vs Lilbee

In-depth architectural comparison of the Overseerr MCP and Lilbee MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Overseerr MCP

Search & Data Extraction · Local stdio

Quality: 55/100 (Good) | Auth: API Key required

Lilbee

Search & Data Extraction · Local stdio

Quality: 60/100 (Good) | Auth: API Key required

Verdict Summary: Choose Overseerr MCP if you need specialized Search & Data Extraction tools running via a local process. Choose Lilbee if your workspace requires Search & Data Extraction integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Overseerr MCP when:

You need dedicated capabilities in the Search & Data Extraction domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: SEERR_URL, SEERR_API_KEY, OVERSEERR_URL, OVERSEERR_API_KEY.
Primary tools included: Batch search and deduplication mode for 50-100 titles, Batch media requests with multi-season confirmation, Manage media requests with filtering and summary stats.

Explore Overseerr MCP Details

Choose Lilbee when:

You need dedicated capabilities in the Search & Data Extraction domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: .

Feature & Specification Comparison

Specification	Overseerr MCP jhomen368 Search & Data Extraction	Lilbee tobocop2 Search & Data Extraction
Summary	Integrate AI assistants with Overseerr and the Seerr (the unified successor) for automated media discovery, requests, and management in Plex, Jellyfin, and Emby ecosystems.	Runs and manages its own local models, or uses your existing Ollama or LM Studio if you prefer. Indexes your files and code, crawls the websites you point it at, and answers with citations to the source.
Category & Scope

Tools & Capabilities Breakdown

Overseerr MCP Tools (6)

Batch search and deduplication mode for 50-100 titles

Batch media requests with multi-season confirmation

Manage media requests with filtering and summary stats

Smart caching to reduce API calls by up to 85%

Supports both Overseerr and Seerr API endpoints

Hardened Docker images with security scanning and input validation

Lilbee Tools (5)

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Overseerr MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "jhomen368-overseerr-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@jhomen368/overseerr-mcp"
      ],
      "env": {
        "SEERR_URL": "YOUR_SEERR_URL_HERE",
        "SEERR_API_KEY": "YOUR_SEERR_API_KEY_HERE",
        "OVERSEERR_URL": "YOUR_OVERSEERR_URL_HERE",
        "OVERSEERR_API_KEY": "YOUR_OVERSEERR_API_KEY_HERE"
      }
    }
  }
}

Lilbee Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "tobocop2-lilbee": {
      "command": "npx",
      "args": [
        "-y",
        "lilbee"
      ],
      "env": {
        "LILBEE_API_KEY": "YOUR_LILBEE_API_KEY_HERE",
        "LILBEE_MODEL_PATH": "YOUR_LILBEE_MODEL_PATH_HERE",
        "LILBEE_GPU_DEVICES": "YOUR_LILBEE_GPU_DEVICES_HERE"
      }
    }
  }
}

Frequently Asked Questions

Overseerr MCP is categorized under Search & Data Extraction and uses a local stdio subprocess. In contrast, Lilbee belongs to Search & Data Extraction using local stdio subprocess. Select Overseerr MCP when you need capabilities focused on search & data extraction and Lilbee when you require tools for search & data extraction.

More alternatives to Overseerr MCP More alternatives to Lilbee Search & Data Extraction category hub