DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to design a page section live with Claude Code on a canvas with Doop

Connect Claude Code over MCP and watch it stream a frame onto your canvas as you follow along.

Who it is forA designer or developer who wants an AI agent to sketch a section, such as pricing, while watching it appear next to their cursor.

The problemPrompting an AI for HTML and refreshing a browser to check each change is slow and disconnected from the design.

The outcomeA new frame with a streamed section on your canvas, created by Claude Code acting as you, visible in the activity feed.

What you need first

  • Git and bun installed (the README says Doop builds and installs with bun, and the server runs on Node)
  • Claude Code or another MCP client, for connecting an agent over OAuth
  • Docker, only if self-hosting the production build
  • An ANTHROPIC_API_KEY, only if you want the built-in Doop Agent to run

Steps

  1. Run git clone https://github.com/kgoedecke/doop && cd doop
  2. Run bun install
  3. Run bun run dev and open http://localhost:4300
  4. Create or open a canvas, then run claude mcp add --transport http doop http://localhost:4300/mcp
  5. Approve the OAuth prompt in the browser, then ask Claude Code to design a pricing section on your canvas

Prompt for your agent

In the repo kgoedecke/doop, the Doop server is running on http://localhost:4300 with the MCP endpoint at /mcp. Using the doop MCP server, create one frame on the canvas <canvas-id> with a three-tier pricing section, then call get_canvas to confirm the new frame is listed. Report the frame id and the number of frames on the canvas.

Caveat. The README describes this flow on a local dev server, and the agent works as the approving user, so only connect accounts you trust to edit the canvas.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page