Skip to content
SPECIFICTION
Get listed

Handoff

handoff.com

WebWindowsmacOSLinuxAPISelf-hosted
Visit handoff.com
Spec score 7.9 #3 of 15 in Component Libraries Software

What it is

Handoff is an open-source tool for design system documentation and automation for teams and AI agents. A browser UI, REST API, and MCP server all read from the same underlying data. Figma is the only source currently wired up: a workspace can pull design tokens from Figma and push tokens, components, documentation, and assets to a registry. Handoff can create documentation pages for React and other component libraries, including live previews, properties, and tokens. Its token pipeline converts Figma tokens into CSS, SCSS, Tailwind, and DTCG outputs. Compatible agents such as Claude, Cursor, and Windsurf can access design system data through the MCP server; agents can also create component pages and usage guidelines for team approval. A promptable design space supports exploration with approved components, tokens, and brand patterns. Workspaces can use local filesystem-backed mode or a Postgres-backed registry, deployable with Docker or Vercel. The docs describe 56 MCP tools across 12 categories and an OpenAPI 3.1 specification for each registry’s REST API. Each registry currently serves one workspace, and the handoff-app package requires Node 20.9 or later. Other data sources and destinations are future direction, not shipped connectors.

Spec sheet

Purpose
Handoff provides automated design system documentation for teams and AI agents.Read 4 Oct 2026 · handoff.com
Product
Handoff is design system documentation and automation with a UI, REST API, and MCP server reading from the same underlying data.Read 3 Oct 2026 · handoff.com
Intended users
Handoff describes itself as built for designers, engineers, project managers, and their agents.Read 4 Oct 2026 · handoff.com
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.Read 3 Oct 2026 · handoff.com
API
Each registry publishes an OpenAPI 3.1 specification for its REST API.Read 4 Oct 2026 · handoff.com
Security
The registry docs describe browser UI session authentication and bearer-token authentication for CLI and MCP clients.Read 3 Oct 2026 · handoff.com
Support
The contact page says messages are read by a human and directs bugs, feature requests, and pull requests to the open source repository.Read 4 Oct 2026 · handoff.com
Agent access
Handoff’s MCP server lets compatible agents including Claude, Cursor, and Windsurf access design system data.Read 3 Oct 2026 · handoff.com
Agent contributions
Agents can create component pages and usage guidelines, with team approval.Read 4 Oct 2026 · handoff.com
Code documentation
Handoff can create documentation pages for React or other component libraries, including live previews, properties, and tokens.Read 3 Oct 2026 · handoff.com
Documentation
Handoff serves design system data through a browser UI, a REST API, and an MCP server that read from the same underlying data.Read 4 Oct 2026 · handoff.com
Figma source
The docs say Figma is the only source currently wired up, and workspaces can fetch design tokens from Figma.Read 3 Oct 2026 · handoff.com
Figma workflow
A workspace can pull design tokens from Figma and push tokens, components, docs, and assets to a registry.Read 4 Oct 2026 · handoff.com
Hosting
The docs describe deploying a registry with Docker or Vercel.Read 4 Oct 2026 · handoff.com
Install requirement
The handoff-app package requires Node 20.9 or later.Read 3 Oct 2026 · handoff.com
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.Read 4 Oct 2026 · handoff.com
Local requirements
The workspace install requires Node 20.9 or later.Read 4 Oct 2026 · handoff.com
MCP support
The MCP server is described as compatible with Claude, Cursor, Windsurf, and other MCP-speaking tools.Read 4 Oct 2026 · handoff.com
MCP tools
The documentation lists 56 MCP tools across 12 categories, including tools for tokens, components, assets, documentation, and build and sync workflows.Read 4 Oct 2026 · handoff.com
Prototype
The product offers a promptable design space for exploring ideas with approved components, tokens, and brand patterns.Read 3 Oct 2026 · handoff.com
Prototyping
The site describes a promptable design space for exploring ideas with approved components, tokens, and brand patterns.Read 4 Oct 2026 · handoff.com
Registry limit
The docs state that one registry currently serves one workspace, with multiple workspaces sharing a database deferred.Read 3 Oct 2026 · handoff.com
Registry storage
A registry stores workspace data in Postgres and serves it through the UI, REST API, and MCP.Read 4 Oct 2026 · handoff.com
REST API
Each registry publishes an OpenAPI 3.1 specification for its REST API.Read 3 Oct 2026 · handoff.com
Token pipeline
Handoff converts Figma tokens through the DTCG pipeline into CSS, SCSS, Tailwind, and DTCG outputs.Read 3 Oct 2026 · handoff.com

Strong points and limits

Strong points

  • UI, REST API, and MCP use the same data
  • Converts Figma tokens into four output formats
  • Agents can draft pages for team approval
  • Local and Postgres-backed workspace modes

Limits

  • Figma is the only connected source
  • Each registry currently serves one workspace
  • Requires Node 20.9 or later

Who it suits

Handoff suits designers, engineers, project managers, and content editors maintaining a design system, along with agents that need access to its data. Teams relying on sources beyond Figma should note that Figma is the only wired-up source.

Verdict

Handoff connects design-system documentation, tokens, and agent access through shared workspace data. Its current Figma-only source and one-workspace registry limit are important constraints for teams evaluating it.

Where Specifiction places it

Alternatives to HandoffAll alternatives →