PlugWiki
seed-design logo

SEED Design Docs MCP Server: Components, Tokens and Icons for Your Assistant

OfficialLocal
Getnpm@seed-design/docs-mcpdaangn/seed-design

Lets Claude, Cursor and other assistants read the SEED Design docs, design tokens and icon library when they build your interface.

SEED is the design system of Daangn (Karrot), and this is its own docs server. It runs on your computer and fetches the public pages from seed-design.io when the assistant asks. No account or key is needed.

It only reads. The docs are partly in Korean. It is separate from the SEED Figma server in the same repository, which needs Figma access.

Good for

  • Front-end developers building with the SEED React or Lynx components
  • Designers who want the assistant to follow SEED tokens and guidelines
  • Teams that want AI-written UI to use real SEED icon and component names

Works in

12 should work

Tap an app to see how to set it up and any known problems.

Install seed-design MCP

Claude Code

  1. 1

    Copy this prompt.

    Add the seed-design MCP server to Claude Code. Run this command:
    
    claude mcp add seed-design -- npx -y @seed-design/docs-mcp
    
    Then check that it loaded and tell me if I need to sign in or restart.
  2. 2

    Paste it into Claude Code. It shows the change and asks before running it.

Requires Node.js.

Built from the package data we hold. Not yet tested by us.

Tools

  • Lists the doc sections and their categories

    Returns the five documentation sections (react, docs, breeze, ai-integration, lynx) with their categories and the endpoints behind them, plus example calls. The assistant is told to call it first.

    Try: “What parts of the SEED docs can you read?”

    Read · discover_seed_docs

  • Lists the documents in one section

    Fetches the section's index from seed-design.io and lists each document's title and path, grouped by category. You can filter by a category such as components or foundation.

    Try: “List the component docs in the react section.”

    Network · list_docs

  • Reads one SEED document

    Downloads one document by section and path, for example components/button, and returns its text. Use it after the list tool to find the path.

    Try: “Show me the SEED Button docs from the react section.”

    Network · get_doc

  • Reads a whole section at once

    Downloads every document of one section as a single combined text. It can be very long, so it suits a full review more than a quick question.

    Try: “Load the full lynx docs and summarize the setup steps.”

    Network · get_full_docs

  • Reads design tokens and component specs

    Returns the raw Rootage data that SEED builds from: an index of resources, or one resource such as /color.json or /components/action-button.json.

    Try: “Get the color tokens from Rootage.”

    Network · get_rootage

  • Lists the SEED icons

    Lists the monochrome and multicolor icons, with an optional filter by type. The icon data comes from the @karrotmarket/icon-data package that is installed with the server.

    Try: “List the multicolor SEED icons.”

    Read · list_icons

  • Finds icons by keyword

    Searches icon names and metadata for a keyword and returns the matches, so the assistant can pick a real icon instead of guessing a name.

    Try: “Find SEED icons related to arrows.”

    Read · search_icons

  • Shows how to use one icon

    Returns the details of one icon, including the import line and component for the React, Vue and Lynx icon packages.

    Try: “How do I import the arrow-left line icon in React?”

    Read · get_icon_details

Read from the source code

Permissions

low risk · 2 things to watch

Low risk

All 8 tools only read public SEED documentation and icon data, so the main cost is context size. Use the single-page tool for focused questions.

What it can do

Watch out for

  • Doc lookups call seed-design.io

    Each docs and token request goes to the public SEED site, which can see the paths you ask for. Icon tools use data bundled with the package. github.com

  • The full-docs tool returns a lot of text

    get_full_docs puts a whole section into the chat. Prefer the list and get tools for a single page to save context. github.com

Security advisories

No published security advisories as of Nov 1, 2026.

Technical details
Turning on read-onlyAll 8 tools only read, so there is nothing to switch off.
Talks toseed-design.io, for documentation and design token files
Sign-in and keysNo sign-in or key.

Questions

Is the SEED Design MCP server official?

Yes. It is published from Daangn's own seed-design repository, and the SEED docs call it the official MCP server for SEED documentation.

Does it need a Figma account or an API key?

No. The docs describe it as running on its own without Figma. It reads public pages and needs no key.

How is it different from the SEED Figma server?

This one reads documentation, tokens and icons. The separate package @seed-design/mcp in the same repo is the Figma-connected server, documented on the SEED site.

Which clients does it work with?

Any client that can run a local command. The SEED docs list install steps for Claude Code, Codex CLI, Gemini CLI, Cursor and Claude Desktop. The install box has the command.

Does it work offline?

Only partly. Icon search uses data installed with the package. Docs and token tools fetch from seed-design.io and cache results for five minutes.

Can it change anything?

No. Every tool reads documentation or icon data and nothing is written.

Is it free?

Yes. It is open source under the Apache-2.0 license.

Information

updated Nov 2, 2026

Publisher
Official
Package
@seed-design/docs-mcp
Registry
npm
Transport
stdio
Auth
None
Version
0.7.0
License
Apache-2.0
Last commit
Oct 31, 2026
Open issues
4

WebsiteGitHubnpmChangelogIssues

Sources

Docs, issue trackers and discussions this page is built from. Issues, quotes and findings above link to their own source.

Show all 3
  1. SEED Docs MCP guide · github.com
  2. docs-mcp README · github.com
  3. docs-mcp tool registrations · github.com

Facts from the official MCP registry, GitHub, npm, PyPI and the Docker catalog. Updated Nov 2, 2026.