Automate and extend
Tilecast connects to other tools in several ways. Choose by who is acting and which direction the data moves.
Choose a starting point
Section titled “Choose a starting point”Command-line interfaceManage screens, pairing, Playlists, settings, plugins, and Activity from a terminal or a script.
MCPLet an AI assistant or other MCP client use Tilecast, with read-only mode and confirmation for risky actions.
API access and tokensGive a script, CI job, or the CLI an expiring credential that acts as your account, then call the HTTP API.
Connect other systemsPush data into Tilecast, read fleet health, and send notifications or webhooks.
PluginsAdd optional Tilecast features from the built-in plugin catalog.
The CLI, MCP, and personal access tokens act as your own Studio account, so your role and screen access apply to everything they do. Integration tokens, notifications, and webhooks don’t act as a person. Each has a narrow, fixed purpose.
Which one do I need?
Section titled “Which one do I need?”| You want to | Use |
|---|---|
| Run Tilecast tasks from a terminal | The CLI, signed in through your browser |
| Run Tilecast tasks from a script or CI job | The CLI or the HTTP API with a personal access token |
| Let an AI assistant read or manage Tilecast | MCP, preferably with --read-only or a read-only credential |
| Keep a Manual Table in sync with another system | An integration token with Write Manual Table rows |
| Monitor screen health from Prometheus or another monitor | An integration token with Read fleet health |
| Get told when something goes wrong | Email or webhook notifications |
| Show a calendar, feed, spreadsheet, or forecast on a screen | A Data Source and a Widget |
Plugins can add their own CLI commands and MCP tools. See Commands from plugins.