Handoff
handoff.com
- Windows
- macOS
- Linux
- Web
- API
- Self-hosted
What Handoff is
Handoff is open-source design system documentation and automation for teams and AI agents. Its browser UI, REST API, and MCP server read from the same underlying data. A workspace can pull design tokens from Figma, then push tokens, components, documentation, and assets to a registry. Handoff creates documentation pages for React and other component libraries with live previews, properties, and tokens. Its token pipeline converts Figma tokens into CSS, SCSS, Tailwind, and DTCG outputs. MCP-compatible agents, including Claude, Cursor, and Windsurf, can access design system data; agents can also draft component pages and usage guidelines for team approval. A promptable design space supports exploration with approved components, tokens, and brand patterns. Workspaces run locally from a filesystem or through a Postgres-backed registry deployed with Docker or Vercel. Each registry currently serves one workspace. The handoff-app package requires Node 20.9 or later. Listed platforms include API, Linux, macOS, self-hosted, web, and Windows.
Who it suits
It suits design and engineering teams, project managers, content editors, and agents maintaining shared design-system information. Teams using Figma and MCP-compatible tools can connect design data, documentation, and automation.
Good to know, and what to watch
- Serves one data set through UI, REST, and MCP
- Imports tokens from Figma
- Generates React component documentation with previews
- Exports tokens to CSS, SCSS, Tailwind, and DTCG
- Supports local or Postgres-backed deployment
- Figma is the only wired source
- Each registry currently serves one workspace
- Requires Node 20.9 or later
- Additional connectors are future direction
The verdict
Handoff links Figma tokens, component documentation, code-oriented outputs, and agent access in one open-source system. Its one-workspace registry model and current Figma-only source support should be considered during deployment planning.
What the maker publishes
- Agent access
- Handoff’s MCP server lets compatible agents including Claude, Cursor, and Windsurf access design system data. source
- Agent contributions
- Agents can create component pages and usage guidelines, with team approval. source
- API
- Each registry publishes an OpenAPI 3.1 specification for its REST API. source
- Code documentation
- Handoff can create documentation pages for React or other component libraries, including live previews, properties, and tokens. source
- Deployment
- Handoff has a local filesystem-backed workspace mode and a registry mode backed by Postgres; the registry can be deployed with Docker or Vercel. source
- Documentation
- Handoff serves design system data through a browser UI, a REST API, and an MCP server that read from the same underlying data. source
- Figma source
- The docs say Figma is the only source currently wired up, and workspaces can fetch design tokens from Figma. source
- Figma workflow
- A workspace can pull design tokens from Figma and push tokens, components, docs, and assets to a registry. source
- Hosting
- The docs describe deploying a registry with Docker or Vercel. source
- Install requirement
- The handoff-app package requires Node 20.9 or later. source
- Integration availability
- The docs say Figma is the only source wired up today; additional sources, npm packages, and CMS destinations are described as future direction rather than shipped connectors. source
- Intended users
- Handoff describes its intended team as designers, engineers, project managers, content editors, and their agents. source
- Intended users
- Handoff describes itself as built for designers, engineers, project managers, and their agents. source
- Local requirements
- The workspace install requires Node 20.9 or later. source
- MCP support
- The MCP server is described as compatible with Claude, Cursor, Windsurf, and other MCP-speaking tools. source
- MCP tools
- The docs describe 56 MCP tools across 12 categories, including tools for tokens, components, assets, documentation, previews, and build and sync. source
- MCP tools
- The documentation lists 56 MCP tools across 12 categories, including tools for tokens, components, assets, documentation, and build and sync workflows. source
- Product
- Handoff is design system documentation and automation with a UI, REST API, and MCP server reading from the same underlying data. source
- Prototype
- The product offers a promptable design space for exploring ideas with approved components, tokens, and brand patterns. source
- Prototyping
- The site describes a promptable design space for exploring ideas with approved components, tokens, and brand patterns. source
- Purpose
- Handoff provides automated design system documentation for teams and AI agents. source
- Registry limit
- The docs state that one registry currently serves one workspace, with multiple workspaces sharing a database deferred. source
- Registry storage
- A registry stores workspace data in Postgres and serves it through the UI, REST API, and MCP. source
- REST API
- Each registry publishes an OpenAPI 3.1 specification for its REST API. source
Checked against the maker's pages on 4 Oct 2026.