Landigo plugin for Claude Code

One install wires Claude Code to your Landigo studio: the MCP server and the Landigo skill pack together.

claude plugin marketplace add https://github.com/umutcakirai/landigo-plugin
claude plugin install landigo@landigo

Then run /landigo:auth. It prints a link, you press Approve in your browser, and this machine is signed in. No token to find, nothing to paste, no configuration.

Not a Claude Code user, or want every agent on the machine wired at once?

npx landigo-mcp install

That registers the same server with Claude Code, Codex and Cursor, whichever of them it finds.

What lands

MCP server (landigo, stdio, npx -y landigo-mcp): brand context in, the skill pack on tap, live editor tools, finished pages out as a scene graph, JSX, images or a native .fig.

Slash commands, one per skill:

Command	What it does
/landigo:design	Design into the open Landigo document: pages, product UI, components, design systems
/landigo:landing	The binding 11 rule landing recipe: fonts, page spine, assets, motion contract
/landigo:clone	Rebuild a reference site pixel perfect, or reskinned to your brand
/landigo:motion	The motion standard: tokens, stagger math, GSAP mechanics, reduced motion
/landigo:brand	Paste a URL, get a Light and Dark token collection plus a guideline deck
/landigo:attach	Wire this terminal to the studio chat panel so the browser drives the agent
/landigo:auth	Sign this machine in to your Landigo account through the browser

Each command is a thin wrapper. The full text of every skill is served by the MCP server through get_skill, read straight from mcp-server/skills/*.md in the studio repo, so there is exactly one source of truth and the commands never drift from the studio.

Authentication

The plugin asks for nothing at install time. It cannot: an empty userConfig value substituted into .mcp.json stops the MCP server from spawning at all, and a config prompt on a first install is a wall in front of a product nobody has seen yet. So the server always starts, signed out, and signing in is its own moment.

/landigo:auth runs a device link:

1. the server asks the studio for a short code,
2. you open https://landigo.dev/link?code=... and press Approve,
3. the studio mints your personal token and hands it to the waiting terminal, once.

The token lands in ~/.landigo/credentials.json, so every later session on this machine is already connected and none of it happens again. Nothing secret is ever typed into a terminal or held on a clipboard.

Other ways in, all still supported:

• npx landigo-mcp login from any terminal, same flow, opens the browser itself.
• login({ token: "lgo_..." }) if you already have a token in hand.
• npx landigo-mcp login --url https://your-studio for a self hosted studio. The URL is remembered, which is why .mcp.json no longer carries one.
• Upgrading from an older install? Your token is already in ~/.landigo/credentials.json from its first run, so nothing to redo.

/mcp shows connection status; it does not sign you in.

Keeping it current

claude plugin update landigo@landigo

Or open /plugin, pick the Marketplaces tab, choose landigo, and enable auto update.

Enable for a team

Commit this to .claude/settings.json in your repository and teammates get prompted to install on open:

{
  "enabledPlugins": { "landigo@landigo": true },
  "extraKnownMarketplaces": {
    "landigo": { "source": { "source": "github", "repo": "umutcakirai/landigo-plugin" } }
  }
}

Layout

.claude-plugin/marketplace.json      marketplace manifest (repo root)
plugins/landigo/
  .claude-plugin/plugin.json         plugin manifest
  .mcp.json                          the landigo MCP server declaration
  skills/<name>/SKILL.md             one per slash command

License: MIT.