Muibook Guidelines Mcp — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited Muibook Guidelines Mcp (MCP Server) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
An MCP (Model Context Protocol) server that provides design system guidelines and component documentation to Cursor Desktop.
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.
git clone https://github.com/your-org/muibook-guidelines-mcp.git
cd muibook-guidelines-mcpnpm installEdit your Cursor Desktop config file:
~/Library/Application Support/Cursor/mcp_config.json%APPDATA%\Cursor\mcp_config.jsonAdd 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.
Completely quit and reopen Cursor Desktop to load the MCP server.
Once installed, you can ask Cursor about design guidelines:
Examples:
`serve_guidelines` - Returns comprehensive design system guidelines including component anatomy, usage patterns, accessibility requirements, and visual references.
Full documentation: https://guides.muibook.com/button
The server isn't connecting. Try these steps:
node --version (needs v16+) cd /path/to/muibook-guidelines-mcp
node server.jsnode server.jsserver.js to modify guidelinesEdit 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`,
},
},
],
};
}muibook-guidelines-mcp/
├── server.js # MCP server implementation
├── package.json # Dependencies and metadata
└── README.md # This fileWe welcome contributions! To add or improve guidelines:
git checkout -b feature/new-component)server.js[Your License Here]
For issues or questions:
major.minor.patchpackage.json and server.json versions synchronized.Patch:
npm version patchMinor:
npm version minorMajor:
npm version majorThis updates package.json version and creates a Git tag automatically.
Option A – Direct publish (NPM will prompt for credentials if needed):
npm publish --access publicOption B – Pre-login (recommended for repeated releases):
npm login
npm publish --access public"mcpName": "io.github.YOURUSERNAME/muibook-guidelines-mcp"⸻
Ensure server.json matches the current version:
"version": "1.0.0"Publish to MCP Registry:
mcp-publisher publish⸻
Tag the release:
git tag v1.0.0
git push origin v1.0.0Add release notes in GitHub for tracking changes.
⸻
Install dependencies:
npm installRun locally:
npm startConnect via MCP client (Cursor, Cline, etc.) or mcp.json:
{
"servers": {
"muibook-guidelines-mcp": {
"command": "node",
"args": ["./node_modules/muibook-guidelines-mcp/server.js"]
}
}
}• 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
• NPM Publishing Docs • MCP Registry Docs • Semantic Versioning
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.