VDS

Agents

AI and MCP integration for VDS.

VDS supports AI- and assistant-driven installs through the Model Context Protocol (MCP). This lets tools add components directly into your project.

Use the @vds-testing/mcp server or a similar MCP adapter to expose VDS component installation commands to your assistant.

The vds MCP server connects your AI assistant directly to the component registry. Ask for components in plain language and they get added to your project automatically.

Model Context Protocol is an open standard supported by Claude, Cursor, VS Code, and other AI tools.

Setup

Add to .cursor/mcp.json in your project:

{ "mcpServers": { "vds": { "command": "npx", "args": ["-y", "@vds-testing/mcp"] } } }
{
  "mcpServers": {
    "vds": {
      "command": "npx",
      "args": ["-y", "@vds-testing/mcp"]
    }
  }
}
  • Restart Cursor to load the server
  • Ask: "Add the dialog and button components from vds"

What your AI can do

Tool What it does
list_components Show all available components by category
search_components Find components by name or description
get_component View source code and dependencies
add_component Add component files to your project
add_components Add multiple components with dependency resolution (barrel last)

Components go to src/components/vds/, utilities to src/utils/, and theme styles to src/styles/.

For named imports from a single path, ask your assistant to add the barrel component after other components are installed.

For interactive components, the MCP flow also adds shared runtime files to src/utils/runtime/ so behavior works out of the box with no extra setup.

If a component needs an npm package, you’ll be told what to install.

Example prompts

  • “What form components does vds have?”
  • “Add the tabs and accordion components”
  • “Add the tabs, accordion, and barrel components”
  • “Show me how the dialog component works”
  • “Build a settings page with cards and switches”

Environment

Variable Default
VDS_REGISTRY_URL https://kds-staging.vercel.app/registry
VDS_REGISTRY_PATH Local registry path for development (unset)