Let an AI Agent Set Up Your Screens
InfoSlides is agent-native. Point Claude, Claude Code or Cursor at the InfoSlides MCP server and ask it to get a screen running — it can create the workspace, upload the deck, register the display, assign a schedule and hand back the stream link, without you opening the dashboard. The same thing is a dependency-free CLI when you would rather type it yourself, and a REST API when another system should be driving.
Free to install · Works with your existing InfoSlides account
You Do Not Have to Be a Developer to Use This
If you already have an AI assistant open, the fastest way to get a screen live is to ask it. Everything the dashboard can do is exposed to the agent as a tool call.
One Command to Connect
infoslides mcp install --client claude-code writes the config for you. Claude Desktop and Cursor are one flag away. From then on, the agent simply has InfoSlides available.
Zero to a Live Screen
Workspace creation is an anonymous tool call that returns an admin key, so an agent can take you from nothing to a playing stream in one conversation — no account set up in advance.
The Backend Still Decides
Plan limits, device allowances and feature entitlements are enforced server-side. An agent cannot talk its way past them, and a leaked key cannot do more than the plan permits.
What that sounds like
Ask in Plain Language, Get a Running Screen
“Set up a lobby screen for Acme Café in portrait, put our lunch menu deck on it, and add a weather slide.” The agent provisions the workspace, uploads the deck, registers a 1080×1920 display, wires the weather source, assigns the schedule and returns the pairing code and the HLS link.
Later: “Hide the patio menu when it’s raining.” That is a visibility condition, and it is a tool call too. The screen starts behaving that way from the next render, with nothing to redeploy.
workspaces · slideshows · media · slide templates · visibility conditions · live data pushes · devices · schedules · stream links · slide previews · API keys · upgrade links
Or Drive It Yourself
One Native AOT binary, no runtime to install. It is the CLI by default and the MCP
server with --mcp — the same tools either way.
Command-Line Interface
Create workspaces, upload slideshows, register screens, assign schedules and read back stream links from your terminal. --json on any command makes the output machine-readable.
REST API & Webhooks
A documented HTTP API with an anonymous OpenAPI document at /v1/openapi.json. Push live values from your POS, inventory or booking system and the slide redraws.
Programmatic Show/Hide
Attach conditions to a slide — time of day, weekday, or a data value you push. Stock hits zero, the product slide stops playing. No one has to remember to do it.
Push Your Own Data
Data-provider API keys are push-only and scoped to a single source, so a build server or a shop-floor script can update one slide without holding credentials for the whole workspace.
Provision on Behalf of Customers
Workspace and user creation are API calls, so a reseller or platform can spin up an InfoSlides account per customer as part of its own onboarding.
Nothing Proprietary in the Way
Screens pair with a six-digit code and play standard HLS. The CLI, the API and the stream format are all things you can point other tools at.
Getting Started
Download the binary for your platform, then pick a lane.
Install
Grab the archive for your platform from the releases page. Native AOT, so there is no runtime to install alongside it.
Connect or Sign In
infoslides mcp install to hand it to an agent, or infoslides login to authenticate the CLI in your browser.
Put Something on a Screen
Upload a deck, register a device, assign a schedule — then read back the stream link and open it on the TV.
A first session
From an Empty Account to a Playing Screen
infoslides login — OAuth in the browser
infoslides tenant create "Acme Cafe" <owner-email> --save
infoslides device create "Lobby screen" --width 1080 --height 1920
infoslides schedule assign <device-id> <slideshow-id>
infoslides stream link <device-id>
Credentials resolve in a fixed order — flags, then
INFOSLIDES_API_KEY and INFOSLIDES_API_URL, then
~/.infoslides/ — so the same script runs on a laptop and in CI
without a code change.
infoslides <verb> — the CLI
infoslides --mcp — an MCP server over stdio
CLI & MCP — Common Questions
Do I need to be a developer to use the MCP server?
No. If you already use Claude, Claude Code or Cursor, one install command connects InfoSlides to it and you then ask for what you want in plain language. The CLI is there for people who would rather type the commands themselves.
Is it safe to let an AI agent manage my screens?
The agent can only do what your plan allows — limits, device allowances and feature entitlements are enforced by the backend, not by the tool descriptions. Data-provider keys are push-only and scoped to a single content source, so a script that updates one slide cannot touch the rest of the workspace.
What does the CLI cost?
Nothing. It is a free download and it works against whatever plan your workspace is on, including the free plan. Creating a workspace through it is anonymous and does not require a card.
Which MCP clients are supported?
Claude Code, Claude Desktop and Cursor have a one-command install. Any other MCP client works too — the server speaks stdio, so it is a command, an argument and an API key in that client's config file.
What do I need installed to run it?
Nothing. The binary is Native AOT compiled, so there is no runtime or package manager involved — download the archive for your platform and run it.
Can another system drive my screens without the CLI?
Yes. Everything the CLI does is a REST call, and the OpenAPI document is published at /v1/openapi.json without authentication. Push a value from your POS or inventory system and a slide can appear, change or hide in response.
Hand Your Screens to an Agent
Free to install, works with the account you already have — or with one the agent creates for you.
Download the CLIGoing further? API reference · The launch post · AI Studio, in the dashboard