
CastHub
io.github.Cast-HubPublished by GitHub account Cast-Hubv0.1.1Updated Oct 25, 2026
Control CastHub digital signage. Manage TVs, presentations, schedules, and emergency alerts.
Overview
CastHub MCP lets an AI assistant manage a CastHub digital signage network: TVs, presentations, schedules, device groups and emergency alerts.
- What you can do
- List, rename, move and delete devices, and send or schedule remote commands to Amazon Signage Sticks, including viewing command status and toggling command plans. Create, update and delete device groups. List, create, update and delete presentations, assign them to groups, and upload image or video slides through multi-step upload tools. List and assign schedules to groups, or remove and delete them. Set, start and stop alert presentations and text alerts for all groups or a single group. Check login status, user profile and subscription details, and get a dashboard overview or the current UTC time.
- When to use it
- Use it when you run screens through CastHub and want to change content, schedules or alerts by asking an assistant instead of clicking through the dashboard. It suits fleet-wide operations such as pushing a promotion to every store or firing an emergency alert to one group.
- Requirements
- The standard path is a hosted endpoint reached with OAuth 2.0 sign-in through the assistant, with no local install. For stdio-only clients, install the npm package globally and set the CASTHUB_API_KEY environment variable from the CastHub dashboard; CASTHUB_MCP_URL can override the endpoint. A CastHub account is needed.
Installation
In SourceWeft
- Open CastHub in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
CastHub MCP Server
Model Context Protocol server for digital signage. Manage TV fleets, presentations, schedules, and emergency alerts from Claude, ChatGPT, Microsoft Copilot, Google Gemini, Cursor, or any MCP-compatible client.
What this is
CastHub MCP Server lets AI assistants directly control digital signage networks. Instead of clicking through a dashboard, you tell your assistant to update the lobby TV, push an emergency alert to all stores, or schedule next week's promotional content. The server exposes approximately 45 tools across devices, presentations, schedules, alerts, groups, and device commands, so the whole CastHub platform is reachable in natural language.
Why this exists
Digital signage management is repetitive, multi-step work that maps cleanly to natural language. Several signage platforms (Fugo, Revel Digital, Screenly) have shipped MCP support over the last year. CastHub differentiates in four ways. You connect to a hosted endpoint that uses OAuth 2.0 with PKCE and dynamic client registration, so you never paste an API key or run a local process for the standard path. Every tool ships with annotations (ReadOnly, Destructive, Idempotent) that drive proper confirmation prompts in each AI client before a disruptive action runs. Pricing is flat-rate with unlimited screens on the Pro plan rather than per-screen. And CastHub is an approved CMS partner on the Amazon Signage Stick.
Connect from any AI assistant
The CastHub MCP server is hosted at https://webapi.cast-hub.com/mcp. Authentication uses OAuth 2.0 with PKCE and dynamic client registration, so you sign in once through your AI assistant and approve access. No API keys, no local install required for the standard path.
Connection instructions for each client are in the CastHub docs:
- Connect Claude (web, Desktop, mobile)
- Connect ChatGPT
- Connect Microsoft Copilot (Copilot Studio and GitHub Copilot in VS Code)
- Connect Google Gemini (Gemini Enterprise and Gemini CLI)
- Connect Cursor
- CastHub CLI for shell automation and CI
Full setup is at https://cast-hub.com/mcp.
Local install for stdio-only clients
For MCP clients that can only launch a local stdio process, install the SDK and point it at the hosted endpoint:
The SDK is a transport shim. All tool execution happens server-side at https://webapi.cast-hub.com/mcp.
Available tools
The server exposes approximately 45 tools across Devices, Device groups, Presentations, Schedules, Alerts, Device commands, and Account and dashboard. The authoritative tool list comes from calling tools/list against the live MCP server, which is the source of truth and may have grown since this README was last updated.
The tables below reflect the tool set as of the last README update. The live server is authoritative; tool inventory may have grown since.
Devices
Device groups
Presentations
Schedules
Alerts
Account and dashboard
How CastHub MCP compares
Example usage
Update content for a specific group of screens
Prompt: "Push the new winter sale presentation to all 12 store screens for next week"
Tools called: get_presentations, assign_presentation, assign_schedule
Trigger an emergency alert
Prompt: "Start a fire drill alert across the warehouse group right now"
Tools called: start_text_alert_for_group
Audit fleet health
Prompt: "Show me all devices that have not checked in for over 24 hours"
Tools called: get_devices (filtered client-side)
Roll out content from Microsoft Copilot or Gemini
Prompt: "Schedule the new menu board presentation across the downtown cafe group for tomorrow morning"
Tools called: get_presentations, assign_presentation, assign_schedule
More walkthroughs in examples/.
Documentation
License
MIT. See LICENSE.
Contributing
Issues and pull requests welcome at github.com/Cast-Hub/mcp-server/issues. For commercial questions or partnership inquiries, contact [email protected]. For customer support questions, contact [email protected].
Source: README.md at commit 3738d8a
Tools
0Version history
1- v0.1.1LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts