Allows coding agents to programmatically query specifications for 93 skeuomorphic 2000s-era UI components.
Also known as pudge-studio/pudge-ui, @pudge-ui/mcp-server
- Stars
- 11
- Tools
- 6
- Downloads, 30 days
- —
- Latest version
- 0.2.0
- Last commit
- Sep 20, 2026
- License
- MIT
What is pudge-ui MCP?
pudge-ui allows coding agents to programmatically query specifications for 93 skeuomorphic 2000s-era UI components. It exposes 6 tools, such as list_components, search_components, get_foundation.
Summary generated from the project's README
About pudge-ui MCP server
Coding agents can programmatically access detailed specifications for 93 skeuomorphic 2000s-era UI components through this interface. It provides a way for AI clients like Claude Desktop or Claude Code to retrieve design data without making external network calls, as all specifications are bundled directly within the package.
Developers use the server to browse the component catalog or find specific items using fuzzy search. The available tools include list_components for category filtering, search_components for name or tag queries, and get_foundation to access core or extended design docs. For more complex needs, get_component retrieves individual specs, get_components handles multiple items at once, and get_composition provides full specifications for complex layouts including all referenced parts. Because the tools are read-only, they do not modify your local filesystem.
What you can do with it
- 1Browse specific UI categoriesAsk the agent to find all available components within a specific design category like buttons.
- 2Locate components via fuzzy searchRequest the agent to find components related to audio controls using keywords.
- 3Retrieve detailed component specificationsHave the agent pull the full foundation and specification data for a single UI element.
- 4Analyze complex UI compositionsInstruct the agent to fetch a composition spec that includes all its referenced component details.
Written from the project's README. Every use case is checked against a quote from it.
How to install pudge-ui MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall pudge-ui MCP in Claude Code
$ claude mcp add pudge-ui -- npx -y @pudge-ui/mcp-serverInstall pudge-ui MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"pudge-ui": {
"command": "npx",
"args": [
"-y",
"@pudge-ui/mcp-server"
]
}
}
}Install pudge-ui MCP in VS Code
.vscode/mcp.json
{
"servers": {
"pudge-ui": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@pudge-ui/mcp-server"
]
}
}
}Install pudge-ui MCP in VS Code CLI
$ code --add-mcp '{"name":"pudge-ui","type":"stdio","command":"npx","args":["-y","@pudge-ui/mcp-server"]}'Install pudge-ui MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"pudge-ui": {
"command": "npx",
"args": [
"-y",
"@pudge-ui/mcp-server"
]
}
}
}Install pudge-ui MCP in Codex
$ codex mcp add pudge-ui -- npx -y @pudge-ui/mcp-serverInstall pudge-ui MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.pudge-ui] command = "npx" args = ["-y", "@pudge-ui/mcp-server"]
Install pudge-ui MCP in Gemini CLI
$ gemini mcp add -s user pudge-ui npx -- -y @pudge-ui/mcp-serverInstall pudge-ui MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"pudge-ui": {
"command": "npx",
"args": [
"-y",
"@pudge-ui/mcp-server"
]
}
}
}pudge-ui MCP tools 6
Detected from the READMElist_componentssearch_componentsget_foundationget_componentget_componentsget_composition
Automated checks
Ran Nov 14, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachablepudge-studio/pudge-ui is public and reachablegithub.com/pudge-studio/pudge-ui ↗Pass
- Package names this repository as its source@pudge-ui/mcp-server names pudge-studio/pudge-ui as sourcenpmjs.com/package/@pudge-ui/mcp-server ↗Pass
- Build provenance (Sigstore attestation)No build attestation published for this releaseNot checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-09-20github.com/pudge-studio/pudge-ui ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from @pudge-ui/mcp-serverPass
- No critical advisory in the package or its dependencies101 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model6 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNo tool named like delete, drop or execPass
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHub@pudge-ui/mcp-server
MCP server for the pudge-ui design system. Lets coding agents query component specs programmatically.
Installation
Add to your MCP client config (e.g. Claude Desktop, Claude Code):
{
"mcpServers": {
"pudge-ui": {
"command": "npx",
"args": ["-y", "@pudge-ui/mcp-server"]
}
}
}
For local development:
{
"mcpServers": {
"pudge-ui": {
"command": "npx",
"args": ["tsx", "src/index.ts"],
"cwd": "/path/to/pudge-ui/packages/mcp-server"
}
}
}
Available Tools
| Tool | Description |
|---|---|
list_components |
List all components, optionally filtered by category |
search_components |
Fuzzy search components by name, description, or tags |
get_foundation |
Get foundation spec docs (core 5 or extended 9) |
get_component |
Get full spec for a single component (foundation + spec) |
get_components |
Get specs for multiple components (foundation included once) |
get_composition |
Get a composition spec with all referenced component specs |
Examples
list_components({ category: "buttons" })
search_components({ query: "volume slider audio" })
get_component({ name: "push-button" })
get_components({ names: ["rotary-encoder", "vu-meter", "vertical-fader"] })
get_composition({ name: "audio-mixer-strip" })
get_foundation({ extended: true })
All tools are read-only (annotated with readOnlyHint) — the server never writes to your filesystem or makes network calls. Specs are bundled in the package.
Development
npm install
npm run dev # run with tsx
npm run build # compile + copy spec
npm run typecheck # type-check only
npm test # run the test suite
Versioning & stability
This server tracks pudge-ui's versioning and is pre-1.0. The component catalog grows between releases, but tool names and input shapes are stable — any change to a tool signature will come with a minor/major version bump and a CHANGELOG entry. Pin a version if you need byte-for-byte reproducibility.
pudge-ui MCP questions
How do I add pudge-ui MCP to Claude Code?
Run claude mcp add pudge-ui -- npx -y @pudge-ui/mcp-server in your terminal. Add --scope user to make it available in every project.
How do I add pudge-ui MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does pudge-ui MCP provide?
It exposes 6 tools, including list_components, search_components, get_foundation, get_component, get_components.
Does this server write to my files or access the internet?
No, all tools are read-only and the server does not write to your filesystem or make network calls.
Where are the component specifications stored?
The component specifications are bundled directly within the package.
How stable are the tool signatures?
Tool names and input shapes are stable, though the component catalog grows between releases.