What is Syntope?
Syntope is built around Syntope Engine, a headless engine for design tokens on the open DTCG standard. The engine validates tokens, resolves references, composes themes, and reads and writes DTCG files. It is a library, not a running service. Everything else in Syntope is a way to use it.
Early beta. Interfaces and file metadata can still change between versions.
Ways to use the engine
| Surface | For | Status |
|---|---|---|
| Syntope Tokens | Designers in Figma. A plugin to author every DTCG type, build themes, apply tokens to layers and link a Git repository. | Stable |
| Syntope MCP | AI apps: Codex, Claude Code, Cursor and Claude Desktop. A Mac app (macOS 13.5 or later) that reaches the plugin through Syntope Bridge, a local connection. Needs Figma Desktop with the plugin open. | Stable |
| Syntope Engine in your code | Developers building their own tools and pipelines. Built from source, not on npm yet. | Partial |
| Syntope CLI | Developers and CI. | Planned |
A mode of Syntope MCP that works on token files without Figma is also planned.
Where your tokens live
Your Git repository is the source of truth. Link GitHub, GitLab or Bitbucket Cloud and the plugin pulls and pushes the complete project as DTCG files. No Syntope server sits between the plugin and your Git host: the plugin’s manifest allows network access only to api.github.com, gitlab.com, api.bitbucket.org and the local connection you pair yourself.
The Figma file holds a working copy. The plugin saves the whole project as private plugin data on the Figma document, one project per file. Until you link a repository, that copy is the only one and the plugin footer shows local. Sync covers linking.
Figma is a consumer, not the owner. Designers author every DTCG type in the plugin. Tokens are then applied to layers or mapped to Figma variables, in one direction: from tokens to variables. See Figma variables.
Figma variables and styles are not a source. Nothing flows back from Figma. To start from existing values, author the tokens in the plugin, or bring them in as DTCG files or a Tokens Studio export. See Import and export.
Files stay valid DTCG 2025.10, and themes follow the DTCG Resolver. What the specification cannot express goes into $extensions.
Who it is for
| You are | Start with |
|---|---|
| A designer working on a design system | Syntope Tokens: typed tokens, themes and bindings to layers |
| A developer consuming tokens | The DTCG files in your repository. Any tool that reads DTCG can use them |
| A developer building token tooling | Syntope Engine in your code |
| Working with an AI app | Syntope MCP: read tokens, change them and apply them to layers in plain words |
What it does not do yet
Merge on sync. A pull replaces the whole project in the file, after a review of what changes. A push replaces the project in the repository. If the repository holds a project you have not pulled, the plugin asks first. Do instead: pull and review before you push. See Sync.
Generate build output. Syntope writes DTCG files, not CSS, JavaScript or platform code. Do instead: pass the files to a build tool that reads DTCG, or read resolved values with the engine.
Work from a command line, or through Syntope MCP without Figma. Both are planned. Do instead: script against the engine.
Run Syntope MCP outside macOS. Windows is not supported yet. Do instead: work in the plugin directly.
Reach a self-hosted Git server. The manifest allows only the three hosted services above. Do instead: export the project and commit the files yourself.
The complete list is on Known limitations.
Next steps
- Getting started: a first result in Figma, with an AI app or in your own code
- Core concepts: token sets, themes, references and bindings
- Token types: every type and its value format