The public Nimbus MCP server gives AI assistants the full Nimbus API. An agent can read a channel's timeline, change the schedule and check playout status with the same calls your team makes through the REST API.
An operator asks in plain language. The agent finds the asset, changes the schedule and checks the outputs, through the same Nimbus API the console and your scripts use.
The agent works with the permissions of the Nimbus user who signed in. Schedules can be validated before air, and every user and API action is written to the Nimbus audit log, so changes made by an agent can be reviewed like any other.
https://mcp.veset.tv/mcpPut the council replay on Channel 1 at 22:30 instead of the film, then tell me if the outputs are healthy.
search_assets(query: "City council replay") asset 4471 City council, replay 01:12:05 readyupdate_schedule_event(channel: "Channel 1", start: "22:30:00", asset: 4471) event updated 22:30:00 City council, replayvalidate_schedule(channel: "Channel 1") 1 gap 23:42:05 to 00:08:00 25:55get_playout_extended_status(channel: "Channel 1") playout A on air outputs 4/4 okplayout B in sync outputs 4/4 okThe council replay (1:12:05) now starts at 22:30 in place of the film. That leaves a 25:55 gap before the next event at 00:08. Should I fill it, or move the next events up? Both playouts are running and all four outputs report OK.
The same functions as the REST API, which covers the full platform.
The same tools for every Nimbus type, from FAST channels to HA and Enterprise.
The server runs at https://mcp.veset.tv/mcp. Add it to Claude, Codex or another OAuth-compatible MCP client.
One MCP connector can manage the playouts of all organisations under a service provider, such as a reseller.
The MCP server is included in every Nimbus plan and in the 7-day trial.
Schedules can be validated before air, a channel can be locked while someone edits it, and every user and API action is logged.
Add https://mcp.veset.tv/mcp to Claude, Codex or another OAuth‑compatible MCP client.
The client opens the Nimbus sign-in over OAuth. Approve the mcp:read and mcp:write permissions.
The agent picks the Nimbus API calls it needs, for example to read a timeline or change a schedule event.
Check the result in the console. The audit log lists every API action.
Move, replace or add events, or import a playlist, without opening the console.
Ask whether a channel is on air and its outputs are healthy.
Operate the playouts of several customer organisations from one connector.
Yes. It runs at https://mcp.veset.tv/mcp and works with OAuth-compatible MCP clients such as Claude or Codex. Setup instructions are on mcp.veset.tv/mcp.
With OAuth. The MCP client opens the Nimbus sign-in, and you approve the mcp:read and mcp:write permissions it asks for.
The agent works with the permissions of the Nimbus user who signed in, so role-based access applies to it as it does to that user. Schedules can be validated before air, a channel can be locked while someone edits it, and every API action is in the audit log.
Yes. It's included in every Nimbus plan and in the 7-day trial.
Yes. Nimbus logs user and API actions in its audit log, so an agent's changes show up like any other API call.
Yes. The REST API covers the full platform, for scripts and integrations.
Tell us which tasks you'd hand to an agent. The demo is an online call of 30 to 60 minutes, and we can set it up around your own workflow if you tell us beforehand.
Or email sales@veset.tv.
We'll reply to . Sales requests get an answer within five business days.