1. Add the server
OpenClaw reads MCP servers from~/.openclaw/openclaw.json. Add a lavendly
entry under mcp.servers:
2. Restart the gateway
3. Use it from any channel
Message your OpenClaw agent like you’d text a colleague:Make a 15-second video of a sleepy fox discovering an old map in a bookshop. Narrate it in a warm voice with captions, lay a cozy ambient track under it, and send me the link when it’s rendered.The agent plans the call sequence (status → create workflow → attach voiceover → attach music → render → poll), uses Lavendly’s idempotency keys so a dropped connection never double-charges, and replies in the same chat with the URL.
4. Let it run on its own
OpenClaw’s edge is autonomy, it keeps a to-do list, a memory, and can run on a schedule. Pair that with Lavendly for hands-off pipelines:Every Monday at 9am, take the top post from my newsletter, turn it into a 30-second vertical video, and DM me the draft for approval before publishing.Lavendly’s credit ledger and monthly cost cap keep an autonomous loop from overspending, the agent checks the balance before each render and stops if it would blow the cap.
Pair it with a skill
The MCP server tells OpenClaw what tools exist. A Lavendly skill tells it how to use them well, the right call order, when to set idempotency keys, and how to read the cost preview before committing. Drop the skill into OpenClaw’s skills directory to turn “an agent that can render videos” into “an agent that produces good videos cheaply.”Next: Agent skills
The operating manual that makes the agent reliable.