Connect AI agents to your screens
HipDeck provides a workspace-scoped Model Context Protocol server for discovering, monitoring, and safely managing digital signage.
Server endpoint
https://api.hipdeck.co/mcp
The endpoint uses MCP Streamable HTTP. It is protected and will return Unauthorized when opened without credentials. MCP clients must send an authenticated JSON-RPC initialize request rather than opening the URL in a browser.
Machine-readable discovery metadata is available at https://api.hipdeck.co/.well-known/mcp.json.
What agents can do
Fleet health
See online state, heartbeat freshness, playback, device diagnostics, and recent disconnects across every display.
Remote recovery
Force a sync, refresh content, clear the player cache, or restart an online player with explicit confirmation.
Manage playlists
Create and edit canonical playlist drafts with version checks.
Publish content
Validate and publish a reviewed playlist draft.
Assign screens
Assign published playlists, schedules, or sequences to displays.
Review operations
Inspect schedules, sequences, and authenticated workspace context.
Authentication
Create a workspace-scoped public API key in Workspace → Developers. Configure the complete key as bearer authentication in the MCP client. Never paste it into a chat message or publish it in documentation.
Available scopes
Safety controls
Every mutation requires explicit confirmation. Playlist writes use optimistic version checks, and publishing or screen assignment cannot proceed without the required write scope and confirmation.
