kgoedecke/doop
The open-source alternative to Paper.design. A multiplayer design canvas where humans and AI agents design together, live. MCP built in.
About kgoedecke/doop
kgoedecke/doop is an open-source project on GitHub, mainly written in TypeScript. The open-source alternative to Paper.design. A multiplayer design canvas where humans and AI agents design together, live. MCP built in. It currently holds 1,542 stars and 185 forks with 70 open issues, and was last pushed on 2026-11-02 (repository created 2026-08-22).
Project Overview
AI Homed tracks it on the Today's Trending board, currently at rank #24 with 162 new stars today.
GitHub Repository Details
README
Doop is the open-source alternative to Paper.design — a multiplayer
design canvas for humans _and_ AI agents. Every design lives on a shareable Canvas
(/c/) holding Frames — artboards that render real HTML in sandboxed iframes. People edit
in the browser; AI agents edit through the built-in MCP server, streaming their designs in
live. Everyone sees everything as it happens: cursors, presence, frame edits, agent status, and an
activity feed.
Think of it as Claude Design for whichever agent you already use: Claude Code, Codex, ChatGPT, Cursor, OpenCode or any other MCP client designs on the same canvas, and the built-in Doop Agent runs on GPT, Claude, Gemini, DeepSeek, Kimi or Qwen models (every agent and model).
- Design with agents, not prompts-and-refresh — connect Claude Code (or any MCP client) once,
- A built-in Doop Agent — queue a card or @mention a role and it designs on its own, no client
ANTHROPIC_API_KEY for as many
free tasks as RESIDENT_TASK_LIMIT grants (none by default) (setup); the
first-canvas welcome performance is scripted and runs without any of it.
- Pages within a canvas — organize frames into named pages from the Layers panel. Add, rename,
get_canvas, manage them with set_canvas_pages (passing the original list as
expectedPages to protect collaborators), and target frames with pageId.
- Clickable prototypes — wire elements to other frames (click, hover, press, key or delay;
/c//proto. Agents use the same
data-doop-* attributes plus get_prototype / set_prototype_start.
- A real canvas editor — draw frames, shapes, pen paths and text, edit any element's fill,
- True multiplayer — live cursors, presence, follow mode, per-frame editing indicators,
- Design memory — pin exemplar frames, capture decisions, and let the distiller propose durable
- Private by default — invite collaborators by email or share a link that can view, comment
- Self-host in one command —
docker compose up, orbun run devwith zero configuration
Works with any agent
Doop isn't tied to one model vendor. Every agent below designs through the same MCP server, works as the person who connected it, and shows up live on the canvas with its own cursor, status and tasks. Connect AI in the top bar walks you through each one.
| Agent | How it connects |
| -------------------------------------------- | ------------------------------------------------------------------------------- |
| Claude Code | claude mcp add, OAuth in the browser (setup) |
| Claude (web and desktop) | Add to Claude in Connect AI (setup) |
| Codex (CLI and desktop) | codex mcp add, OAuth in the browser (setup) |
| ChatGPT | A custom MCP server in ChatGPT, guided by Connect AI → ChatGPT |
| Cursor | Add to Cursor in Connect AI |
| OpenCode, VS Code Copilot, OpenClaw and more | Any MCP client, over OAuth or with an agent key (setup) |
| Headless agents (n8n, Mastra, CI) | An agent key as a bearer header (setup) |
No agent of your own? The built-in Doop Agent runs on the model account you connect: a ChatGPT subscription, or an OpenAI, Claude, Gemini or OpenRouter key. OpenRouter brings DeepSeek, Kimi, Qwen, GLM and MiniMax (details).
Quickstart
git clone https://github.com/kgoedecke/doop && cd doop
bun install
bun run dev
Doop builds and installs with bun (bun.lock is the only
lockfile); the server itself runs on Node.
- Web app: http://localhost:4300
- API + WebSocket + MCP server: http://localhost:4400 (the web port proxies
/api,/ws,
/mcp, /.well-known, /i/, /ingest and /local-agent to it)
bun run dev and bun run build also package the Claude Desktop extension with a Node script,
so Node must be on your PATH as well.
Everything works with no configuration: data persists to an embedded Postgres (PGlite) in data/pg,
and every optional integration (SMTP, stock photos, object storage, analytics) degrades gracefully
until its variable in .env.example is set (the ones that matter).
The built-in Doop Agent runs once a user connects a model account in Settings
(or on the server's ANTHROPIC_API_KEY if you raise RESIDENT_TASK_LIMIT) — agents you connect
yourself over MCP need no key.
Or self-host the production build with Docker:
BETTER_AUTH_SECRET=$(openssl rand -hex 32) docker compose up -d # app + Postgres on :4400
Production build without Docker: bun run build && bun run start (single server on :4400 serving
everything). Set DATABASE_URL to use a real Postgres — same code path as PGlite.
Prefer not to run anything? doop.design is the hosted version.
Once you sign in, Home is where you start: describe what you want and Doop makes a canvas with drafts queued for the Doop Agent, or pick up one of your canvases, workspaces and connected agents.
The canvas editor
The bottom toolbar holds the tools; every one has a single-key shortcut. Shapes drawn on the canvas become standalone elements, and shapes drawn inside a frame become positioned HTML/SVG layers of that frame, so agents read and edit them like any other markup.
| Tool | Key | What it does | | ----------- | --- | ------------------------------------------------------------------------------------- | | Select | V | Click to select, drag the background for a marquee, ⇧/⌘-click to add to the selection | | Hand | H | Pan (Space or the middle button pans from any tool) | | Frame | F | Draw an empty frame | | Rectangle | R | Draw a rectangle | | Circle | O | Draw a circle or ellipse | | Vector path | P | Bézier pen: snaps to its own anchors, previews closing the path; Alt skips snapping | | Text | T | Place a text layer | | Comment | C | Pin a comment to an element or to the canvas |
- Frames — drag to move, pull the corner handle to resize, snap to neighbours and guides.
- Elements inside a frame — click to select, drag a corner grip or edge to resize (⇧ keeps the
W × H badge shows the size), drag the element to
move it within or across frames. The Design tab edits fill, stroke, text (font, size, weight,
alignment), opacity, corner radius, rotation, position, flex layout (direction, gap, padding,
wrap, alignment) and image fills; HTML shows its source; Prototype wires interactions. The
floating toolbar adds Comment, Ask AI (pre-fills an @mention), Code, Edit text and Copy link.
- Path editing — double-click a path to drag its anchors and Bézier handles, switch points
- Layers — a searchable tree of pages, frames and elements: drag to reorder or reparent, hide,
- Rulers and guides — ⇧R shows rulers; drag out of one to add a guide. Guides belong to the page,
- Zoom — 8% to 1600%. Wheel pans, ⌘/Ctrl + wheel or a pinch zooms; a 1px pixel grid fades in from
- Panels — the right side panel has Agents, Comments, Activity and Memory tabs;
- Themes — Light, Dark or System under Settings → Appearance.
- Phones — the canvas works on a phone: one-finger pan, pinch zoom, tap to comment, and bottom
| Shortcut | Action | | ---------------- | ------------------------------------------------------ | | ⌘Z / ⌘⇧Z (or ⌘Y) | Undo / redo your own edits | | ⌘C / ⌘V / ⌘D | Copy, paste, duplicate frames or layers | | ⌫ | Delete the selected element, else the selected frames | | ⌘⇧H / ⌘⇧L | Hide / lock the selection | | ⌥↑ / ⌥↓ | Move a layer up or down (Layers panel) | | ⇧1 / ⇧2 | Zoom to fit everything / the selection | | ⌘0 / ⌘+ / ⌘− | Zoom to 100%, in, out | | ⇧R | Toggle rulers | | ⌘. | Hide or show all UI | | ⌘K | Open the Agents composer (on Home: the search palette) | | Esc | Deselect, stop following |
Click a collaborator's avatar to follow their viewport; an agent's avatar flies you to what it is working on. Placeholder frames show where an agent that has picked up a card is about to design.
Comments, imports and exports
Comment on any element or anywhere on the canvas. The Comments tab lists the page's threads
(open or resolved) with their replies. @mention an agent role in a comment or a reply (for example
@doop) to queue a design card; the agent's answer comes back in the thread. People who miss a
comment get an email digest (opt out under Settings → Account), and canvases opened through a
view-only or comment-only link show a badge and disable editing.
The import source picker offers Website (one page, or discover a whole site and pick its pages),
Live app (the sync snippet), and
GitHub repo (through the GitHub App or a fine-grained token: Doop reviews the repo's screens and
components and queues cards for the Doop Agent to sketch them and extract the design system into a
style guide).
Right-click a frame and choose Export… to download PNG, JPG or a vector PDF (of the frame, or of
every selected frame as one PDF). Export in the top bar binds any frames of the page into one PDF. A progress toast tracks the
render; the desktop app opens its native save panel. Every frame also has a public live image at
/i/.png?scale=2 (or .jpg) that re-renders when the design changes, handy as an
og:image or in docs.
Figma, Canva and Photoshop (PSD) import and export are currently available in Doop Cloud and not part of the open source.
Integrations
Integrations in the rail is where an account connects the outside tools Doop works with:
| Integration | What it does |
| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
| Linear | Read issues through MCP, or delegate an issue to Doop: it designs a canvas and reports the result back to Linear (setup) |
| Slack | Mention @Doop with a brief; it designs a canvas and posts the result in the thread (setup) |
| Meta Ads | Pull ad creatives onto a canvas on a schedule with an automation |
The Figma integration (import frames as editable HTML, export frames back to Figma) and the Canva integration (import designs as editable frames, send frames back with live text) are currently available in Doop Cloud and not part of the open source. A self-hosted Integrations page shows Linear, Slack and Meta Ads.
Outbound webhooks (Settings → Webhooks) POST a signed JSON event to your own URL when a comment is created, replied to or resolved, when a frame is created, or when an agent finishes or fails a board card, with retries and a test ping (events and signatures).
To reference a specific element in feedback, select it and choose Copy link
in its floating toolbar, or right-click its Layers row and choose Copy link to
element. Opening the link selects the element and opens its properties on the
correct page. The URL includes the canvas ID, frame ID and URL-encoded CSS
selector, so an AI agent can locate it in the frame HTML. Canvas access rules
still apply. Selectors that use element IDs survive layout changes; selectors
based on sibling positions can change when the HTML is restructured.
Approve screens for development
Select a frame and turn on Development → Mark as approved in the inspector, or right-click one or more frames and choose Mark ready for dev. A green badge appears above the screen and in Layers. Hover the toggle row or a badge to see who approved it and when. Turn the toggle off to move an approved screen back to draft.
Changing the HTML or frame dimensions switches an approved screen to Needs review; review it and turn Mark as approved on again. Moving, renaming, hiding, locking, or moving between pages keeps approval. Copies start as drafts. An approval checks the frame revision so a concurrent edit cannot accidentally be approved, and waits for live design streams to finish.
Agents can read approvalStatus (draft, ready_for_dev, needs_review) and
approval attribution in get_canvas and get_frame. Call
get_canvas({ canvas_id, approval_status: "ready_for_dev" }) to find approved
screens, then re-read get_frame before implementing. Only ready_for_dev is
current sign-off. Approval is set by people in the app. In Automations, choose
Designs are approved to run a workflow when frames on a selected canvas become
ready for dev. Without an enabled workflow, approval only records sign-off.
The REST equivalent is PUT /api/frames/:id/approval with
{ status: "ready_for_dev" | "draft", expectedUpdatedAt }. The signed-in user's
identity supplies the attribution; the endpoint uses the same canvas access rules
as editing and returns 409 when the reviewed revision is stale.
Clickable prototypes
Turn frames into a flow you can click through. Switch on Prototype mode (top bar), pick an element and add an interaction in its Prototype tab, or drag the handle on its right edge onto another frame. Each interaction is a trigger (click, hover, press, a key or a delay) and an action (go to a frame, open one as an overlay, go back, close the overlay, scroll, open a link), with an optional transition: dissolve, slide or push. Connectors on the canvas show where every element leads, and a Start flag marks the frame each page's flow begins on.
Press Play to run it full screen, or share /c//proto: the player follows the
same canvas access rules, and the browser's Back and Forward walk the flow. Frames stay live
while you play, so an edit on the canvas shows up on the screen you are looking at.
Interactions are plain attributes on the element in the frame HTML, so they sync, version and export with the frame, and agents write them with the same tools they design with:
" data-doop-transition="push-left">Book stay
Agents check their wiring with get_prototype, which flags links to missing frames, and set
the start with set_prototype_start. Both the MCP server and the built-in Doop Agent have them.
The full attribute reference is in .context/specs/prototyping.md.
iPhone and iPad app
The SwiftUI iOS app lives in ios/. Open ios/Doop.xcodeproj
in Xcode to run it against Doop Cloud or your own HTTPS server. It uses SwiftUI for the app interface and a native canvas that
renders frames with the Blitz HTML/CSS engine (Rust, no WebKit), over the same REST API and WebSocket rooms. The app is in development;
see the iOS README for validation status and remaining release requirements.
Connect Claude
Choose Connect AI → Claude → Add to Claude. On hosted Doop, this opens Claude's connector form with Doop's name and server URL filled in. Confirm it, sign in to Doop, then start a new Claude chat and paste the canvas prompt from the dialog. No file download, terminal or API key needed.
The updated Doop desktop app also offers Add to Claude for local and self-hosted
servers: it opens Claude Desktop's extension installer directly, with your server
URL filled in. Confirm the installation in Claude and approve the Doop sign-in.
The online connector needs a publicly reachable HTTPS server; localhost connections
use the desktop app. Manual extension installation remains available as a fallback.
Build and installation details: claude-extension/.
Hook up Claude Code
One command connects Claude Code (or any MCP client) to your canvas:
claude mcp add --transport http doop http://localhost:4300/mcp
That triggers the standard MCP OAuth flow — a browser window opens, you approve, and from then on
the agent works as you. Ask it to design something on your canvas id and watch it happen live.
Everything in this shot is the real flow: Claude Code announced itself with set_status, created a
frame, and is streaming the pricing section in — presence avatar, "for Kai Moreno" attribution,
the frame chip, the working strip, and the task in the Agents panel.
Watch an agent design
The first canvas after signup comes with a performance: the Doop Agent streams a welcome design in while you watch — status in the working strip, a task in the panel, a pulsing border on the frame it's building.
That welcome performance is scripted (server/demo.ts) — a pre-authored frame replayed through
the same machinery real agents use, so it runs with no configuration at all. The Doop Agent proper
needs a key.
The Doop Agent
Doop ships a built-in design team that lives in the server and picks work up on its own: queue a
board card, @mention a role in a comment, or post task feedback over the API, and it runs
without a human in the loop. Roles (Doop builds; specialists own one pass each — UX, copy, brand,
accessibility) are defined in shared/agents.ts, and a card can be routed
through several in order.
Normally each user's own connected model account pays for their runs (next section). The server
can also pay for a free tier, on Anthropic by default, once RESIDENT_TASK_LIMIT is above 0:
ANTHROPIC_API_KEY=sk-ant-... # in .env, or the environment of your deployment
Same key gates the guideline distiller (server/distill.ts), which proposes
durable style rules from your canvas.
The free tier can run on Azure OpenAI instead — useful when your organisation's credits or compliance rules live there:
```bash DO