PluginBench
MCP Server
Active
MIT

io.github.pudge-studio/pudge-ui MCP Server

io.github.pudge-studio/pudge-ui

93 skeuomorphic 2000s UI component specs for coding agents—nostalgic interfaces built on physical design principles.

RepositoryRegistry
How to choose

What this kind of tool is for

  • Scaffold, lint, or restyle a component your agent is already editing.
  • Run accessibility, link, or screenshot checks against a local build.
  • Turn a design constraint into generated markup the agent can iterate on.

How to compare servers like this

Framework fit:
Check the tool targets your stack (React, Vue, plain HTML) before installing it.
Runtime needs:
Some browser-driving tools need a local browser or display; read the setup notes first.
Maintenance signal:
Frontend tooling churns quickly; recent commits are a good filter.
Output quality:
Prefer tools whose generated code you would accept into the repo as-is.

This page carries your copy-paste config: pick your MCP client in the install section on this page and use the copy button.

What is the io.github.pudge-studio/pudge-ui MCP server?

The pudge-ui MCP server provides access to 93 detailed component specifications for 2000s-era skeuomorphic user interfaces, inspired by hardware like iPods, Nokias, and DJ consoles. Each spec includes physical analogs, mechanisms, CSS recipes, and constraints to guide AI agents in building authentic retro interfaces. It's designed to give coding agents the prose-based context they need to implement components across any tech stack.

pudge-ui is a design system specification for nostalgic, skeuomorphic interfaces that mimic 2000s consumer electronics. Rather than a component library, it provides detailed written specs covering the physical hardware inspiration, exact CSS implementations, and design rules for 93 components across 11 categories (buttons, toggles, dials, sliders, readouts, meters, navigation, forms, overlays, indicators, and data displays). Use it by querying the MCP server or copying specs directly into your LLM conversation to build retro-styled interfaces in React, SwiftUI, Flutter, or plain CSS.

How to install io.github.pudge-studio/pudge-ui

Copy-paste configuration for popular MCP clients.

transport: stdio
Config generated by PluginBench — verify against the source before use.
~/Library/Application Support/Claude/claude_desktop_config.json
JSON config
{
  "mcpServers": {
    "pudge-ui": {
      "command": "npx",
      "args": [
        "-y",
        "@pudge-ui/mcp-server"
      ]
    }
  }
}

Tools & capabilities

Tools this server exposes to the agent.

  • Query component specs — Access detailed specifications for any of the 93 skeuomorphic UI components across 11 categories (buttons, toggles, dials, sliders, readouts, meters, navigation, forms, overlays, indicators, data).
  • Browse material surfaces — Reference the 6 physically-accurate material recipes: brushed metal, chrome, rubber, glossy polycarbonate, glass, and phosphor screen.
  • Access foundation specs — Query design tokens, materials, depth model, naming conventions, and other foundational design system documentation.

Use cases

  • Build a retro music player interface with iPod-inspired dials and transport controls
  • Create a nostalgic camera interface with LCD readouts and physical button specs
  • Design a DJ console-style mixer with faders, crossfaders, and VU meters
  • Implement a Nokia-style mobile menu with D-pad navigation and keypad buttons
  • Develop a Gameboy-inspired game UI with rubber buttons and dot-matrix displays

io.github.pudge-studio/pudge-ui MCP server FAQ

What is pudge-ui?

pudge-ui is a specification-based design system for 2000s-era skeuomorphic interfaces. It provides 93 detailed component specs (not code) that describe physical analogs, mechanisms, CSS recipes, and design rules. You hand the specs to a coding agent or LLM, and it builds the components in your chosen stack.

Is pudge-ui free?

Yes. The code and component specs are MIT licensed. The pudge-ui name, Pudge mascot, and logo are trademarks of Pudge Studio and not covered by the MIT license.

How do I use it with Claude or Cursor?

Add the MCP server to your config with `npx @pudge-ui/mcp-server`, then ask your agent to build interfaces using pudge-ui components. Alternatively, copy specs manually from ui.pudgestudio.com and paste them into any LLM conversation.

What components are included?

93 components across 11 categories: buttons (push, gel, rubber, keypad, etc.), toggles, dials, sliders, readouts, meters, navigation, forms, overlays, indicators, and data displays. Each is inspired by real 2000s hardware like iPods, Nokias, Nikon cameras, and DJ consoles.

Can I use pudge-ui in any tech stack?

Yes. pudge-ui is stack-agnostic. Specs work with React, React Native, SwiftUI, Jetpack Compose, Flutter, plain CSS, or any other framework. The specs provide CSS recipes and design rules; you implement them in your chosen language.

Do I need to install a package?

No package installation required. pudge-ui is a specification, not a component library. Either use the MCP server for agent integration or copy specs directly from ui.pudgestudio.com into your LLM conversation.

