MCP server
The server exposes NostalgiaUI to any MCP client, so an AI coding agent can ask for the tokens and component source it needs rather than guessing.
Tools
| Tool | Answers |
|---|---|
list_eras | the eras, with period and label |
list_palettes | the palettes, with appearance and source licence |
get_tokens | CSS variables, a Tailwind preset, or DTCG JSON for one pairing |
get_component | imports, source, era CSS and the traps to avoid |
import_vscode_theme | a palette from a VS Code theme, with provenance |
check_contrast | a WCAG audit of one pairing |
Claude Code
From a clone of the repo, the included .mcp.json registers the server automatically. From anywhere else:
claude mcp add --transport stdio nostalgiaui -- node /absolute/path/to/nostalgia-ui/packages/mcp/dist/cli.jsClaude Desktop
Add the server under mcpServers in claude_desktop_config.json.
{
"mcpServers": {
"nostalgiaui": {
"command": "node",
"args": ["/absolute/path/to/nostalgia-ui/packages/mcp/dist/cli.js"]
}
}
}Try it
Ask: build me a settings page in Frutiger Aero with the Nord palette. The agent should call get_tokens and get_component, and the notes in each answer tell it the things that are easy to get wrong.