All servers / Docs / VaneUI MCP server
VaneUI MCP server
Model Context Protocol server that exposes VaneUI component documentation as resources for MCP-aware clients.
Tested by ConnectATDScore 86 out of 100. Tested 2026-11-19 on package version 1.3.0. Package: @vaneui/mcp · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 20 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 8 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (2.7 seconds including download)
- Tools offered: 3
- Last published: 2026-11-16
- Weekly downloads (npm): 761
- License: MIT · Direct dependencies: 2
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
search_docs3 of 3 parameters describedSearch the VaneUI docs (component pages, guides, usage rules, prop-to-Tailwind mapping). Give a few words or an exact name such as `themeDefaults`. Results are doc sections, best first: sections that hold every word come before sections that hold some, and a word in a heading or page title counts more than one in the text. Returns a JSON array of up to `limit` sections, each with `slug`, `section`, `heading`, `lineNumber` and a short `snippet`, and says when more sections matched than were returned. Pass a result's `slug` and `section` to get_doc to read that section. Use this before guessing prop names, defaults, or class mappings.
get_doc2 of 2 parameters describedRead a VaneUI docs page. With only `slug` it returns the page's intro and the list of its sections; with `section` it returns that section in full, code examples included. Call search_docs first when you do not know which page or section holds the answer: each of its results has the `slug` and `section` to pass here. Component pages (`button`, `modal`, `field`, ...) hold what get_component_props does not list: value props such as `open` and `onClose` or `label` and `error`, sub-components and examples.
get_component_props2 of 2 parameters describedReturn a VaneUI component's boolean props, one line per category, default marked `*`. By default (`compact`) it lists the component's own props and names the shared layout categories it takes; slug `common` lists those once. detail `full` adds descriptions and every shared prop. Value props such as `label` or `title` are on the component's page: call get_doc with the same slug. The slug is the resource basename: `button`, `card`, `icon-button`, etc.
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.