Skip to content
Back to search

paprika

Local design tool for AI agents with a built-in MCP server · Ferramenta de design local para agentes de IA com servidor MCP embutido

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/leonardo-moraes360--paprika/badge.svg)](/listings/leonardo-moraes360--paprika)

HTML

<a href="/listings/leonardo-moraes360--paprika"><img src="/api/listings/leonardo-moraes360--paprika/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 113 lines
  1. 🇺🇸 English | [🇧🇷 Português](README.pt-BR.md)
  2. <p align="center"><img src="docs/brand/icon.svg" alt="Paprika icon" width="128"></p>
  3. <p align="center"><img src="docs/assets/paprika-window.png" alt="Paprika canvas open on the brand proposals: layers on the left, canvas in the middle, document tokens on the right" width="900"></p>
  4. # Paprika
  5. **A design tool where you and your AI agent draw together.**
  6. You open a canvas in your browser. Your agent (Claude Code, or any other agent that speaks [MCP](https://modelcontextprotocol.io)) gets its own set of tools to create screens, components and diagrams on that same canvas. You watch its cursor move while it works, fix things by hand whenever you like, and undo anything either of you did.
  7. Everything runs on your own computer. There is no account to create, no usage limit and no cloud service holding your designs.
  8. ## Why you might like it
  9. - **Your agent can design, not only write code.** Ask for a login screen, a flowchart or a set of icons and see it appear.
  10. - **You stay in control.** You see what the agent is touching as it happens, and you share one undo history, so nothing is lost.
  11. - **The agent checks its own work.** It can take screenshots and run checks for color contrast, text that doesn't fit and missing design tokens before it tells you it's done.
  12. - **From design to code.** A design can be exported as HTML, a React component or SVG.
  13. - **It stays yours.** Designs live in a local database and can be exported to a plain file you can keep in git.
  14. ## Get started
  15. You need [Docker](https://docs.docker.com/get-docker/). Then, in a terminal:
  16. ```bash
  17. git clone https://github.com/leonardo-moraes360/paprika.git
  18. cd paprika
  19. docker compose up -d --build
  20. ```
  21. The first build takes a few minutes. When it finishes:
  22. 1. Open **http://localhost:4777** in your browser. You'll see your workspaces; double-click one to open its canvas.
  23. 2. Connect your agent to **http://localhost:4777/mcp**. With Claude Code:
  24. ```bash
  25. claude mcp add --transport http paprika http://localhost:4777/mcp
  26. ```
  27. Other agents: add an MCP server of type "HTTP" (sometimes called "streamable HTTP") with that address.
  28. 3. Ask your agent for something, like *"Use Paprika to design a sign-up screen for a coffee shop app."*
  29. Your designs are kept in a Docker volume, so they survive restarts. `docker compose down` stops Paprika; `docker compose up -d` starts it again.
  30. Prefer not to use Docker? See [running from source](docs/development.md#run-from-source).
  31. ### Or let your agent set it up
  32. Copy this prompt into your agent (it works best in one that can run terminal commands, such as Claude Code):
  33. ```text
  34. Please set up Paprika for me, a local design tool for AI agents
  35. (https://github.com/leonardo-moraes360/paprika).
  36. 1. Check that Docker and Docker Compose are installed and running. If they
  37. aren't, stop and tell me how to install them; don't install anything
  38. without asking me first.
  39. 2. Clone the repository into a folder of my choice (ask me; default to
  40. ~/paprika) and run `docker compose up -d --build` inside it. The first
  41. build can take a few minutes.
  42. 3. Wait until http://localhost:4777/api/workspaces answers, then tell me to
  43. open http://localhost:4777 in my browser.
  44. 4. Add Paprika to yourself as an MCP server over HTTP at
  45. http://localhost:4777/mcp. In Claude Code:
  46. claude mcp add --transport http paprika http://localhost:4777/mcp
  47. If you need a restart or a new session to see the new tools, tell me.
  48. 5. Once the tools show up, call `get_design_guide`, then draw a small welcome
  49. frame on the canvas so I can see it working.
  50. If something fails, show me the error and what you'd suggest. Keep host port
  51. 4777: the server only accepts that port.
  52. ```
  53. ## What you can do
  54. - Organize designs into **workspaces**, each with its own pages and a cover on the overview.
  55. - Draw frames, shapes, text, images and free **vector paths** with the pen tool.
  56. - Build **components** and reuse them as instances; switch **light and dark themes** with design tokens.
  57. - Make **diagrams**: boxes, decisions, sticky notes and arrows that follow the shapes.
  58. - Paste SVG or HTML from anywhere and get editable layers; download the result as SVG.
  59. - See **every connected agent** on the canvas with its own cursor, name and color.
  60. - Work as a **team without a server**: `paprika serve --team` connects each person's Paprika and agents peer to peer (Iroh + a Loro CRDT), with invites by link or QR and only the team's keys accepted ([Team sync](docs/team-sync.md)).
  61. The full list of tools and shortcuts is in [Using the canvas](docs/canvas.md).
  62. ## Learn more
  63. | If you want to… | Read |
  64. |---|---|
  65. | Learn the canvas, shortcuts and diagrams | [Using the canvas](docs/canvas.md) |
  66. | Connect an agent, see every MCP tool and the file format | [Agents and MCP](docs/mcp.md) |
  67. | Run with Docker: import, export, backups, ports | [Docker](docs/docker.md) |
  68. | Build from source, run the tests, contribute code | [Development](docs/development.md) · [CI](docs/ci.md) |
  69. | Understand how it is built | [Architecture](docs/architecture.md) · [Go server](server-go/README.md) · [Decisions (ADRs)](docs/adr/) |
  70. | See what's planned | [Backlog](docs/backlog.md) |
  71. ## Good to know
  72. - Paprika listens only on your own machine (`localhost`) and has **no login**. Don't expose it to a network you don't trust.
  73. - Taking screenshots and exporting SVG use a headless Chrome, which the Docker image already includes.
  74. - Found a security problem? Please report it privately, as described in [SECURITY.md](SECURITY.md), not in a public issue.
  75. ## Contributing
  76. Ideas, bug reports and pull requests are welcome. Start with [CONTRIBUTING.md](CONTRIBUTING.md); everyone taking part follows the [Code of Conduct](CODE_OF_CONDUCT.md).
  77. Paprika is an original project. Paper (paper.design) was only a conceptual reference ("an HTML/CSS canvas connected to agents"); no code, assets or behavior were copied or reverse-engineered.
  78. ## License
  79. [MIT](LICENSE)

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.