thmh
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@thmhsearch for a primary button component"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Tehon-Mihon (thmh)
Story-less UI component catalog for the AI era — auto-generated from your code, served by a Vite plugin, exposed to agents via MCP
Overview
thmh reads your components directly: static analysis of their types and variant definitions generates every combination of their variants, so you never write a Story file.
It runs inside your app's own Vite dev server — one line in vite.config.ts — and inherits the aliases, Tailwind setup, and environment variables you already have, so there is no second build config to keep in sync.
Everything it knows is written to catalog.json, the single source of truth from which the human-facing UI, the agent-facing MCP server, and CI checks are all derived.
That MCP server exposes tools such as search_components and get_component_detail, letting coding agents find and reuse the components you already have instead of inventing near-duplicates.
The catalog UI is served at /__thmh/; repositories with no host app, such as standalone design systems, can use the thmh CLI instead.
Related MCP server: bunge-ds-mcp
The name
Tehon-Mihon is two Japanese words that both end in 本 (hon) — a book, and the original a thing is copied from.
手本 (てほん, [tehoɴ]) is a model to copy: the sheet of calligraphy a student sets beside their own paper and reproduces stroke for stroke. This is what an agent needs — the exact shape of a component, its props and its variants, ready to be followed.
見本 (みほん, [mihoɴ]) is a sample to look at: the swatch, the specimen, the one you examine before you choose. This is what a person needs — the component rendered, every variant on screen.
From one manifest, two books are born at once.
Getting Started (Prototype)
This section walks through the current prototype. The thmh CLI only implements build; dev, init, and mcp print a "not implemented" message for now.
Prerequisites: Node.js 24+ and pnpm 11 (see packageManager in package.json).
git clone <this repo> && cd thmh
pnpm install
pnpm build
pnpm dev:exampledev:example builds every package, then starts the Vite dev server for examples/react-app. Open:
http://localhost:5173/— the example app itselfhttp://localhost:5173/__thmh/— the catalog, with every variant of the exampleButtonrenderedhttp://localhost:5173/__thmh/api/catalog.json— the same data as a manifest
Edit examples/react-app/src/components/ui/button.tsx and save — the catalog re-analyzes and refreshes within a couple of seconds, no restart needed.
To generate a manifest without a dev server, run the CLI against a built app:
node packages/thmh/dist/cli.js build --root examples/react-app --out catalog.jsonTo run the test suite:
pnpm testThis server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/haribote/thmh'
If you have feedback or need assistance with the MCP directory API, please join our Discord server