Anthias integration
Anthias (by Screenly) is open-source digital signage that runs on a Raspberry Pi or PC, and each player serves its own REST API. An agent can list, add, schedule, reorder, switch and delete the images, videos, web pages, streams and YouTube videos a screen plays, upload media files, skip to the next or a given asset, read and change player settings and the display on/off schedule, read device health, turn an HDMI-CEC display on or off, and reboot or shut the device down. Each device manages its own content; ids are per device. Not exposed: asset custom headers, authentication settings, imports and migrations that take another platform's token, backup and restore, the asset content download and viewer-only routes. Authentication is HTTP Basic with the player's operator account, which must be turned on first (Settings, Authentication); the vendor advises keeping the device on a LAN or VPN, or behind a reverse proxy, never directly on the internet.
Say what should happen.
The workflow builds itself.
What you can do with Anthias
Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.
Each badge shows the default agent permission of an endpoint (allowed: an agent calls it without asking; ask first: you are asked before an agent calls it, when the agent or chat asks permission for sensitive actions; never: no agent may call it), which every user can change endpoint by endpoint in their credential settings.
Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.
Asset, 5 operations
create_assetCreate assetPOSTAgents: ask firstAdds an asset to the device's playlist; it shows on the real screen when enabled and inside its schedule. For an image or video file, call upload_file_asset first and pass its uri and ext.delete_assetDelete assetDELETEAgents: ask firstDeletes an asset from the device, removing it from the real screen's playlist.get_assetGet assetGETAgents: ask firstReturns one asset with its schedule and status; poll it after create_asset until is_processing is false to confirm a video is on air (is_active).list_assetsList assetsGETAgents: ask firstLists every asset on the device (images, videos, web pages, streams) with its schedule and whether it is playing now (is_active) or still being prepared (is_processing).update_assetUpdate assetPATCHAgents: ask firstChanges the fields you send on one asset (name, schedule, duration, enabled state, order) and leaves the others as they are; the change applies to the real screen.
Device, 2 operations
reboot_deviceReboot devicePOSTAgents: ask firstRestarts the real device (power control); nothing shows on the screen until it has booted again.shutdown_deviceShutdown devicePOSTAgents: ask firstShuts the real device down (power control); the screen stops showing content.
Device settings, 2 operations
get_device_settingsGet device settingsGETAgents: ask firstReturns the player's settings: name, time zone, date and clock format, default durations, audio output, screen rotation, shuffle, splash screen and the display power schedule.update_device_settingsUpdate device settingsPATCHAgents: ask firstChanges the player settings you send (name, time zone, durations, rotation, shuffle, display schedule) and leaves the others as they are; applies to the real device.
Device info, 1 operation
get_device_infoGet device infoGETAgents: ask firstReturns the device's health and identity: Anthias version, model, uptime, load, memory, free space, storage and power-supply health, IP and MAC addresses, display power state.
Display, 1 operation
set_display_powerSet display powerPOSTAgents: ask firstTurns the real screen on or off over HDMI-CEC (experimental; needs a CEC adapter and a display that answers CEC, else an error message comes back).
Integration info, 1 operation
get_integrationsGet integrationsGETAgents: ask firstReturns whether the device runs under balena fleet management and, if so, its balena app, device and OS details.
Media file, 1 operation
upload_file_assetUpload file assetPOSTAgents: ask firstUploads an image or video file to the device and returns its uri and ext; pass both to create_asset to put it in the playlist.
Playback, 1 operation
control_playbackControl playbackGETAgents: ask firstChanges what the real screen shows now: next, previous, or one asset (asset& followed by its asset_id). Returns a short confirmation.
Playlist, 1 operation
set_playlist_orderSet playlist orderPOSTAgents: ask firstSets the order in which the device plays its assets, from a comma-separated list of asset ids; changes the real screen's loop.
Use Anthias from Claude Code, Cursor or Codex
Connect Anthias in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Anthias operations become tools the client can call, next to every other integration you connected.
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"
[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"{
"mcpServers": {
"livecontext": {
"type": "http",
"url": "https://livecontext.ai/mcp",
"headers": {
"X-API-Key": "YOUR_API_KEY"
}
}
}
}How to connect Anthias
- Create your workspace
Sign up free. Nothing to install.
- Connect Anthias once
Add your Anthias connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
- Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.
Anthias integration FAQ
What can you do with the Anthias integration?
LiveContext exposes 15 operations on Anthias, covering asset, device, device settings and device info.
