MCP server

Connect Claude Code, Cursor, VS Code, Codex, Claude.ai or Claude desktop to DS Manager over MCP, so your coding agent can edit, import, sync and install your shadcn design system.

Last updated 16 Nov 2026DS Manager

DS Manager is an MCP server. When you connect a coding agent to it, the agent can read and change your design systems, answer their comments, bring in a project's theme or a Figma design system, sync the shadcndesign Figma kit and install a published system into your project. Figma conversion and kit sync are not offered in ChatGPT or Codex. Every change shows in the editor, and the things you decide on, such as reviews and publishing, stay with you in DS Manager.

The design agent runs inside DS Manager. The MCP server is for an agent that runs somewhere else, such as Claude Code in your project.

Who can use it

The MCP server is part of Pro and Lifetime. A Free account can try it with 50 edits and 500 reads, once. The MCP tab shows how many are left, and your agent gets a note when 10 edits or 50 reads remain. When either runs out, your agent stays connected and is told MCP is part of Pro. DS Manager checks your plan on every call, so after an upgrade the agent carries on without signing in again. See Plans and limits.

The agent runs on your own plan with its provider, such as Claude, Cursor or Codex. MCP calls don't use the AI usage that comes with DS Manager.

In a team, a call on a paid team's system runs on the team's plan, so a Free member spends none of their own allowance there. Calls on your Personal systems, calls that name no system, and calls on a team whose plan isn't paid run on your own plan. Tokens stay personal: each person connects their own agent. See Agents in a team.

Try MCP free with 50 edits

Free accounts get 50 edits and 500 reads to try it. Pro and Lifetime accounts get the full daily limits.

Server address

Add this address to your agent:

https://manager.shadcndesign.com/api/mcp

The server uses streamable HTTP and signs you in with OAuth. In your agent's config the server is named ds-manager, and it reports its name as DS Manager.

The MCP tab in Settings

The setup lives in DS Manager. Open the account menu, choose Settings… and go to the MCP tab, between API keys and Plans. The tab has these sections:

  • Address, with a Copy address button.
  • Where your agents can work, each workspace your agents can reach, Personal and your teams, with your role and its number of systems. A workspace where your agent can only read is marked "read only", or "read only until renewed" for a team whose plan isn't paid.
  • Set up your agent, one row for each agent: Claude Code, Cursor, VS Code, Codex, Claude.ai and Claude desktop. Click a row to open its steps. Under the list, Copy setup prompt copies a prompt you paste into Claude Code, Cursor or Codex so the agent sets itself up.
  • Other connected agents, for connected agents that aren't in the list. It shows only when there is one.
  • Figma kit files, the kit file linked to each system.
  • Recent calls from your agents.
The MCP tab in DS Manager Settings with the server address, and Set up your agent listing Claude Code as Connected, the Cursor row open on its Add to Cursor button and mcp.json snippet, and closed rows for VS Code, Codex, Claude.ai and Claude desktop

A closed row says how its setup goes, such as "One command" or "One click". Once that agent is connected, the row says Connected and when it last made a call, or Signed out when it needs to connect again.

A Free account that has used its allowance sees Get Pro to connect agents in place of the setup. Its connected agents are still listed, so it can revoke them.

Connect your agent

There is a guide for six agents: Claude Code, Cursor, VS Code, Codex, Claude.ai and Claude desktop. Each one ends the same way: DS Manager opens in your browser and you approve the agent on the Allow screen. You never paste a token. Each code block in a guide has its own copy button.

Claude Code

  1. Run this command:

    claude mcp add --transport http ds-manager https://manager.shadcndesign.com/api/mcp
    
  2. In Claude Code, run /mcp, choose ds-manager and then Authenticate.

  3. Approve the agent in the browser.

Cursor

  1. In Settings, MCP, open the Cursor row and click Add to Cursor. Cursor opens and adds the server.
  2. In Cursor, choose Connect next to ds-manager.
  3. Approve the agent in the browser.

To add it by hand instead, follow Or add it by hand under the button: open Cursor Settings, then MCP, add a custom server and put this in mcp.json:

{
  "mcpServers": {
    "ds-manager": {
      "url": "https://manager.shadcndesign.com/api/mcp"
    }
  }
}

VS Code

  1. In Settings, MCP, open the VS Code row and click Add to VS Code. VS Code opens and adds the server.
  2. In VS Code, choose Start above ds-manager, then Allow when VS Code asks to sign in.
  3. Approve the agent in the browser.

To add it by hand instead, put this in .vscode/mcp.json in your project:

{
  "servers": {
    "ds-manager": {
      "type": "http",
      "url": "https://manager.shadcndesign.com/api/mcp"
    }
  }
}

Codex

  1. Run this command:

    codex mcp add ds-manager --url https://manager.shadcndesign.com/api/mcp
    
  2. Then sign in:

    codex mcp login ds-manager
    
  3. Approve the agent in the browser.

