Developers
Four ways to drive Screenly from code: the API, the CLI, the MCP server, and edge apps you build yourself.
- Subproducts title
- Tools
- Summary
- Script Screenly: the API, the CLI, the MCP server, and edge apps.
- Edge apps Build your own content: a web app packaged for a screen, with typed settings, encrypted secrets, and versioned deploys across a fleet.
- MCP server Let an AI assistant work with your workspace: 34 tools, scoped by your API token, with behaviour hints so a client knows what is destructive.
- CLI Manage screens, content, playlists and edge apps from a terminal or a CI pipeline. Table, JSON, or CSV output on every command.
- Web pages The parts of a web content item that are reachable from code: JavaScript injection, request headers and authentication, and the fields the dashboard does not expose.
- API A REST API over your workspace, built on PostgREST. Filter, select, and embed with query parameters rather than one endpoint per question.
- Overview The four programmatic surfaces, which to reach for, and how to authenticate.