Paper is a design tool that connects canvas, code, and AI agents so teams can create, share, and ship work in one workflow. Includes desktop app and MCP access.

Paper

What Paper is

Paper is a design tool built around a connected canvas for teams, agents, code, and data. Its site describes a workflow based on web standards, where design work can move between the canvas and code without losing structure or context.

The product centers on a Paper Desktop app and a Paper MCP server that lets AI agents read and write design files. The docs also point to related workflows for Snapshot, tokens, paste, SVGs, and vector editing, making Paper more than a single canvas view and more of a design workspace tied to implementation and content sources.

Features

Connected canvas for teams and agents

Paper is positioned as a connected canvas where teams can work with agents, code, and data in one design space built on web standards.

MCP-based agent access

The Paper MCP server lets AI agents read and write design files, so agents can use design context and help move content between sources and the canvas.

Desktop app-powered local server

The desktop app starts the MCP server in the background when a file is opened, which keeps the agent connection tied to the local Paper session.

HTML/CSS canvas with code export

Paper's HTML/CSS canvas exports design work as code, which supports a back-and-forth workflow between design and implementation.

Real-content and token workflows

The docs and homepage describe using real content, design tokens, styles, and components from files, CMSs, databases, or other apps instead of placeholder content.

Snapshot extension for editable components

A Paper Snapshot extension is available for copying and pasting web components directly into Paper as editable layers.

Common use cases

  • Collaborative product design

    Teams can keep design work, code context, and connected data in one place when they need a canvas that aligns with implementation rather than isolated mockups.

  • Agent-assisted design workflows

    Designers using Cursor, Claude Code, Codex, or other MCP-compatible tools can ask agents to read and write design files, pull context in, and help manage repetitive changes.

  • Content-driven layout work

    When working from real content, tokens, styles, or components, teams can sync those sources into Paper instead of filling layouts with placeholder text.

  • Design-to-code iteration

    Developers and designers can move between the canvas and code using the HTML/CSS export workflow, which supports a more continuous handoff.

  • Web component capture

    Users who need editable representations of web UI can paste components into Paper with Snapshot instead of starting from static screenshots.

Pros and Cons

Pros

  • Combines design work, code-oriented export, and agent-assisted workflows in one product.
  • Supports reading and writing through MCP, which makes it practical for agent-driven design tasks.
  • Provides concrete setup paths for several tools, including Cursor, Claude Code, Claude Desktop, Codex, Copilot, and OpenCode.
  • Offers a free entry plan and a clearer paid path for advanced usage and teams.
  • Includes Paper Snapshot for turning web components into editable layers instead of screenshots.

Cons

  • Some capabilities are still only lightly documented on the public site, so it is harder to judge the full depth of the editor and collaboration features from the available pages alone.
  • Desktop and MCP workflows depend on the local Paper app and a compatible host tool, so setup involves more than using a web-only editor.

FAQ

How do you connect AI agents to Paper?

Paper Desktop is required to use the Paper MCP server. Once the app is installed, opening a file in Paper starts the MCP server in the background.

Which tools can connect to Paper's MCP server?

The docs show connections for Cursor, Claude Code, Claude Desktop, Codex, Copilot, Antigravity, and OpenCode. The general pattern is to install or register the Paper MCP server, then connect the host tool to the local server at `http://127.0.0.1:29979/mcp` when using the manual setup path.

What platforms are available for Paper Desktop?

The downloads page lists Paper Desktop builds for Linux (AppImage), Linux (Deb), Linux (RPM), macOS (ARM), and Windows (x64).

Does Paper have a free plan?

The pricing page shows a Free plan and paid Pro and Organizations plans. Free includes limited MCP tool calls, limited image generation, a 25 MB max image size, and limited collaboration files; Pro adds higher limits and extra features such as video export and unlimited collaboration files; Organizations adds SAML/SSO, admin controls, custom contracts, dedicated support, and priority onboarding.

What kinds of workflows does Paper support?

The docs list sections for MCP, Snapshot, Tokens, Paste, SVGs, and support, which suggests Paper is built around working with web content, design tokens, pasted designs, and vector editing workflows.

Quick Facts

Category
Design tool
Primary workflow
Design, share, and ship work from a connected canvas
Agent integration
Paper MCP server for read/write access
Desktop availability
macOS, Windows, and Linux builds listed
Pricing
Free, Pro, and Organizations plans
Source domain
paper.design

Analysen zu Paper

Traffic-Daten dienen nur als Referenz.

Traffic & Rankings

Monatliche Besuche
319.054
Durchschn. Besuchsdauer
01:43
Seiten pro Besuch
3.75

Traffic-Trends

Top-Regionen

  • Vereinigte Staaten: 26.0%
  • Indien: 8.59%
  • Deutschland: 7.83%
  • Brasilien: 4.01%
  • Vereinigtes Königreich: 3.61%
  • Andere: 49.9%

Traffic-Quellen

  • Direkt: 47.1%
  • Suche: 29.7%
  • Verweise: 9.11%
  • Social: 11.0%
  • E-Mail: 1.68%
  • Display-Anzeigen: 0.53%