Skip to main content
Cursor is MCP-aware. Configure via ~/.cursor/mcp.json (global) or <workspace>/.cursor/mcp.json (per-project). 
{
  "mcpServers": {
    "lavendly": {
      "command": "npx",
      "args": ["-y", "@lavendly/mcp"],
      "env": {
        "LAVENDLY_API_KEY": "lv_live_…"
      }
    }
  }
}
Restart Cursor. In Composer, the Lavendly tools appear and Composer can invoke them inline.
Use the per-workspace file when you maintain multiple environments, staging vs production, and want the right one auto-loaded by project.

​
Verifying the install

In a new Composer thread, ask:
What’s available right now on Lavendly?
Composer will call get_status and get_schema and show you the capability map. If you see the response, you’re wired in.

​
Pair it with a skill

The MCP server gives Cursor the tools; the skill gives it the operating manual. Loading both together turns Composer from “can call Lavendly tools” into “reliably produces good Lavendly output.”