MCP server for timepicker-ui: options, events, themes, public API, snippets and time validation.
io.github.pglejzer/timepicker-ui-mcp MCP Server
This MCP server provides access to timepicker-ui capabilities, specifically covering options, events, themes, public API, snippets, and time validation. It is identified by the slug io-github-pglejzer-timepicker-ui-mcp and described as an MCP server focused on timepicker UI behavior and related resources.
🛠️ Key Features
Options
Events
Themes
Public API
Snippets
Time validation
🚀 Use Cases
Retrieve or inspect timepicker UI configuration options
Access event-related information for timepicker interactions
Review theme details used by timepicker-ui
Use the public API and snippets
Validate time inputs based on server-provided rules
⚡ Developer Benefits
Centralized programmatic access to timepicker-ui components (options, events, themes)
Reusable references for the public API and snippets
Support for time validation workflows
⚠️ Limitations
Server description does not specify available tools, endpoints, or counts beyond the listed areas.
~29 KB gzipped core. The range plugin is about 7 KB, the timezone plugin about 3 KB, the wheel plugin about 10 KB, and a plugin only gets bundled if you import it (bundle stats).
Clock, wheel or compact wheel (a small dropdown under the input).
Plain JS API, so it works the same in React, Vue, Angular, Svelte or without a framework.
Doesn't touch window or document on import, so it's safe in Next.js, Nuxt and other SSR setups.
Keyboard and screen reader support. All texts, the screen-reader ones included, can be translated via labels.
Or import timepicker-ui/index.css to get all of them. Writing your own theme: styling guide.
Plugins
Range, timezone and wheel ship as separate imports. Register them once before creating pickers. You need WheelPlugin for the wheel and compact-wheel modes.
Registration is global. Call PluginRegistry.register() once, before you create pickers. Every picker created afterwards gets a small manager for each registered plugin.
A plugin does nothing unless the picker turns it on: range.enabled, timezone.enabled, or ui.mode set to 'wheel' or 'compact-wheel'.
A plugin registered after a picker was created is not available to that picker. Create the picker again.
Turning a feature on without its plugin registered emits error.
Without a bundler, load the core UMD build and the plugin UMD builds you need. The core build exposes TimepickerUI.PluginRegistry.
The plugin globals are TimepickerUIRange.RangePlugin, TimepickerUITimezone.TimezonePlugin and TimepickerUIWheel.WheelPlugin.
Upgrading
From 4.6, 4.7 adds the range plugin in wheel and compact-wheel, setView() / getView(), clear(), getActivePart(), setRangeCaptions() and the range:change event. Some defaults changed: AM/PM is a radiogroup, the timezone combobox moved to .tp-ui-timezone-selected, aria-valuetext reads "7 of 12", and dark follows Material Design 3 tokens. The CHANGELOG lists them under "Check before upgrading".
From 4.5 to 4.6 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).
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.
5.0.0 is planned but has no release date yet. 4.5.0 prepares for it. Planned changes:
Plugins will be built and registered differently. 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.
CSS class names keep the 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.
The options renamed in 4.5.0 lose their old names, for example 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.
Code that is no longer needed is removed, including backward-compatibility paths for the deprecated items and dead code. This reduces bundle size and load cost for the core and each plugin. No size target is set yet. 4.5.0 already removes internal dead code that has no effect on the public API or markup. 5.0 removes the rest together with the items below.
Items deprecated in 4.5.0 are removed:
OptionTypes (use TimepickerOptions)
clock.currentTime.locales
getValue().degreesHours and getValue().degreesMinutes
the legacy focusInputAfterCloseModal option (use behavior.returnFocus)
the hide event and HideEventData (never emitted)
the range:get-disabled-time and range:update-disabled events (never emitted)
ErrorEventData.rejectedHour and rejectedMinute (always undefined)
Also removed, because they do nothing or mislead:
internal events in the public TimepickerEventMap (range:minute:commit, animation:*) and its catch-all index signature, so on('typo') becomes a type error
behavior.delayHandler (it only delays closing and never debounced buttons)
TimepickerUI.isAvailable() (same as document.querySelector(...) !== null)
the undocumented DOM getters hour, minutes, okButton, cancelButton, clockHand
the callback arguments of open(cb) and destroy() in both forms, destroy(cb) and destroy({ callback }) (use once('open') or run the code after the call)
RangeManager, TimezoneManager and WheelManager exported from the plugin entry points (you can't get an instance today, and the new plugin API replaces them)
Changed events and options:
select:hour, select:minute and select:second fire once when a value of their unit is picked, in every mode. Today, in clock mode, they fire when a field is activated, so picking an hour fires select:minute. To follow face changes, use switch:face, which 4.5.0 already emits
ui.footer replaces ui.inline.showButtons and wheel.hideFooter: false hides OK, Cancel and Clear in every mode, and true shows them in inline mode too
behavior.commitOnChange replaces ui.inline.autoUpdate and wheel.commitOnScroll: each picked value is written to the input and emits confirm, and the picker stays open
wheel.ignoreOutsideClick moves to behavior.ignoreOutsideClick and works in every mode, the clock modal included
the minute announcement reads labels.minute; labels.announceMinute is removed (its default is already Minute since 4.7.0)
ui.cssClass is applied to one element instead of two
Package and CSS:
about 50 CSS custom properties that no rule reads are removed, for example --tp-tertiary-container, --tp-on-tertiary-container, --tp-radius, --tp-hover-bg and 18 of the 34 --tp-size-* tokens. 5.0 lists them all
the ./plugins/* wildcard in package.jsonexports is removed, while ./plugins/range, ./plugins/timezone and ./plugins/wheel stay
crane-straight becomes a variant of crane with square corners (option name not decided)
ui.keyboardIcon / ui.clockIcon take an element or a factory function instead of an HTML string