Skip to main content
Glama
michaeltrilford

Muibook Guidelines MCP Server

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.

Related MCP server: WordPress Design System MCP Server

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
  4. Check for errors in the console output

  5. 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

Available Tools

1 tool
serve_guidelinesB

Access guidelines for your design system as you build to ensure consistency.

ParametersJSON Schema
NameRequiredDescriptionDefault
jsonYesAccess guidelines for your design system as you build to ensure consistency.

TDQS

B3.1/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Access' implies a read operation but the description does not explicitly state that the tool is non-mutating, what it returns, or any behavioral characteristics. This is a significant gap for a tool with no annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence with no filler, and the central purpose is front-loaded. It could pack in more behavioral or parameter detail without losing conciseness, but as written it is efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with one required parameter, no annotations, and no output schema, the description should explain what to pass in 'json' and what the tool will return. It instead focuses on design workflow, leaving an agent without enough information to construct a correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema description coverage is nominally 100%, the parameter's description is just a repetition of the tool description ('Access guidelines for your design system...') and gives no actual meaning about what the required 'json' string should contain, what format it should be in, or how it affects the operation. The description adds no clarifying value beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb, 'Access', and identifies the resource, 'guidelines for your design system', along with the purpose, 'ensure consistency'. It clearly states what the tool does, though with no sibling tools it does not need to differentiate from alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'as you build' provides a clear usage context: the tool is meant to be consulted while building to maintain design consistency. With no sibling tools and no exclusions, this context is sufficient.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool updatev1.0.0
    • First observedserve_guidelines

TDQS

B3.4/5.0

Scored across 1 tool

Disambiguation5/5

Only one tool exists, so there is no possibility of confusion or overlap. The tool's purpose is clear and unique.

Naming Consistency5/5

The single tool name follows a clean verb_noun pattern (serve_guidelines), which is consistent and easily readable.

Tool Count3/5

With only one tool, the server feels minimal but not unreasonable for a narrowly scoped guideline-serving purpose. It sits at the thin end of acceptable.

Completeness3/5

The tool provides access to guidelines, but there are no options for searching, filtering, or retrieving specific sections. This may force agents to process a large blob of content, though it could suffice for very simple use cases.

Related MCP Connectors

Related MCP Servers