Featured

Deploy OpenClaw in 60 seconds — 20% off logoDeploy OpenClaw in 60 seconds — 20% off

Launch OpenClaw on Hostinger in about 60 seconds and keep your agent live 24/7. Our referral link gives you 20% off, no coupon code needed.

Launch on Hostinger
Run your Hermes agent on Hostinger, fully managed logoRun your Hermes agent on Hostinger, fully managed

Launch Hermes on Hostinger in one click, fully managed, no VPS knowledge needed. Use code ZACAARON10 for 10% off.

Launch on Hostinger
Crawl and scrape any site into clean data, 10% off logoCrawl and scrape any site into clean data, 10% off

Firecrawl crawls and scrapes any site into clean markdown for your agent. Get 1,000 free credits, and new users get 10% off their first purchase.

Try Firecrawl free
Your own AI agent, running 24/7 with QwikClaw logoYour own AI agent, running 24/7 with QwikClaw

QwikClaw sets up and runs an always-on OpenClaw agent for you. One click, no config files, no server setup.

Deploy now
One API to scrape, enrich, and extract the internet. logoOne API to scrape, enrich, and extract the internet.

Context.dev gives your agents a single API to scrape, enrich, and extract live web data — no proxies, no parsers, no maintenance.

Start building free
SetupClaw: done-for-you OpenClaw for founders & exec teams logoSetupClaw: done-for-you OpenClaw for founders & exec teams

White-glove OpenClaw for founders and exec teams (4–50+ employees): we install, harden, integrate your tools, and maintain it — secured from day one.

Get it set up for you
SEO data APIs for your agent, $1 free credit logoSEO data APIs for your agent, $1 free credit

DataForSEO gives your agent live access to SERP results, keyword data, backlinks, and on-page SEO data through one API. New accounts get a $1 credit, good for up to 20,000 keyword or backlink lookups.

Try DataForSEO free
Reach 47,000+ AI builders

A flat monthly placement in front of developers actively installing AI tools. No lock-in, cancel anytime.

Advertise here

Works with

Claude CodeClaude DesktopCursorVS CodeClineCodex CLIOpenClaw+ any MCP client

Install to Claude Code

This server doesn't publish a one-line install command. Follow the setup in the source repository.

Summary

Provides design system guidelines and component documentation to Cursor Desktop, enabling accurate advice on UI components, patterns, and best practices.

README.md

Muibook Guidelines MCP Server

An MCP (Model Context Protocol) server that provides design system guidelines and component documentation to Cursor Desktop.

Overview

This MCP server delivers comprehensive design system guidelines directly to Cursor, enabling it to provide accurate, consistent advice about UI components, patterns, and best practices from your design system.

Features

  • Component Guidelines: Detailed documentation for UI components (buttons, forms, navigation, etc.)
  • Visual References: Direct links to component anatomy diagrams and examples
  • Accessibility Standards: Built-in accessibility requirements and best practices
  • Design Tokens: Access to color, typography, spacing, and other design tokens
  • Usage Patterns: Real-world examples and usage guidelines

Installation

Prerequisites

  • Node.js (v16 or higher)
  • Cursor Desktop application

Setup

  1. Clone this repository
git clone https://github.com/your-org/muibook-guidelines-mcp.git
cd muibook-guidelines-mcp
  1. Install dependencies
npm install
  1. Configure Cursor Desktop

Edit your Cursor Desktop config file:

  • macOS: ~/Library/Application Support/Cursor/mcp_config.json
  • Windows: %APPDATA%\Cursor\mcp_config.json

Add this server:

{
  "mcpServers": {
    "muibook-guidelines": {
      "command": "node",
      "args": ["/absolute/path/to/muibook-guidelines-mcp/server.js"]
    }
  }
}

Replace /absolute/path/to/muibook-guidelines-mcp/ with the actual path where you cloned this repository.

  1. Restart Cursor Desktop

Completely quit and reopen Cursor Desktop to load the MCP server.

Usage

Once installed, you can ask Cursor about design guidelines:

Examples:

  • "Show me the button component guidelines"
  • "What are the accessibility requirements for buttons?"
  • "What button variants are available?"
  • "How should I use primary vs secondary buttons?"

