Pudge Ui

io.github.pudge-studioPublished by GitHub account pudge-studiov0.2.0Updated Oct 24, 2026

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

VerifiedSTDIODesktop onlyKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Lets a coding assistant look up specs for 93 skeuomorphic 2000s-era UI components from the pudge-ui design system.

What you can do
Serves the pudge-ui component catalog to coding agents as read-only tools. Tools include list_components (optionally filtered by category), search_components (fuzzy search by name, description, or tags), get_component and get_components for full specs, get_foundation for core or extended foundation docs, and get_composition for a composition spec with all referenced component specs. Specs are bundled in the package, so lookups are local.
When to use it
Useful when an assistant is building or editing interfaces with the pudge-ui design system and needs accurate component names, props, and composition details instead of guessing. Also handy for browsing the catalog by category or fuzzy search before choosing components.
Requirements
Runs locally over stdio as the npm package @pudge-ui/mcp-server, typically launched with npx. No authentication, environment variables, or headers are declared, and no network access is needed since specs ship with the package. Desktop-only; not available as a web executable.
Before you install
The README states all tools are read-only and that the server never writes to the filesystem or makes network calls. The project is pre-1.0 and the component catalog grows between releases, so pin a version if you need reproducible output.

Installation

In SourceWeft

  1. Open Pudge Ui in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

@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):

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

For local development:

json
{  "mcpServers": {    "pudge-ui": {      "command": "npx",      "args": ["tsx", "src/index.ts"],      "cwd": "/path/to/pudge-ui/packages/mcp-server"    }  }}

Available Tools

ToolDescription
list_componentsList all components, optionally filtered by category
search_componentsFuzzy search components by name, description, or tags
get_foundationGet foundation spec docs (core 5 or extended 9)
get_componentGet full spec for a single component (foundation + spec)
get_componentsGet specs for multiple components (foundation included once)
get_compositionGet 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

bash
npm installnpm run dev        # run with tsxnpm run build      # compile + copy specnpm run typecheck  # type-check onlynpm 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.

Source: packages/mcp-server/README.md at commit 301bb96

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.2.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts