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:

npm install -g @cast-hub/mcp

{
  "mcpServers": {
    "casthub": {
      "command": "casthub-mcp",
      "env": {
        "CASTHUB_API_KEY": "your-api-key-here"
      }
    }
  }
}

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

... View full README on GitHub