Skip to main content

​
1. Locate the config file

OSPath
macOS~/Library/Application Support/Claude/claude_desktop_config.json
Windows%APPDATA%\Claude\claude_desktop_config.json
If the file doesn’t exist, create it.

​
2. Add the Lavendly MCP server

{
  "mcpServers": {
    "lavendly": {
      "command": "npx",
      "args": ["-y", "@lavendly/mcp"],
      "env": {
        "LAVENDLY_API_KEY": "lv_live_…"
      }
    }
  }
}
That’s it. The server installs itself on first launch through npx; no clone, no build.

​
3. Restart Claude Desktop

After restart, you’ll see a tools indicator in the input box. Ask:
“List my Lavendly workflows.”
Claude calls the MCP server, returns your workflows, and offers to create or render one for you.

​
Pair it with a skill

The MCP gives Claude the tools. To get good results consistently, correct call order, idempotency keys, cost-aware decisions, load a Lavendly skill alongside the MCP. See Agent skills.

​
A first conversation

Once installed, try this:
Make me a 5-second video: a sleepy fox in a bookshop discovering an old map. Narrate it in a warm storyteller voice, “Some maps lead nowhere. This one led home.” Add a soft acoustic underscore. Captions on. Send me the URL when it’s done.
Claude works through six tool calls, workflow create → voiceover attach → music attach → mix configure → render → poll, and returns the final URL. The same workflow shows up on your canvas, fully editable, if you want to keep iterating manually.

​
Troubleshooting

Your config file likely has a JSON syntax error. Claude Desktop silently ignores invalid configs. Open the file in a JSON-aware editor.
Verify your API key, the skill emits a clear error message on the first call if LAVENDLY_API_KEY is missing or invalid.
Replace "command": "npx" with an absolute path: which npx. Common on macOS when Claude Desktop launches without a login shell.