Figma conversion and Figma kit sync are not available in Codex.

Claude.ai and Claude desktop

The Claude.ai and Claude desktop guides have the same steps.

  1. Go to Settings, Connectors, Add custom connector.
  2. Name it DS Manager and paste the server address.
  3. Click Connect, then approve the agent in the browser.

Other clients

Other MCP clients that sign in with OAuth may work, but DS Manager has no guide for them. MCP clients that run inside a web page can't connect. Claude's own connectors are the exception.

The Allow screen

When your agent connects, DS Manager opens a page that asks whether to let the agent in, for example "Allow Claude Code to use DS Manager?". The browser tab's title names the agent too. The page lists what the agent will be able to do. Check the name, then click Allow, or Cancel to stop.

Disconnect an agent

In the MCP tab, open the agent's row in Set up your agent and click Revoke. An agent that isn't in the list has its own Revoke under Other connected agents. Claude.ai and Claude desktop share one connection, so connecting either one marks both rows connected, and revoking either one disconnects both.

When there are two or more connections, Revoke all appears next to the Set up your agent heading. It asks "Disconnect every agent?" first, because each agent then has to be allowed again on its own computer.

An agent stays connected until you revoke it. An agent you leave unused for 30 days is disconnected on its own.

What the agent can do

The server gives the agent 33 tools, listed here by job. ChatGPT and Codex get 30 of them, without the three Figma tools.

Start and get help

  • whoami confirms the connection and shows your name and plan.
  • get_skill gives the agent DS Manager's steps for one job: build, import, convert, figma, install, locks, components or comments. ChatGPT and Codex don't get the convert and figma steps.

Build and edit a system

  • list_systems lists your Personal systems, then each team's, with the workspace, your role in it and whether each system is published.
  • read_system sums up one system: style, colors, radius, fonts, icons, edits, lint, open comment threads and whether it is published.
  • create_system makes a new system with the default look. It counts toward your plan's system limit. Its optional workspace takes a team's id or name from list_systems to create the system in that team, where you need to be an editor or above.
  • read_tokens and read_theme read the full color table and the rest of the foundation.
  • set_tokens sets light and dark colors and adds custom tokens, in oklch or hex.
  • set_foundation changes fonts, radius, spacing, the type scale, control heights and focus. Fonts can be Google Fonts or fonts you uploaded to the system. When a name matches both, the uploaded font wins.
  • set_icons adds, renames or removes the system's custom icons, SVG icons that install next to the icon library. It also sets a line icon's stroke width and picks the icon the Spinner draws. Adding icons and picking the Spinner's icon are part of Pro.
  • view_page describes a page as text, with contrast checks that list failing pairs first. The agent uses it to check its own work.

Each change appears in the editor as the agent makes it. All the changes in one run show as one banner that names the agent and counts the values, such as "Claude Code changed 24 values", with an Undo button that takes back the whole run. On a team's system, another member's run names them, such as "Jordan's Claude Code changed 12 values".

A system the agent creates appears without a reload. If no system is open, it opens on its own. Otherwise a toast offers Open.

Components and blocks

  • list_components, read_rules and find_rules find and read component styles as Tailwind utilities.
  • edit_rules restyles components by swapping, adding or removing utilities. An entry can hold several classes, such as px-2 py-1.5, and each is written on its own. A swap takes one class in from.
  • reset_rules puts rules back to the style's default.
  • variants adds, renames or removes a variant or size, such as a soft Button. It can also hide a built-in value with a replacement, or show it again. On Button, Toggle, Input, Textarea, Badge, Kbd and Avatar it creates a new axis, such as Avatar shape, and renames or removes it. Its answer names the file and line of any custom component left on a removed or renamed value. See Variants and states.
  • set_props sets or resets the system's own default for a kit prop, such as where Select opens or whether Dialog shows its close button. The installed component takes it as its default, and code that passes the prop still wins. See Behaviour.
  • create_component, update_component and read_component build custom components that the kit doesn't ship, in React and TypeScript. DS Manager checks each one before it saves it. The agent can also put a component in a group, archive it or restore it.
  • list_blocks lists Pro Blocks by group, Landing page, Application, E-commerce and AI, and shows which are locked.

Comments

  • read_comments reads the comment threads on a system: the open ones, the resolved ones or all of them, on one page or across the system, or one thread in full.
  • write_comment starts a thread on a page, replies to a thread, and resolves or reopens it. It also edits or deletes a comment by you or your agents.

An agent can't pin a comment to an element, so the threads it starts sit on a whole page. Its comments are signed with its name and yours, such as "Claude Code via Jordan Lee". Ask it to go through the open comments: it reads them, makes the changes, then resolves each thread with a reply that says what changed. A thread it didn't act on gets a reply that says why, and stays open.

Given a share link in place of a system, the agent can read and write comments on someone else's system while that link allows comments. Through a share link it comments but doesn't edit.

