Local developer preview

Give your assistant the actual source.

Discover components, read their real APIs, and retrieve the source you can own. DEVVY MCP connects your coding assistant to the library without adding AI dependencies to your application.

Find the right pieces

Search 100 components by name or task. Responses stay small until you request more.

Use the right version

Published 0.3.1 is the default. Workspace requests remain explicitly separate and unreleased.

Own the implementation

Get canonical TypeScript, dependency and helper closure, styles and MIT notices.

Connect from a local checkout

This optional tool is implemented in the repository. It is not published as an npm MCP package and has no hosted endpoint. Build the checkout before connecting:

Rebuild your local server to use the updated published-source pin. Updating this website does not replace a previously built MCP snapshot or change your editor configuration.

pnpm install --frozen-lockfile
pnpm build

Configure a local stdio server in your MCP client. Replace the example with the absolute path to your checkout. Configuration file formats vary by client.

{
  "mcpServers": {
    "devvy-ui": {
      "command": "node",
      "args": ["/absolute/path/devvy-ui/packages/mcp/dist/server.mjs"]
    }
  }
}

Connect your editor

Codex

codex mcp add devvy-ui -- node /absolute/path/devvy-ui/packages/mcp/dist/server.mjs
codex mcp list

Claude Code

claude mcp add --transport stdio devvy-ui -- node /absolute/path/devvy-ui/packages/mcp/dist/server.mjs
claude mcp list

Cursor

Merge the local-server JSON above into .cursor/mcp.json (project) or ~/.cursor/mcp.json (personal), then enable the server in MCP customizations.

VS Code

Use MCP: Add Server → Command (stdio), or merge this VS Code workspace configuration into .vscode/mcp.json. Copilot Global uses its own configuration destination; select the appropriate agent harness in the guided flow.

{
  "servers": {
    "devvy-ui": {
      "type": "stdio",
      "command": "node",
      "args": ["/absolute/path/devvy-ui/packages/mcp/dist/server.mjs"]
    }
  }
}

Use absolute paths and review your client’s trust prompt. DEVVY does not change editor settings automatically. Protocol tests and Inspector checks do not certify an interactive session in every editor.

Try a useful request

Find a searchable selector for our settings form.
Read its published 0.3.1 API and source dependencies.
Give me an installation plan, then explain how to customize
its colors while preserving keyboard behavior.

What the tools do

Tool	Result
`search_components`	Bounded component discovery by name and description.
`get_component`	Version-specific canonical API source and focused import.
`get_source`	Component, dependency/helper source and license; optional styles.
`get_guide`	Bundled customization, accessibility and contributor guidance.
`get_installation_plan`	Reviewed commands and required imports, without executing them.
`get_design_tokens`	Version-matched CSS tokens, selectors and media conditions; filtered and paginated.
`get_component_examples`	Verified compositions with real imports, dependency closure, styles and attribution.
`get_ui_recipe`	Settings form, project dashboard or adaptive Glass workspace using supported components.

Discover resources and reusable prompts

Read the versioned catalog, token, example and recipe resources via resources/list. Use build_ui, customize_theme or review_component from prompts/list to start with verified context. Example coverage is curated; unavailable examples are clearly marked.

{"name":"get_ui_recipe","arguments":{"recipe":"project-dashboard","version":"0.3.1"}}

Structured tool responses are capped at 384 KiB before SDK wire metadata. Source is never silently truncated. The official SDK handles current 2026-07-28 and legacy stdio clients. Standalone packaging is prepared, with publishing disabled until tests and a release review are complete.

Full setup, protocol references and verification guide ↗

Predictable boundaries

Tool requests read bundled data. They do not modify your project, execute shell commands, request secrets, or fetch arbitrary remote content. Source installation stays with the CLI and its conflict protection. This connection supplies context; your assistant and application remain responsible for reviewing generated changes.

The pinned published registry supplies 0.3.1 source, including optional table selection. Choose workspace only when you intend to use the unreleased checkout; unsupported versions are rejected. Development guides can describe newer features, so version-specific component source is the API authority.

Install the stable React library →