Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
MCP server for timepicker-ui: options, events, themes, public API, snippets and time validation.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"timepicker-ui": {
"command": "npx",
"args": [
"-y",
"timepicker-ui-mcp"
]
}
}
}Run this in your terminal
claude mcp add timepicker-ui -- npx -y timepicker-ui-mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"timepicker-ui": {
"command": "npx",
"args": [
"-y",
"timepicker-ui-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"timepicker-ui": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"timepicker-ui-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account pglejzer, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (2.1.0) reached the registry 18 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, EmbeddedCI BenchPod
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Drive a BenchPod hardware-in-the-loop bench: power, flash, UART, I2C, CAN, analog and logic.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
A time picker for web forms. Attach it to an and users pick a time on a clock face or a scroll wheel.
Live demo · Documentation · Changelog · React wrapper
window or document on import, so it's safe in Next.js, Nuxt and other SSR setups.labels.HH:MM:SS) in the clock, wheel and compact wheelclock.isTimeDisabled)npm install timepicker-ui
<input id="timepicker" type="text" />
import { TimepickerUI } from "timepicker-ui";
import "timepicker-ui/main.css";
const input = document.querySelector("#timepicker"); const picker = new TimepickerUI(input, { clock: { type: "24h" }, ui: { theme: "dark" }, callbacks: { onConfirm: (data) => console.log("Selected:", data), }, }); picker.create();
No global CSS reset is needed: the picker sets box-sizing: border-box on its own elements (details).
picker.create(); // render the picker and attach it to the input
picker.open(); picker.close(); picker.destroy(); picker.getValue(); // { hour, minutes, seconds, type, time }, seconds only with clock.showSeconds picker.setValue("14:30"); // "2:30 PM" works too picker.setValue("14:30:15"); // with clock.showSeconds picker.setOptions({ ui: { theme: "crane" } }); picker.setRange({ from: "09:00", to: "17:00" }); // needs RangePlugin picker.getRange(); picker.setActivePart("to"); picker.refreshDisabledTime(); // after the data behind clock.isTimeDisabled changes
const off = picker.on("confirm", (data) => {}); // on() and once() return a function that removes the handler off(); picker.on("confirm", (data) => {}); picker.on("cancel", (data) => {}); picker.on("open", () => {}); picker.on("update", (data) => {}); picker.on("clear", (data) => {}); picker.on("error", (data) => {}); picker.once("confirm", handler); picker.off("confirm", handler);
TimepickerUI.getById("my-id"); TimepickerUI.getAllInstances(); TimepickerUI.isAvailable("#timepicker"); TimepickerUI.destroyAll();
Grouped by area. Pass only what you need, the rest has defaults (full list).
new TimepickerUI(input, {
clock: { type: "12h" | "24h" | "auto", // default "12h"; "auto" follows the browser locale incrementHours: 1, incrementMinutes: 1, showSeconds: false, // true adds seconds (HH:MM:SS) incrementSeconds: 1, disabledTime: { hours: [], minutes: [], seconds: [], ranges: "" }, isTimeDisabled: ({ hour, minutes, seconds }) => false, // hour is 0-23 defaultTime: "now" | { time, updateInput }, }, ui: { theme: "basic" | "dark" | "m3-green" | "crane" | "blueprint" | ..., mode: "clock" | "wheel" | "compact-wheel", // default "clock" animation: true, backdrop: true, initialView: "clock", // or "keyboard" editable: false, inline: { enabled: false, container: "#picker" | element, showButtons: false, autoUpdate: false, embedded: false }, clearButton: false, // or { clearInput: false } to keep the input value on Clear cssClass: "", }, labels: { am, pm, ok, cancel, clear, clockTitle, hour, minute, second, rangeFrom, rangeTo, timezone, ... }, behavior: { focusTrap: true, returnFocus: false, delayHandler: 0, id: "" }, callbacks: { onConfirm, onCancel, onOpen, onUpdate, onSelectHour, onSelectMinute, onSelectSecond, onSelectPeriod, onClear, onError, ... }, wheel: { placement: "auto" | "top" | "bottom", hideFooter: false, commitOnScroll: false, hideDisabled: false, ignoreOutsideClick: false }, range: { enabled: false, linked: true, minDuration, maxDuration }, timezone: { enabled: false, default, list }, });
Preview all of them: basic, crane, crane-straight, m3-green, m2, dark, glassmorphic, pastel, ai, cyberpunk, blueprint, blueprint-dark.
main.css is required and already includes basic. The rest are separate files:
import "timepicker-ui/main.css";
import "timepicker-ui/theme-dark.css";
new TimepickerUI(input, { ui: { theme: "dark" } });
Or import timepicker-ui/index.css to get all of them. Writing your own theme: styling guide.
Range, timezone and wheel ship as separate imports. Register them once before creating pickers. You need WheelPlugin for the wheel and compact-wheel modes.
import { TimepickerUI, PluginRegistry } from "timepicker-ui";
import { RangePlugin } from "timepicker-ui/plugins/range"; import { TimezonePlugin } from "timepicker-ui/plugins/timezone"; import { WheelPlugin } from "timepicker-ui/plugins/wheel";
PluginRegistry.register(RangePlugin); PluginRegistry.register(TimezonePlugin); PluginRegistry.register(WheelPlugin);
new TimepickerUI(input, { range: { enabled: true } });
From 4.5 nothing breaks. 4.6 adds ui.inline.embedded, range.linked, clock.isTimeDisabled with refreshDisabledTime(), the setRange() / getRange() / setActivePart() methods, and a remover returned by on() / once(). See the CHANGELOG.
From 4.4, 4.5 adds optional seconds (clock.showSeconds) and fixes many bugs. It also renames many options to clearer names, for example ui.initialView instead of ui.mobile, and adds setOptions() in place of update(). The old names keep working until 5.0, and the options page lists every pair. A few changes can affect an existing setup: the AM/PM part of the value is always AM / PM whatever labels.am / labels.pm say, out-of-range clock.disabledTime.ranges edges such as 25:00 are reported as errors, the old .tp-ui-ripple classes are gone, and some focus-ring and radius tokens changed. The CHANGELOG lists them under "Check before upgrading".
From 4.3 nothing breaks. 4.4 adds the blueprint and blueprint-dark themes, 16 new labels.* for screen-reader text, and Home/End/PageUp/PageDown keys. See the CHANGELOG.
From 3.x, options are now grouped (clock, ui, labels, ...), events go through picker.on(), and CSS class names changed. There's a migration guide.
From 2.x, you have to import the CSS yourself and some event names changed (legacy guide).
React:
import { useEffect, useRef } from "react";
import { TimepickerUI } from "timepicker-ui"; import "timepicker-ui/main.css";
function TimePicker() { const ref = useRef (null); useEffect(() => { if (!ref.current) return; const picker = new TimepickerUI(ref.current); picker.create(); return () => picker.destroy(); }, []); return ; }
There's also a React wrapper (docs). Vue and Angular examples are in the quick start docs.
datepicker-ui is the companion calendar from the same author. It has no dependencies, follows Material Design 3, is safe to import during server rendering and uses the same theme names, so the two pickers match. It covers single dates, ranges and multiple dates.
npm install @pglejzer/datepicker-ui
The date and time guide shows how to use both pickers in one form.
5.0.0 is planned but has no release date yet. 4.5.0 prepares for it. Planned changes:
PluginRegistry.register(...) and the exported plugin types (PluginRegistry, Plugin, PluginManager, PluginFactory, TemplateProvider, ClearHandler, CoreState, EventEmitter) will change. The built-in range, timezone and wheel plugins stay. A migration guide ships with 5.0.tp-ui- prefix, but the part after it is reworked to follow Material Design component naming. Custom CSS that targets these classes will need updating. 5.0 ships a table of old and new names.ui.mobile (now ui.initialView) and clock.smoothHourSnap (now clock.discreteHourJump). The options page lists every pair. The select:am / select:pm events go too (use select:period), and so does update() (use setOptions()).behavior.returnFocus becomes true by default: on close, focus goes back to the input, or to the data-open element that opened the picker. Set behavior.returnFocus: true now to return focus to the input.Only the beginning is shown; read the rest in the repo