What if your team could design, iterate, and deploy entire products without ever leaving a Slack thread?

👉 That's Paper Builder. It follows your team's conversation, generates the product you're envisioning on Paper, and deploys it on Vercel. Directly in the Slack channel. From single pages to entire flows, by using your design system. Just tag Paper Builder in the thread. Under the hood, a Python server orchestrates three flows: 1. 🔍 The Intent Detection Flow: Claude CLI - Agent 1 reads the Slack thread and classifies the request as design or deploy. 2. 🎨 The Design Flow: Claude CLI → Paper MCP - The server checks if a design system folder exists in the project. - Agent 2 checks if a design system exists on the Paper canvas. - Agent 3 uses the Paper MCP to build or refine the UI, applying the design system tokens 📝 Paper MCP tools used: + get_guide: To load design-specific instructions.

+ get_basic_info: To understand the current canvas state.

+ write_html & update_styles: To create and edit visual elements.

+ get_screenshot: To capture the design for Slack review.

+ finish_working_on_nodes: To finalise the session on Paper. 3. ⚒️ The Deploy Flow: Claude CLI (→ Paper MCP) → React/Vite → Vercel

- Agent 4 exports the artboards as React components and image assets.

- Agent 5 wires the navigation between screens and prepares the app for deployment. 📝 Paper MCP tools used: + get_jsx: To transform canvas components into React components. + get_computed_styles: To extract exact CSS tokens from the artboards. + get_fill_image: To download icons and images for the local bundle.

It's open source, run it yourself and share your feedback: https://github.com/valeeff/paper_builder_on_slack