Lint locks

  • read_locks tells the agent your system's Lint locks in plain words and how to add shadcn's linter to the project.
  • read_lint_policy reads the published lint policy file.

An agent can't change or remove a lock, and it can't delete a component. Only you can, in DS Manager. In a team, only admins and the owner change locks, and an editor's agent that hits one is told "Ask an admin to unlock it."

Import a project's theme

import_project reads a shadcn/ui project and brings its theme into DS Manager. It reads:

  • components.json
  • globals.css
  • the Tailwind config
  • the fonts in the root layout
  • the files in components/ui

Your code is read, never run. The changes wait on a review page that you apply, into a new system or an existing one.

Convert a Figma design system

convert_figma brings in a design system from another Figma file, such as Untitled UI or your company's library. It is not for the shadcndesign kit. If you give it the kit file linked to your system, it refuses and points the agent to Figma kit sync. It is not offered in ChatGPT or Codex.

Give the agent the Figma file's link. The agent reads the file with Figma's own MCP tools, so your agent needs those connected. DS Manager never opens the file, and the conversion changes nothing in it.

It brings in:

  • theme tokens
  • extra colors, as custom colors
  • fonts, radius, shadows and spacing
  • the components that match a shadcn component

Components with no shadcn match are not brought in. They are listed as left out.

Converting into a new system creates it right away. Converting into an existing system opens a review page first.

Figma kit sync

figma_sync and figma_continue keep a system and its shadcndesign Figma kit file in step. There are three actions:

  • Pull brings changes from the kit into DS Manager through a review.
  • Push writes your DS Manager values into the kit after you confirm them on a review page.
  • Undo push puts back what the last push overwrote.

Figma kit sync is not offered in ChatGPT or Codex.

Sync works only with the shadcndesign Figma kit 3.0 or newer. Run it in the file that holds the kit's variables. A product file that only uses the kit as a library is refused. DS Manager is sold separately from the shadcndesign.com packages, and a kit license doesn't include DS Manager Pro.

The sync runs through your agent's own Figma MCP connection. DS Manager never talks to Figma.

Your Figma seat decides what the agent can do:

  • Push needs a Full seat on a paid Figma plan.
  • Pull works on a Dev seat.

A push edits the variables that already exist in the kit. It also draws the variants you added, such as Button size xl, and the axes you created, such as Avatar shape, as real variants in the kit's component sets. The review page lists them under "Variants in the kit", and you can untick any of them. A value that would add more than 120 variants to one set, or whose component has no set in the file, stays in DS Manager. So do Tablet and Mobile values and custom components, which the review page lists under "Not in the kit". Variants go one way: a pull brings nothing back from the component sets.

After a push that drew variants, publish the library in Figma so files that use the kit get them. When you remove a value that a push drew, the next push moves its variants into a hidden frame beside the set, and the push after that deletes them. An undo puts them back.

Each system links to one kit file. The Figma kit files section of the MCP tab shows the link, with Unlink to remove it. In a team, the link is shared by the team, and any editor can pull or push through their own agent's Figma connection.

Install into a project

install_commands gives the shadcn CLI commands for a published system and any Pro Blocks, in the right order, for npm, pnpm and other package managers. Before it runs them, the agent lists the files they will overwrite and asks you. Afterwards it runs typecheck, lint and build. See Publish and install.

Publish

publish_link doesn't publish. It returns a link that opens the system with Publish ready, and you press Publish in DS Manager. It also says which registry version is live.

Reviews

These changes wait on a review page until you apply them:

  • a project import, into a new or an existing system
  • a Figma conversion into an existing system
  • a pull from the Figma kit
  • a push to the Figma kit, which you confirm before anything is written

review_status tells the agent whether you applied it, discarded it or still have it open.

A review into a team's system belongs to the team. Every member who can edit that system can see it and apply it.

Agents in a team

Your agent signs in as you, so in a team it acts with your role there:

  • A viewer's agent reads, installs and comments. A write is refused, and the agent is told to say "You can view this team's systems but not edit them. Ask an admin for editor access."
  • An editor's agent also edits, creates systems, imports and publishes.
  • Lint locks stay with admins and the owner. An editor's agent that hits a lock is told "Ask an admin to unlock it."
  • In a team whose plan isn't paid, every agent only reads, and is told to ask the owner to renew.

Usage limits

Every account has these limits. They are per person, also in a team:

  • MCP requests: 60 a minute and 3,000 a day
  • Edits: 30 a minute and 1,000 a day
  • Imports or Figma conversions: 20 a day
  • Custom component checks: 30 a minute and 3,000 a day
  • Figma script steps: 120 a day
  • Page views (view_page): 100 a day

The daily limits reset at midnight UTC.

A Free account also has a one-time allowance of 50 edits and 500 reads, never refilled. Comment tools count like any other read or edit. Calls that fail don't count. When either runs out, DS Manager refuses each call with a sentence that MCP is part of Pro.

One call can send at most 1 MB and get back at most 100 KB, and it must finish within 60 seconds.