README (reference)

Source of truth, from the repository.

<img src="./docs/public/og-image.jpg" /> <p align="center"> <a href="https://github.com/pudge-studio/pudge-ui/stargazers"><img src="https://img.shields.io/github/stars/pudge-studio/pudge-ui?style=flat&logo=github&label=Star&color=f5a623" alt="Star pudge-ui on GitHub"></a> <a href="https://www.npmjs.com/package/@pudge-ui/mcp-server"><img src="https://img.shields.io/npm/v/@pudge-ui/mcp-server?style=flat&logo=npm&logoColor=white&label=npm&color=cb3837" alt="npm version"></a> <a href="https://www.npmjs.com/package/@pudge-ui/mcp-server"><img src="https://img.shields.io/npm/dm/@pudge-ui/mcp-server?style=flat&logo=npm&logoColor=white&label=downloads&color=cb3837" alt="npm downloads"></a> <a href="LICENSE"><img src="https://img.shields.io/badge/license-MIT-blue?style=flat" alt="MIT License"></a> <a href="https://ui.pudgestudio.com"><img src="https://img.shields.io/badge/docs-ui.pudgestudio.com-f5a623?style=flat" alt="Documentation"></a> </p>

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

CategoryComponentsInspired by
ButtonsPush, gel, rubber, clear, keypad, REC, function grid, icon, segmentedSony Alpha, iPod, Nokia, Gameboy
TogglesToggle, slide, rocker, power, DIP switch, LED checkbox, radioCamera switches, phone silent switch
DialsRotary encoder, mode dial, radial knob, cylindrical scroll, click wheelNikon mode dial, DJ knobs, iPod wheel
SlidersVolume, scrubber, fader, dual range, crossfader, stepper, vertical faderMixing console, DJ crossfader
ReadoutsSignal display, camera readout, LCD, timecode, 7-segment, dot matrixCamera viewfinder, alarm clock, LED ticker
MetersSpectrum, VU, EQ, histogram, waveform, gauges, oscilloscopeAudio equipment, camera histogram
NavigationMenu grid, list, tab bar, D-pad, rack panel, breadcrumbs, paginationNokia menu, iPod list, Gameboy D-pad
FormsText input, textarea, search, select, color picker, file inputEquipment LCD entry, TV color bars
OverlaysPanel, bezel, dialog, toast, focus brackets, grid overlay, tooltipRack-mount panels, camera AF
IndicatorsChips, badges, LEDs, spinners, skeleton, accordion, transport controlsPanel LEDs, iPod transport
DataData table, media grid, film stripDiagnostic readouts, contact sheets

6 material surfaces

Every component uses one of six physically-accurate material recipes:

  1. Brushed Metal — iPod back plate, anodized aluminum
  2. Chrome — Nikon dial rings, polished trim
  3. Rubber — Gameboy buttons, soft-touch matte
  4. Glossy Polycarbonate — iPod Nano case, gel buttons
  5. Glass — iMac G3 clear shell, frosted plastic
  6. Phosphor Screen — Camera viewfinder, VU meter display

Project structure

spec/
  foundation/     design tokens, materials, depth model, naming
  components/     individual component specs
  compositions/   multi-component assembly specs
  guides/         extension guide, LLM usage guide, prompt templates
packages/
  mcp-server/     MCP server for agent integration
docs/             documentation site (ui.pudgestudio.com)

Philosophy

  1. Physical analog commitment — every CSS property maps to a real material or manufacturing process
  2. Warm neutral palette — warm grays (#1c1a18 not #1c1c1c) under tungsten workbench lighting
  3. Three-plane depth model — every raised element uses a 3-layer shadow stack
  4. Material honesty — rubber looks different from chrome looks different from glass

Contributing

See CONTRIBUTING.md for guidelines.

License & brand

Code and component specs are MIT. The pudge-ui name, the Pudge capybara mascot, and the logo are trademarks of Pudge Studio and are not covered by the MIT license — please don't use them to imply endorsement or for a fork's branding.

License

MIT

Related MCP servers

Ideogram V3 API — generate, edit, remix, reframe, replace background, upscale images

0
TypeScript
MIT
View repository →

Measures your site in a real browser and returns verifiable observations, with evidence and limits.

Basque Country hyperlocal mobility: ES/EU semantic search, routing, open-data POIs, peak-bagging.

0
Python
Apache-2.0
View repository →

Web toolkit for AI agents: read any URL as Markdown, screenshot, extract data, or crawl a site.

View repository →

Your architecture in your agents' context: checks, specs, ADRs and docs over MCP, at write time.

View repository →

Your runbooks as agent tools: scripts from runbooks.json served as typed, allowlisted MCP tools.

View repository →