Available Prompts

serve_guidelines - Returns comprehensive design system guidelines including component anatomy, usage patterns, accessibility requirements, and visual references.

What's Included

Button Component Guidelines

  • Complete anatomy breakdown with visual diagrams
  • Usage guidelines and best practices
  • Five button variants (Primary, Secondary, Tertiary, Link, Icon)
  • Accessibility requirements
  • Component states and behaviors

Full documentation: https://guides.muibook.com/button

Troubleshooting

Red indicator in Cursor Desktop

The server isn't connecting. Try these steps:

  1. Verify the path in your config file is correct and absolute
  2. Check Node.js version: Run node --version (needs v16+)
  3. Test the server manually:
   cd /path/to/muibook-guidelines-mcp
   node server.js
  1. Check for errors in the console output
  2. Restart Cursor completely (quit and reopen)

Guidelines not appearing

  • Confirm the server shows as connected in Cursor (not red)
  • Try asking explicitly: "Show me the serve_guidelines prompt"
  • Check Cursor's MCP logs for errors

Images not loading

  • Ensure you have internet connectivity (images are hosted externally)
  • Check that the URLs in the guidelines are accessible
  • Try fetching an image URL directly in your browser

Development

Running the server locally

node server.js

Making changes

  1. Edit server.js to modify guidelines
  2. Restart Cursor Desktop to reload changes
  3. Test your prompts

Adding new components

Edit the prompt content in server.js:

if (request.params.name === "serve_guidelines") {
  return {
    messages: [
      {
        role: "user",
        content: {
          type: "text",
          text: `# Add your new component guidelines here`,
        },
      },
    ],
  };
}

Project Structure

muibook-guidelines-mcp/
├── server.js            # MCP server implementation
├── package.json         # Dependencies and metadata
└── README.md           # This file

Resources

Contributing

We welcome contributions! To add or improve guidelines:

  1. Fork this repository
  2. Create a feature branch (git checkout -b feature/new-component)
  3. Add or update component guidelines in server.js
  4. Test with Cursor Desktop
  5. Submit a pull request

License

[Your License Here]

Support

For issues or questions:

  • Open an issue on GitHub
  • Check the troubleshooting section above
  • Contact the design system team

---

NPM Package

Versioning

  • Follow semantic versioning: major.minor.patch
  • Patch: bug fixes, no API changes
  • Minor: new features, backward-compatible
  • Major: breaking changes, API changes
  • Keep package.json and server.json versions synchronized.

Bumping Versions

Patch:

npm version patch

Minor:

npm version minor

Major:

npm version major

This updates package.json version and creates a Git tag automatically.

Publishing to NPM

Option A – Direct publish (NPM will prompt for credentials if needed):

npm publish --access public

Option B – Pre-login (recommended for repeated releases):

npm login
npm publish --access public
  • --access public ensures the package is publicly available.
  • Make sure package.json includes the MCP identifier:
"mcpName": "io.github.YOURUSERNAME/muibook-guidelines-mcp"

Optional MCP Registry Update

Ensure server.json matches the current version:

"version": "1.0.0"

Publish to MCP Registry:

mcp-publisher publish

GitHub Release (Optional)

Tag the release:

git tag v1.0.0
git push origin v1.0.0

Add release notes in GitHub for tracking changes.

Local Development & Testing

Install dependencies:

npm install

Run locally:

npm start

Connect via MCP client (Cursor, Cline, etc.) or mcp.json:

{
  "servers": {
    "muibook-guidelines-mcp": {
      "command": "node",
      "args": ["./node_modules/muibook-guidelines-mcp/server.js"]
    }
  }
}

Release Checklist

• Test MCP server locally • Update package.json and server.json versions • Bump version (patch, minor, or major) • Commit and push changes • Publish to NPM (--access public) • Optionally publish to MCP Registry (mcp-publisher publish) • Optionally create GitHub release with notes

References

• NPM Publishing Docs • MCP Registry Docs • Semantic Versioning

See related servers & alternatives →

Related MCP servers

Browse all →

Related guides

Hand-picked reading to help you choose and use Files & Docs servers.