The Leed plugin teaches Claude Code how to build, preview and publish your Leed website, change CMS settings and manage assets, and gives it the Leed documentation. One command, /leed:setup, installs and connects everything else.
What you need
- Claude Code, in the terminal, in your IDE, or in the Code tab of the Claude desktop app
- Node.js 22 or later
- git 2.31 or later
- Bun, which the Leed CLI runs on
- A Leed account with developer access to your company, which an administrator grants (see Billing and Developer Access). Setting up your site’s files needs it.
/leed:setup checks Node, git and Bun and tells you how to install anything that is missing.
1. Install the plugin
In Claude Code, run:
/plugin marketplace add leed-ai/ai-plugins
/plugin install leed@leed2. Run /leed:setup
/leed:setupIt works through seven steps. Each one checks first and only changes something when the check fails, so it is safe to run again at any time. On a machine that is already set up it reports everything green and changes nothing.
- Node, git and Bun. If one is missing or too old, setup tells you how to install it for your system and stops. Install it, open a new terminal, and run
/leed:setupagain. - The Leed CLI. Setup installs
leedwith Bun (bun install -g @leed-ai/cli), at the same version as the plugin, or upgrades the one you have to match. If your CLI is already newer than the plugin, setup leaves it alone and tells you to update the plugin instead. - Sign in and set up your site. Setup checks whether you are signed in and whether your site is set up. If you need to sign in, it asks you to run
leed setup --env productionyourself: a browser opens, you sign in and choose your company, and the CLI asks which folder to keep your site in (~/leedby default) and checks out your site’s files there. If you are already signed in, setup asks which company to use and sets the site up for you. If you work for several companies, sign in once for each withleed setup --env production --new-login. - Your site. Setup asks the CLI which sites are set up on this machine (
leed site list) and reports where your site’s checkout is. You can move the folder later: the CLI finds it again the next time you run aleedcommand inside it. - Connect your CMS. Setup runs
leed mcp add --cms, which connects Claude to your company’s CMS. With one company it is available in every project; with several, it is added to each site’s folder so each site talks to its own company. - Leed documentation (optional). Setup asks once whether to add the Leed documentation server, so Claude can look things up in the Leed docs. It remembers your answer and does not ask again.
- Auto-update. Setup asks whether you want the plugin to update itself. It is off unless you say yes.
3. Sign in to your CMS from Claude
The first time, Claude needs your permission to use your CMS:
- Restart Claude Code, or start a new session, so it picks up the new server.
- Run
/mcp, choose your Leed CMS server, and sign in in the browser window that opens.
You only do this once per machine. How the CMS server is bound to your company is in Connecting to the Operator MCP.
4. Build your site
Ask Claude to build your site, or run /leed:site-onboarding. Claude asks about your business, proposes your pages, menus and search, and once you say yes, sets up your menus, theme and fonts and writes starter templates for your header, footer and home page. It adds a blog or documentation with /leed:create, and finishes by checking the result on your staging site. What each of the plugin’s skills does is in The Leed Plugin for Claude: Skills.
No Leed account yet?
You can build your whole site on your own machine first. Ask Claude to start a sandbox site, or run leed site init --sandbox yourself: it makes a local Leed site that builds and previews at http://localhost:8080 with no account, and Claude can design it, import a Claude Design handoff into it or migrate your existing docs into it. When you are happy with it and have an account, run /leed:site-sandbox-move: Claude creates everything the site needs in your CMS and moves the site into it. See Sandbox Sites.
Keeping up to date
The plugin and the CLI are released together and should always be the same version. When you start Claude Code, the plugin checks. If they match you see nothing; if not you see one line telling you what to do:
| The line says | Do this |
|---|---|
| the Leed CLI is older than the plugin | run /leed:setup |
| the Leed plugin is older than the CLI | run claude plugin update leed@leed, then restart Claude Code |
| they are different builds | run /leed:setup |
Turn on auto-update
Claude Code does not update third-party plugins automatically unless you turn it on. Run /plugin, open Marketplaces, select leed, and choose Enable auto-update. Claude Code then updates the plugin when it starts.
Organizations can turn auto-update on for everyone, and lock it, through Claude Code managed settings. See the For organizations section of the plugin’s README.
Using Claude Desktop chat?
Chat in the Claude desktop app has no terminal, so Claude cannot install the Leed CLI there, or build and push your site. It can still plan your site and set up your CMS settings over MCP. To finish, open the Code tab, or install Claude Code, and run /leed:setup.
Not using Claude?
You can use the Leed CLI on its own. See Get Started with the Leed CLI.