# Library

> Design context, for humans and agents.

The infrastructure your design system runs on. Components, tokens, and patterns — live, connected, and in context for your team and your agents.

## Why Library

Design used to have a source. Now it's everywhere — in Figma, in pull requests, in prompts someone typed at midnight, in code an agent wrote and nobody reviewed.

The gap between what was designed and what actually shipped used to be a process problem. Now it's an infrastructure problem. Components change faster than any wiki can track. Agents need context that traditional docs were never built to provide.

Library is that infrastructure: a live context layer for your design system — readable by your team, usable by your agents, always reflecting what your product actually is.

## Document

**Context that stays current, from Figma and code.**

Library reads your components, tokens, and patterns at the source — and keeps them in context as your product evolves. Bring Figma libraries (styles, components, variables) in directly, write pages by hand, or have an AI agent draft them from a Figma file.

## Publish

**Your context layer has a URL.**

A live, browsable site from day one. Updates the moment anything changes. Every workspace publishes to `your-workspace.preview.guide` automatically — no deploy step. Each page ships with an AI chat sidebar so visitors can ask questions in plain language, grounded in your design system.

Workspaces can be public (anyone with the link) or private (workspace members only). Custom domains are coming soon.

## Ask with AI

**Context you can have a conversation with.**

Ask anything in plain language and Library reasons across your components, tokens, patterns, and decisions to surface the answer. For your team today. For your agents tomorrow.

## MCPs

**Plays nicely with everyone.**

Library plugs into Claude, Cursor, v0, Windsurf, and more via MCP. Your design system becomes a tool every agent can read.

Public workspaces are read by default — no API key needed. Connect, and an agent can navigate folders, search pages, and read content. Private workspaces require a key. To let an agent write back (append docs, draft pages from Figma), create a key in Workspace settings with "Allow document writes" enabled.

The MCP exposes:
- `api.getWorkspace()` — explore folders, pages, and structure.
- `api.listDocuments()` — search and browse pages.
- `api.readDocument(id)` — read full page content.
- `write_design_context` — (with key) append updates to a page.

## Live preview

A real context layer, built with Library: https://index.preview.guide — components, tokens, patterns, and AI answers, live on a public URL.

## Pricing

Try free for 30 days. $15 per editor per month after trial. Unlimited viewers (AI answers are billed separately, priced per token — you only pay for what your team and viewers actually use).

## Links

- Sign up / app: https://app.library.guide
- How to use Library: https://www.library.guide/how-to-use.md
- MCP endpoint: https://mcp.library.guide/<your-workspace>
- Library plugin for Figma: https://www.figma.com/community/plugin/1539555100619791974/library-plugin-for-styles-variables-components