VS Code CopilotIDE

Sonarr (TV) MCP Server

Bring Media Management
to VS Code Copilot

Name: Sonarr (TV) MCP Server
Price: 29 USD
Availability: InStock
Rating: 0.2 (1 reviews)
Author: Vinkius

Learn how to connect Sonarr (TV) to VS Code Copilot and start using 18 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

GDPR Free for Subscribers

Add SeriesDelete Episode FileDelete Queue ItemDelete SeriesGet EpisodeGet Episode FileGet HealthGet HistoryGet QueueGet SeriesGet System StatusList CommandsList Episode FilesList EpisodesList SeriesStart CommandUpdate EpisodeUpdate Series

Unlock for AI Agents

Ask AI about this MCP Server ChatGPT Claude Perplexity

Compatible with every major AI agent and IDE

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

+ other MCP clients

What is the Sonarr (TV) MCP Server?

Connect your Sonarr instance to any AI agent to take full control of your TV media library through natural conversation.

What you can do

Library Management — List all series, add new shows via TVDB ID, and update monitoring status or quality profiles.
Episode Tracking — Fetch details for specific episodes, list all episodes in a series, and manage their monitored state.
File Control — List and delete physical episode files directly from your storage to manage disk space.
Activity Monitoring — Access download history and current queue status to see what's downloading or stalled.
System Health — Check Sonarr's connectivity, system status, and internal health metrics to ensure smooth operation.

How it works

Subscribe to this server
Enter your Sonarr URL and API Key
Start managing your media library from Claude, Cursor, or any MCP-compatible client

Who is this for?

Media Enthusiasts — manage your library, check episode statuses, and clean up files without opening the web interface
Home Lab Users — automate show tracking and monitor download health via simple chat commands
Automation Fans — integrate your media server workflows into your daily AI assistant routines

Built-in capabilities (18)

add_series

Adds a new series to the library

delete_episode_file

Deletes an episode file from disk

delete_queue_item

Removes an item from the queue

delete_series

Removes a series from the library

get_episode

Returns a specific episode by its ID

get_episode_file

Returns a specific episode file

get_health

Returns any health check warnings or errors

get_history

Access the history of grabbed and imported episodes

get_queue

Returns all items in the download queue

get_series

Returns a specific series by its ID

get_system_status

Returns system information (version, OS, paths)

list_commands

Returns all currently running commands

list_episode_files

Returns all episode files for a series

list_episodes

Returns all episodes for a specific series

list_series

Returns all series in the library

start_command

g., SeriesSearch, RescanSeries, RefreshSeries). Starts a new command

update_episode

Updates an episode (e.g., marking it as monitored)

update_series

Updates an existing series

Why VS Code Copilot?

GitHub Copilot Agent mode brings Sonarr (TV) data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 18 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

—
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
—
Project-scoped MCP configs (.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access
—
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
—
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

See it in action

Sonarr (TV) in VS Code Copilot

AI Agent→Vinkius

High Security·Kill Switch·Plug and Play

Why Vinkius

Sonarr (TV) and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect Sonarr (TV) to VS Code Copilot through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.

4,000+MCP Servers ready

<40msCold start

60%Token savings

	Raw MCP	Vinkius
Server catalog	Find and host yourself	4,000+ managed
Infrastructure	Self-hosted	Sandboxed V8 isolates
Credential handling	Plaintext in config	Vault + runtime injection
Data loss prevention	None	Configurable DLP policies
Kill switch	None	Global instant shutdown
Financial circuit breakers	None	Per-server limits + alerts
Audit trail	None	Ed25519 signed logs
SIEM log streaming	None	Splunk, Datadog, Webhook
Honeytokens	None	Canary alerts on leak
Custom domains	Not applicable	DNS challenge verified
GDPR compliance	Manual effort	Automated purge + export

Unlock for AI Agents View step-by-step setup guide for VS Code Copilot →

Enterprise Security

Why teams choose Vinkius for Sonarr (TV) in VS Code Copilot

The Sonarr (TV) MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 18 tools execute in hardened sandboxes optimized for native MCP execution.

Your AI agents in VS Code Copilot only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

Unlock for AI Agents View full Sonarr (TV) details →

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

The Vinkius Advantage

How Vinkius secures
Sonarr (TV) for VS Code Copilot

Every tool call from VS Code Copilot to the Sonarr (TV) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start

Ed25519Signed audit chain

60%Token savings

FAQ

Frequently asked questions

Can I add a new TV series to my library using this agent?

Yes! Use the add_series tool. You will need to provide the title, TVDB ID, and the root folder path where the files should be stored.

How do I check if Sonarr is running correctly or has any errors?

You can use the get_health tool to see any active health checks or get_system_status to retrieve general system information and version details.

Is it possible to see what is currently being downloaded?

Absolutely. Use the get_queue tool to list all items currently in the download queue, including their status and progress.

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.