Cast MCP Server

MCP server for Google Cast — discover devices, play media, control volume, launch apps, and manage queues over stdio. Exposed over MCP by the cast mcp mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

MCP server for Google Cast — discover devices on your local network via mDNS, play media, control volume, launch apps, and manage queues, all over stdio. No environment variables or API keys required; the server connects directly to Cast receivers using the castv2 protocol.

Its toolset

Everything the assistant can do here goes through one of these:

• Domain — Tools
• Discovery — discover_devices
• Media — play_media, pause, resume, stop, seek, get_media_status
• Queue — load_queue, queue_next, queue_prev
• Apps — get_status, launch_app, stop_app
• Volume — get_volume, set_volume, mute, unmute

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

When to reach for it

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Cast MCP's toolset — Domain, Discovery, Media and 3 more — is a fair guide to whether it matches your workflow. It is maintained by daanrongen; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the cast mcp mcp server does with a few real requests.