Lode for AI agents

A remote, read-only server. Free components, blocks, docs and skills work without an account. Pro source and Pro skills unlock when you connect with a Pro token (see Pro access).

claude mcp add --transport http lode https://lodeui.com/api/mcp

{
  "mcpServers": {
    "lode": {
      "url": "https://lodeui.com/api/mcp"
    }
  }
}

{
  "servers": {
    "lode": {
      "type": "http",
      "url": "https://lodeui.com/api/mcp"
    }
  }
}

[mcp_servers.lode]
url = "https://lodeui.com/api/mcp"

Teaches the agent when to reach for Lode, how to install it, and the design rules to keep.

npx shadcn@latest add https://lodeui.com/r/lode-skill.json

Other agents can read SKILL.md directly, or paste INSTRUCTIONS.md into AGENTS.md, CLAUDE.md, or Cursor rules.

• SKILL.mdEntry point: workflow, principles, never-do list, and quick decisions
• INSTRUCTIONS.mdShort always-on rules for AGENTS.md, CLAUDE.md, or Cursor rules
• design.mdHierarchy, spacing, color, type and surfaces
• copy.mdButtons, empty states, errors and sample data that read well
• components.mdEvery component, block and template by category
• composition.mdHow to assemble screens: frame, states, forms, overlays, tables
• motion.mdDurations, springs, and when motion helps
• accessibility.mdFocus without rings, semantics, keyboard, and announcements
• responsive.mdWidths to check, overflow, tables, and touch targets
• review.mdThe checklist to run before calling UI done
• example-settings.mdA worked account settings page
• example-pricing.mdA worked pricing section with plans, comparison, and FAQ
• example-dashboard.mdA worked analytics overview with KPIs, chart, and table

Longer playbooks for whole pages and reviews. Pro members download them signed in from /api/skills, or read them through the MCP server connected with a Pro token.

• Lode Pro skillProEntry point: picks the right Pro workflow and sets up Pro access
• Full-page generationProBrief, plan region by region with every state, build, and verify a whole page, or stop at the plan
• Design system generationProA brand theme on the token set with contrast checked in both themes
• Refactor to LodeProMigrate custom, shadcn/ui, MUI, or Chakra UI to Lode with parity checks
• Motion auditProInventory every animation, assign tokens, cut motion that explains nothing
• Responsive auditProMeasure five widths, fix overflow, layout, and touch, then re-measure
• Accessibility auditProKeyboard, names, focus, contrast and announcements, fixed and re-tested

Free items install from their URL, with no setup beyond a project that has components.json:

npx shadcn@latest add https://lodeui.com/r/button.json

Items land under the components alias in components.json and import each other through the same aliases, so src/ projects and monorepo packages work as they are. npm dependencies install automatically.

Personal access tokens unlock Pro for the shadcn CLI and for AI tools. Each token uses your own license, so create one per machine or tool and revoke any of them on its own.

1. 1

   Create a token

   Open API keys in your dashboard, name the token after the tool or machine, and copy it. It is shown once.

2. 2

   Connect the MCP server with the token

   get_component then returns the full source of Pro items, get_install_command returns @lode commands, and get_skill returns Pro skills.

   Claude CodeCursorVS CodeCodex

   Terminal

   claude mcp add --transport http --scope user lode https://lodeui.com/api/mcp \
     --header "Authorization: Bearer lode_..."

   Paste your token in place of lode_… The user scope keeps it out of project files.

3. 3

   Install Pro items with the shadcn CLI

   161 Pro components, blocks, and templates install from the @lode registry.

   components.json

   {
     "registries": {
       "@lode": {
         "url": "https://lodeui.com/r/{name}.json",
         "headers": {
           "Authorization": "Bearer ${LODE_API_KEY}"
         }
       }
     }
   }

   .env.local

   LODE_API_KEY=lode_...

   Then install by name

   npx shadcn@latest add @lode/dock @lode/crm-landing

The shadcn CLI expands ${LODE_API_KEY} from your environment or .env.local; never commit the token. Each token allows 120 requests a minute and stops working when you revoke it or Pro ends. Free dependencies of Pro items resolve through the same registry, so one entry is enough.

Plain text and JSON for agents, search, and your own tooling.

• llms.txtIndex of every component and block with links to its Markdown
• llms-small.txtOverview, install, and one line per item, for small context windows
• llms-full.txtThe whole library as one Markdown file for a single context load
• Component markdownAny component or block as Markdown: add /markdown to its page URL
• Registry indexshadcn registry with 215 installable items
• CatalogMetadata for every item, including Pro: use cases, keywords, and notes, without source
• Skill indexEvery skill file as JSON

Name the job, not the markup. The agent searches Lode before it writes anything.

Build a settings page with Lode. Use the Lode MCP server to find
components for the profile form, notification switches, and a destructive
delete action. Install them with the shadcn CLI and check the page in
light and dark themes.