MCP.Market

Pudge UI MCP server

by pudge-studio·io.github.pudge-studio/pudge-ui·v0.2.0·11 stars
No reviews yet

Query pudge-ui — 93 skeuomorphic 2000s-era UI component specs — for coding-agent context.

A91/100grade A
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
A91/100

full report

Adoption
Growing

11 stars30 downloads/wk

Reviews

Write one

Nobody has reviewed Pudge UI yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Pudge UI tools (6)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • get_component

    Get the full spec for one pudge-ui component: its physical analog (the real 2000s hardware it imitates), mechanism, exact CSS recipe, and constraints — with the foundation prepended so the result is self-contained. This is the spec you hand to a coding agent to build the component in any stack (CSS, React Native, SwiftUI, Compose, Flutter). Accepts a component id or display name (e.g. 'push-button

  • get_components

    Get full specs for several pudge-ui components at once, with the shared foundation included a single time (deduplicated) to save context. Use when building a screen that needs multiple components — pass an array of component ids or names.

  • get_composition

    Get a pudge-ui composition — a pre-assembled multi-component layout (e.g. 'audio-mixer-strip') — with every referenced component spec inlined and the foundation included once. Use to build a complete, cohesive interface in one shot rather than wiring components together yourself.

  • get_foundation

    Get the pudge-ui foundation: the design-system rules every component depends on. Core (default) returns 5 docs — philosophy, tokens, materials, depth-model, naming. Set extended=true for all 9 (adds theme, accessibility, layout, canvas). Load this once at the start of a build so the agent applies the depth model, material recipes, and warm-neutral palette correctly.

  • list_components

    List pudge-ui components — 93 skeuomorphic UI specs across 11 categories (buttons, toggles, dials, sliders, readouts, meters, navigation, forms, overlays, indicators, data). Returns each component's id, name, category, and one-line description. Optionally filter by category id. Use this first to discover what exists, then call get_component for full specs.

  • search_components

    Fuzzy-search pudge-ui components by name, description, or tag (e.g. 'volume', 'knob', 'LCD', 'walkman'). Returns ranked matches with id, name, category, and description. Use this when you know what the user wants but not the exact component id; then call get_component with the best match.

Public scan report

scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it

no findings
  • Code scan11 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 7 days ago15/15
  • Maintainer identityregistry namespace matches repository owner7/10
Overall 91/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Pudge UI compares

Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
91/100
higher than 88% of 4,460 AI and agents servers
Tools
6
the typical AI and agents server has 6
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
11
more than 85% of 2,711 AI and agents servers
Downloads a week
30
more than 17% of 1,538 AI and agents servers with a package

What its tools let an agent do: 6 read

Install Pudge UI in Claude Code, Cursor or VS Code

Runs npx -y @pudge-ui/mcp-server on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add pudge-ui -- npx -y @pudge-ui/mcp-server
Add to Cursor

What the publisher says

From the Pudge UI repository's README, as published. We do not edit it. Read it on GitHub

A design system for 2000s-era consumer-electronics interfaces, written for coding agents.

Like what you see? ⭐ Star pudge-ui on GitHub — it helps coding agents and developers discover the project.

pudge-ui is a specification, not a component library. There's no package to install and no React components to import. Each component is a written spec — the physical part it imitates, how that part works, the exact CSS, and the rules that keep an implementation honest. You hand the spec to a coding agent, and it builds the component in whatever stack you're using: React Native, SwiftUI, Jetpack Compose, Flutter, or plain CSS.

Skeuomorphic detail doesn't fit in design tokens. --color-primary: blue can't describe the three-layer shadow of a raised rubber button or the lip shadow inside a recessed LCD. That needs prose — which is also what an LLM reads best.

Every component spec covers:

  • Physical analog — the real 2000s hardware it mimics (Sony Walkman, Nikon dials, iPod click wheel, Nokia keypads, DJ consoles)
  • Mechanism — how the part actually works (dome switches, rotary encoders, capacitive touch)
  • CSS recipe — the exact CSS that reproduces the look
  • Constraints — rules that rule out the "close but wrong" version

Use it

  1. Browse the components at ui.pudgestudio.com.
  2. Copy a component spec, or install the MCP server below.
  3. Give it to your agent (Claude, GPT, Copilot, whatever) and describe what you're building.

Quick start

With MCP (Claude Code, Cursor, etc.)

Add to your MCP config:

{
  "mcpServers": {
    "pudge-ui": {
      "command": "npx",
      "args": ["-y", "@pudge-ui/mcp-server"]
    }
  }
}

Then ask your agent: "Build a music player interface using pudge-ui components"

Manual (any LLM)

  1. Copy the foundation spec
  2. Copy the component spec(s) you need
  3. Paste into your LLM conversation
  4. Describe what you want to build

What's inside

93 components across 11 categories

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Pudge UI: common questions

Is Pudge UI MCP server safe?
Yes, by our scan: it is graded A (91/100). Read the Pudge UI safety report
How do I install Pudge UI?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Pudge UI need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Pudge UI maintained?
The last commit was 45 days ago (2026-09-20). The latest release is v0.2.0.
What can I use instead of Pudge UI?
Servers from other publishers that do the same job: Serena MCP: the IDE for your agent MCP server, Figma Context MCP server and SuperCompress MCP server.
How does Pudge UI compare with other AI and agents MCP servers?
safety score 91/100 (higher than 88% of 4,460 AI and agents servers); tools 6 (the typical AI and agents server has 6); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Pudge UI

Same job from other publishers: the closest match first, then the best rated.

  • Serena MCP: the IDE for your agent
    A powerful toolkit for coding, providing semantic retrieval and editing capabilities.
    C
  • Figma Context
    Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.
    B
  • SuperCompress
    Compress coding-agent context ~64%. Hosted Neural Keep MCP for Cursor/Claude/Codex.
    B
  • Orcareplay
    Read, replay and fork recorded coding-agent runs.
    A
  • Total Agent Memory
    Persistent local memory for coding agents: temporal knowledge graph, procedural and episodic recall
    A