Cliphi + Hermes

Clips from your
Hermes agent

Hermes speaks MCP natively, so Cliphi plugs straight in. Any Hermes setup that takes custom MCP servers can add it today.

1Add the Cliphi MCP server

Add the custom server URL https://www.cliphi.com/api/mcp, or pick Cliphi from the Hermes catalog if it is listed there. Hermes opens a Cliphi sign-in the first time it connects.

2Send your video link

Hermes submits the job and polls it; the tools are async by design so nothing blocks.

3Approve the renders

Your agent shows free previews and asks before it renders anything. Clips come back as links.

Hermes questions

Over MCP, the same open protocol Hermes uses for every other tool. You add Cliphi as a server and approve the sign-in it opens the first time, and your agent can then use it the way it uses anything else.

No, and this matters for agents more than for people. Every Cliphi call returns quickly with a job id, so an agent polls for progress instead of sitting inside a request for several minutes and timing out halfway through a long video.

Cliphi splits the work in two on purpose. Finding moments and generating previews produces nothing permanent, so it is safe to let an agent do freely. Rendering is the step that creates real output, and it is the one worth putting an approval in front of.

Yes. Each video is an independent job with its own id, so an agent can hold several in flight and collect them as they finish. Cliphi does the processing, so the agent is only tracking state.

Also works from

Give your Hermes agent a clipping tool

Cliphi speaks MCP, so your agent can pick it up and start working.

Building your own agent or workflow? Developer docs