gibeon.ioHeadless digital signage.
Orchestrate your screens through a REST API or through a hosted MCP server for your AI agent. No CMS UI needed. Build your own pipeline. We handle content delivery, offline cache and publish state.
Two surfaces, one OAuth token · The same Supabase OAuth token works for both.
www.gibeon.io/v1
OpenAPI 3.1, Bearer auth, 60 req/min per token. Resources: players, playlists, sequences, planning, assets, asset-folders. Mutating calls return a publish_required flag so your orchestrator knows when a publish needs to go out.
www.gibeon.io/mcp
Streamable HTTP transport for MCP (JSON-RPC 2.0). Every API action exposed as a tool call for Claude, Cursor or custom agents via the Anthropic SDK. Paste it into your agent config and you are set.
Build an agent that rotates your content every week
An MCP agent that, on Monday morning, rotates last week’s top 3 content items to the other screens and sends a report on Sunday evening. No CMS tab open, no mouse click. Plus an audit trail (Pro+) that shows the agent did it, and proof-of-play that measures the real rotation.
Quota per tier
| Tier | API calls/mo | MCP tool calls/mo | Webhooks/mo |
|---|---|---|---|
| Free | 1,000 | 100 | ✗ |
| Starter (€39/mo) | 50,000 | 5,000 | 1,000 |
| Pro (€99/mo) | 500,000 | 50,000 | 10,000 |
| Business (€198/mo) | 5,000,000 | 500,000 | 100,000 |
| Agency (€249/mo) | 10,000,000 | 500,000 | 100,000 |
Frequently asked questions
What does "headless" mean for digital signage?
Headless means you orchestrate your screens programmatically without ever opening the CMS UI. Upload content, build playlists, assign screens, trigger publishes, all through the REST API or MCP tool calls. Our CMS becomes an optional inspection window, not your workspace.
Which endpoints does the Public API have?
Players, playlists (+ items + reorder), sequences (+ items + reorder), planning, assets (two-step signed-URL upload), asset-folders. Authentication via a Supabase OAuth token (Authorization Code + PKCE) as a Bearer token. 60 req/min per token.
What exactly does the MCP server do?
The MCP server is a hosted Streamable HTTP transport at www.gibeon.io/mcp that exposes every API action as a tool call for AI agents (Claude, Cursor, custom agents via the Anthropic SDK). An agent can call "list_players", "update_player_playlist" or "publish_players" as if they were local functions.
Can I use MCP on the Free plan?
Yes. 100 MCP tool calls a month on Free, 5,000 on Starter, 50,000 on Pro, 500,000 on Business and Agency. Enough to build an agent that rotates your content every week.
Is there an npm package?
There was @gibeon/mcp-server for local stdio hosting, but it is deprecated: it used the removed gib_live_ keys. Use the hosted MCP at www.gibeon.io/mcp.
How do I handle publish state in an automated pipeline?
Every mutating call on a player returns publish_required: true when the change needs a publish. Your agent or script then calls POST /v1/players/<id>/publish. No manual operator click.
Start free on the free tier
No credit card. 1,000 API calls and 100 MCP tool calls a month. Enough to build an agent that manages your content.