coss-ui-mcp — an MCP server for coss ui docs

[Zoot01]

coss-ui-mcp — an MCP server for coss ui docs

I built a small MCP server that exposes coss ui's docs (components, hooks, install commands, props, and design tokens) to coding agents like Claude Code, Cursor, and Copilot as tools, instead of pasting the whole design system into a prompt.

Repo: https://github.com/Zoot01/coss-ui-mcp

What it does:

• coss_plan — describe a screen/feature, get back a ranked component shortlist + install commands
• coss_search — find a component/hook by name or use case
• coss_get_component — full docs for one component: install (CLI + npm deps + CSS tokens), props/API, examples
• coss_get_doc / coss_theme — overview guides and the design-token/font system for rebranding
• coss_list_components — cheap catalog listing

How it's built:

• Zero dependencies, pure Node (node:* built-ins only, also runs on Bun/Deno) — implements the MCP stdio transport directly
• npm run sync re-snapshots the live docs from coss.com/ui/llms.txt into a local ./data folder, so it also works offline
• The snapshotted doc content is from apps/ui/, which LICENSING.md carves out as MIT, so this repo is MIT too

Getting started:

git clone https://github.com/Zoot01/coss-ui-mcp.git
cd coss-ui-mcp
npm run sync   # optional — a docs snapshot ships in the repo, this just refreshes it

Then point your MCP client at server.mjs (stdio), e.g. for Claude Code, add to .mcp.json:

{
  "mcpServers": {
    "coss-ui": { "command": "node", "args": ["/ABS/PATH/coss-ui-mcp/server.mjs"] }
  }
}

Cursor, VS Code (Copilot), and Claude Desktop configs are in the README. Restart the client and prompt normally — the agent calls the coss_* tools as needed.

Note: this was mostly built with an AI coding agent (Claude Code) — I'm still actively improving it, so treat it as early/rough. Happy to take feedback/PRs if this is useful to others working with coss ui in agentic coding tools.