Pulse-IT now ships an MCP server. Twenty three tools, covering sequences, workflows, user tasks, metrics and system health, enabling scheduled triggers, and statistics gathering. Access follows the same permission model as everything else in the platform — an assistant can be scoped to trigger workflows without touching configuration, or to read status without triggering anything.

That’s the spec sheet. If you build integrations for a living, it probably looks familiar — this is what a well-built MCP server should look like, in media or anywhere else. Standard schemas, standard auth.

Here’s what it’s actually for.

A delivery request arrives by email

A film, a platform, a deadline. Someone on the operations team reads it, opens the orchestration platform, finds the right workflow, fills in the form, triggers it, and keeps an eye on it until it lands.

None of that is hard. It’s translation. A person takes intent written in plain language and converts it into clicks. Multiply that by every request, every day, and translation becomes a real share of what an operations team actually does.

The tools above are how that translation layer disappears. You sit in Claude, or any assistant that speaks MCP, and say what you need: “Deliver this film to this platform, based on this request.” The assistant finds the sequence in Pulse-IT that does the job and triggers it. If the workflow needs a human decision along the way, it comes back and asks. You answer. It continues.

The constraint is the point

The assistant runs what you’ve already built. Your workflows, your naming, your permissions, your rules. It doesn’t invent a pipeline on the fly — it operates yours.

That constraint matters more than it sounds. An operation you can talk to is only useful if you can still trust what it does. The conversation is new but the control underneath it is not.

The question worth asking

Every vendor shipping MCP right now can list what their servers expose. Fewer are saying what happens to the person who used to do that work by hand.

The operational question is quieter and more useful: how much of your team’s week goes into translating intent into clicks? Reading a request, finding the workflow, filling the form, checking the status. That work never shows up in a cost report, because it’s spread across everyone. It’s still cost.

When you can say what you need instead, that layer goes away. The person who knows what needs to happen says so. The operation does it, inside the rules their organisation set. That’s what we mean when we say Embrace is the operating layer for media — the supply chain is the flow of content, and this is what runs it. On your terms, now in your words.

What comes next

Today the conversation runs existing workflows. Building them from a described outcome is the obvious next step, and we’re working on it.

Honestly, the bar isn’t whether a demo can produce a workflow — it’s whether your operations team would run one they didn’t draw, with the same visibility, the same log, the same cost line as everything else in production. The tools that shipped were built to that standard. The next ones will be too.

About Embrace

Embrace is the operating layer for media companies, connecting people, technology and processes since 2015. Pulse-IT and Automate-IT enable operations teams to orchestrate, automate and continuously improve complex media operations.

Our products are heavily used 24/7 by leading media groups such as Arte Studio, BCE, Be tv, CANAL+, Disney-ABC News, Euronews, Eurosport, Hearst Networks EMEA, Madison Square Garden Networks, Mediawan Thematics, M6, Mercedes-AMG, NBA, NFL Films, NHL, Omnicom Group, Orange, Red Bee Media, RTL Group, ProSiebenSat1, Sinclair, TF1, TV5MONDE, and Warner Bros. Discovery.

For more information, visit www.embrace.fr.