---
title: Design engineers
description: Drive a real vector canvas from Claude Code, Cursor or any MCP client, and keep the files in git. Unlimited canvas work on Free.
section: solutions
order: 2
featured: false
related: solutions/ship-to-code, agents/overview, developers/blueprint
---

# Brilliant for design engineers

Can the agent in my editor design on a real canvas? Yes. Brilliant runs a local MCP server the whole time the app is open, at http://127.0.0.1:3333/mcp, and any tool that speaks MCP can read and edit your canvas. Canvas work is unlimited on every plan, Free included; an image an agent generates on Brilliant AI draws on your Brilliant AI usage.

<DocFigure src="/docs/images/solutions/design-engineers-scene.webp" srcMobile="/docs/images/solutions/design-engineers-scene-390.webp" stage="panel" alt="A terminal agent editing a product card on the Brilliant canvas" caption="Your agent, in your editor, on the canvas." />

## How do I connect my editor?

Turn on its row in Settings, MCP Connections. The list holds Claude Code, Cursor, Codex, VS Code, Windsurf, Antigravity, Zed and more, and anything else takes one line of config. With Claude Code, opening the built-in chat once registers the endpoint for you. See [Connect your agent](/docs/agents/overview).

## What does an agent write?

Blueprint: one element per line, children indented under their parent, tokens in place of literals. You never have to write it yourself. Brilliant serves the grammar to agents over MCP.

```text title="Blueprint"
al(v,g($spacing.lg),pad($spacing.xl)) s(360,hug) f[($color.surface)] rd($radius.md) "Card"
  t("Settings",$font.family,$font.size.lg,sb) f[($color.text.primary)] #title
```

Values like $spacing.lg resolve through your design system, so an agent stays on your system by default. Read the [Blueprint language](/docs/developers/blueprint).

## Do design files behave like source?

Yes. A .bl file is plain, deterministic text: clean diffs, blameable history and branchable experiments. A published project is also a real git repository you can clone.

<DocFigure src="/docs/images/solutions/design-engineers-blueprint.webp" srcMobile="/docs/images/solutions/design-engineers-blueprint-390.webp" stage="panel" alt="A design beside the Blueprint text that describes it" caption="The canvas and the Blueprint text are the same design." />

## How do I get code back out?

Export a selection as HTML in three flavors, or as React JSX. Copy as puts the same thing on your clipboard, along with CSS properties or raw Blueprint. See [Ship to code](/docs/solutions/ship-to-code).

<DocFigure src="/docs/images/solutions/design-engineers-code.webp" srcMobile="/docs/images/solutions/design-engineers-code-390.webp" stage="panel" alt="A design exported as code" caption="From the canvas to code you can keep." />

## Common questions

### Does Brilliant need to be open?

Yes. The MCP server runs inside the app, on localhost.

### Can I drop my live React components on the canvas?

Brilliant components are design components. To work from your own, ask your agent to read your code and draw them, or to build from the canvas in your stack.

## Where next?

- Connect your editor: [Connect your agent](/docs/agents/overview).
- Learn the file format: [Blueprint language](/docs/developers/blueprint).
- See every format: [Import and export](/docs/workspace/import-and-export).
- Hand off without a document: [Ship to code](/docs/solutions/ship-to-code).
- Understand the layout on disk: [Canvases and files](/docs/workspace/canvases-and-files).
