In Claude, open Settings → Connectors → Add custom connector, then paste the endpoint.
Open Claude ↗Give your AI the vocabulary to build the right interface.
Connect once. Your AI can search 559 product and UI guides, compare easily confused patterns, and turn rough intent into a buildable brief.
Public · read-only · no account requiredhttps://howtovibeui.com/mcp Add a remote Streamable HTTP server and use the same endpoint. No API key or OAuth step is required.
streamable-httpFrom vague idea to clear decision.
Describe the job
Use your own words. The AI searches names, aliases, examples, and use guidance across ten languages.
Resolve the pattern
It compares plausible terms by behavior and evidence boundary instead of choosing by appearance alone.
Build with context
It produces acceptance criteria, then inspects your real project before recommending implementation.
Small surface. Clear jobs.
Every tool is marked read-only, non-destructive, idempotent, and closed-world so AI clients can make safer approval decisions.
search_ui_vocabularyFind precise terms from the user's own words
READ ONLYget_ui_termRead complete guidance and evidence boundaries
READ ONLYcompare_ui_patternsCompare easily confused patterns in context
READ ONLYbuild_ui_briefCreate an implementation-neutral build brief
READ ONLYUse Vibulary without changing how you talk.
- “
I need the panel that slides in from the side so an admin can edit invoice details without losing the table.
- “
Compare a modal dialog, drawer, and bottom sheet for reviewing a destructive action on mobile.
- “
Turn this rough onboarding idea into acceptance criteria, including keyboard, loading, error, and reduced-motion behavior.
Tell your AI when to reach for Vibulary.
The MCP server already sends these instructions during connection. Paste the prompt below into project instructions when you want the same behavior to be explicit in every task.
Use Vibulary whenever a product, UI, design, motion, AI, testing, delivery, or macOS idea is described imprecisely. Search Vibulary first, compare plausible patterns, respect each term’s authority scope and limitation, and build an implementation-neutral brief. Inspect the real project before proposing or making code changes.