LabscoMCP early access ↗
daanrongenMCP SERVER

Cast

Find the Chromecasts on your network and drive playback, volume and queues from the chat.

by daanrongen ↗IoT, Smart Home & Embedded HardwareCommunity

LABSCO SUMMARY

No key, no account, no cloud round trip.

It speaks the protocol the receivers already speak, on your own network, which is why there is nothing to configure. Start with discovery — every other tool needs a device from that list, and it is also the fastest way to find out whether your client machine is on the same subnet as the speakers.

What it is

A Google Cast controller over stdio. It discovers Cast receivers on the local network by mDNS and talks to them directly with the castv2 protocol — no cloud account in the path.

What you get

  • 17 tools in five groups
  • Discovery: discover_devices scans the local network for Cast-enabled 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

Requirements

The npm package @daanrongen/cast-mcp, version 1.1.4, launched with bunx @daanrongen/cast-mcp; Claude Code takes claude mcp add cast. No environment variables and no API keys at all. What it does need is to be on the same local network as the receivers, since discovery is mDNS.

Setup effort

One command — bunx @daanrongen/cast-mcp