Agent integration

Works with the agents you already use.

build69 speaks the Model Context Protocol, so any MCP-aware assistant can fetch components. Point it at one URL and go.

CClaude

Add the server in Claude's connector settings. Native tool-calling picks the right component.

⌘Cursor

Drop the MCP config into .cursor/mcp.json and prompt inline.

</>VS Code

Works with MCP-enabled extensions and Copilot agent mode.

{ }Custom

Any MCP client or your own agent — the protocol is open and documented.

Under the hood

The agent decides, the registry delivers.

You describe the UI. The agent maps intent to a component, calls get_registry_item, and writes the resolved source into your project — with the right imports and dependencies already handled.

1You prompt: “add a KPI dashboard row”

2Agent fetches StatCard + Sparkline

3Source lands in your repo, on-brand

// tool call
get_registry_item({ name: "StatCard" })
✓ 4 files · 1 dep · tokens ✓

get_registry_item({ name: "Sparkline" })
✓ 1 file · 0 deps

→ wrote src/dashboard/kpis.tsx

Connect your agent in under a minute.

Get your API key Read setup docs