Skip to main content
Claude Code is MCP-aware out of the box. Add Lavendly as a server and its tools become available in any project.

​
1. Add the server

claude mcp add lavendly \
  --command "npx" \
  --args "-y" "@lavendly/mcp" \
  --env "LAVENDLY_API_KEY=lv_live_…"
Or edit ~/.claude/mcp.json directly: 
{
  "mcpServers": {
    "lavendly": {
      "command": "npx",
      "args": ["-y", "@lavendly/mcp"],
      "env": { "LAVENDLY_API_KEY": "lv_live_…" }
    }
  }
}

​
2. Verify

claude mcp list             # 'lavendly' with 20 tools
claude mcp inspect lavendly

​
3. Use it from any project

In Claude Code:
Generate a 5-second cinematic intro for this project’s README, show the project name in cursive on a velvet background, with a quiet piano sting. Save the URL into docs/intro.md.
Claude Code uses the Lavendly MCP for the video, then its built-in file tools to write the URL into the doc.

​
Pair it with a skill

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

​
Per-project configuration

Pin a project to a specific environment by dropping .claude/mcp.json in the project root: 
{
  "mcpServers": {
    "lavendly": {
      "command": "npx",
      "args": ["-y", "@lavendly/mcp"],
      "env": { "LAVENDLY_API_KEY_REF": "LAVENDLY_STAGING_KEY" }
    }
  }
}
LAVENDLY_API_KEY_REF reads the named env var from your shell, so the key itself never lands in committed config.