September 26, 2026
.png)
Riga, 28.09.2026. Veset has released MCP 2.0 for Veset Nimbus. The update exposes the full Nimbus REST API through Veset's MCP endpoint, so any MCP-capable AI assistant can work with Nimbus, from daily scheduling to setting up new channels. Connecting is also simpler: with OAuth, users add the connector, sign in with their Nimbus account and start asking, with no manual token setup.
MCP 2.0 is available to all Nimbus customers and on the 7-day free trial. It is an additional way into the platform customers already run, not a separate product.
From first release to full API
Veset opened MCP for Veset Nimbus in August, starting with channels, playlists and output configuration. MCP 2.0 extends this to the whole API through the same endpoint, https://mcp.veset.tv/mcp.
For daily operations, an assistant can now check live status across all playouts, uptime, historical metrics, live input and MediaConnect status, as-run logs and the audit log. It can create, copy, import and export schedules, shift or transpose events to another day, replace assets, validate schedules and apply them to the channel, as well as export EPG and mark SCTE-35. Live control covers taking or skipping events, adding instant secondary events such as graphics, and switching the emergency playlist on and off. On the asset side, it can search the library, check metadata, find missing assets and follow the ingest queue.
For setup and provisioning, an assistant can create channels, create or clone playouts and change instance size. It can configure outputs, live inputs, CDN, SCTE-35 triggers and ad insertion, apply graphics projects, manage access rights, upgrade playout versions, create backups, and report usage and uptime per playout.
What this looks like in practice
A scheduler can ask: "Take yesterday's playlist for Channel 1, change every series to its next episode, move it to today and apply it to the channel." The assistant reads the playlist, finds the next episode of each series in the asset library, transposes the events to today and applies the schedule. This relies on episodes being set up as series in the library.
An operations team can start the day with: "Which of my channels have missing assets or schedule errors in the next 48 hours?" The assistant runs the missing-assets report and schedule validation across all channels and returns one list to act on.
For ad reconciliation and compliance, a question such as "What aired on Channel 2 yesterday between 14:00 and 15:00, and was every break marked with SCTE-35?" is answered from the as-run log and the schedule's SCTE-35 markers.
Users can also ask the assistant to build a channel dashboard, for example showing what's on air, the next 24 hours, live input status and playout health, built from live Nimbus data and laid out the way they want.
And for new channels: "Clone the playout of Channel 1 into a new channel with the same outputs, but with an SRT input from our new encoder." The assistant clones the playout, creates the channel and updates the live input, instead of the user going through the configuration screens one by one.
Users stay in control
Every request runs with the user's own Nimbus permissions. When connecting the assistant, users also choose view-only or edit access for it, so a view-only connection can't change anything on their channels.
How to connect
In your AI assistant, add a custom connector with the URL https://mcp.veset.tv/mcp, sign in with your Nimbus account and choose view or edit access. Then ask about your channels. Setup steps are on mcp.veset.tv/mcp, and Veset can walk teams through it on their own workflow.
