@atomixstudio/mcp 1.0.35 → 1.0.37

package/README.md

@@ -2,7 +2,7 @@
 
 MCP (Model Context Protocol) server and CLI for Atomix Design System. Query and sync design tokens from AI coding tools (Cursor, Claude Desktop, Windsurf, etc.) or from the command line.
 
-**Version:** 1.0.28 — Sync to Figma: removes variables/styles not in payload (same collections only); color scopes (Bg = frame fill only, Action/Feedback = all fill); update-or-create for paint/text/effect styles to avoid duplicates; change summary in sync response; instructions AI-tool agnostic.
+**Version:** 1.0.36 — MCP exposes token/query tools and **syncAll** (writes `.cursor/skills/atomix-ds/SKILL.md` and `atomix-dependencies.json`). Figma push/design-in-Figma are not part of this package; use Atomix Studio and the Figma plugin for in-Figma workflows.
 
 ## Getting Your Credentials
 
@@ -62,12 +62,11 @@ Once connected, the AI can call these tools:
 | `listTokens(category)` | List all tokens in a category |
 | `searchTokens(query)` | Search tokens by name or value |
 | `validateUsage(value)` | Check if a hardcoded value should use a token |
-| `syncAll(options?)` | Sync tokens, AI rules, skills (.cursor/skills/atomix-ds/*), and atomix-dependencies.json. One tool for full project sync. **/--sync** invokes this. Optional: `workspaceRoot` (project root so files are written in the repo; else `ATOMIX_PROJECT_ROOT` env or cwd), `output` (default ./tokens.css), `format` (default css), `skipTokens` (if true, only skills + manifest). |
+| `syncAll(options?)` | Sync tokens, AI rules, `.cursor/skills/atomix-ds/SKILL.md`, and atomix-dependencies.json. One tool for full project sync. **/--sync** invokes this. Optional: `workspaceRoot` (project root so files are written in the repo; else `ATOMIX_PROJECT_ROOT` env or cwd), `output` (default ./tokens.css), `format` (default css), `skipTokens` (if true, only skill + manifest). |
 | `getRules(topic?)` | Get design system governance rules; optional topic: colors, typo, motion, icons, layout, visual |
 | `exportMCPConfig(tool)` | Get MCP configuration for different tools |
 | `getSetupInstructions(tool)` | Get detailed setup guide |
 | `getDependencies(platform?, stack?)` | Get suggested dependencies (icons, fonts, SKILL.md, token files). Optional: `platform` (web, ios, android), `stack` (e.g. react, vue, next). Use with **/--get-started** prompt. |
-| `syncToFigma()` | Push design system to Figma (variables, paint styles, text styles, effect styles). Uses built-in bridge + Atomix plugin. If the plugin is not connected, the response includes `agentInstruction` to connect. **Available on all tiers (Free and Pro).** |
 
 ### getDependencies
 
@@ -80,7 +79,6 @@ Returns DS-derived suggestions so the AI can build a "Suggested" vs "Already pre
 - **iconLibrary** — `package`, `nativePackage`, and a performance hint (use individual imports; apply the DS icon sizing/weight token when rendering icons).
 - **fonts** — Font family names from typography tokens + hint to link fonts via URL (e.g. Google Fonts); no need to download or add font files to the repo.
 - **skill** — `path` (e.g. `.cursor/skills/atomix-ds/SKILL.md`) and `content` (generic, platform-agnostic SKILL.md).
-- **skillFigmaDesign** — `path` (`.cursor/skills/atomix-ds/figma-design-SKILL.md`) and `content` (Figma design skill: advisory and generative UI on the Figma canvas).
 - **tokenFiles** — e.g. `["tokens.css", "tokens.json"]` with copy instructions.
 - **meta** — `dsName`, `platform`, `stack`, `designSystemVersion`, `designSystemExportedAt`. Use `designSystemVersion` to compare with skill frontmatter `atomixDsVersion` and suggest **syncAll** when the design system is newer.
 
@@ -88,7 +86,7 @@ If the design system is unavailable, the tool may fail; the client should tell t
 
 ### syncAll
 
-**syncAll** is the single sync tool: tokens file, AI rules, skills (`.cursor/skills/atomix-ds/SKILL.md` and `.cursor/skills/atomix-ds/figma-design-SKILL.md`), and **atomix-dependencies.json**. The manifest records icon library, font families, and skill paths. The **/--sync** prompt invokes it. All paths are resolved under a project root so files are written **inside the repo** (committable). Project root is: `workspaceRoot` argument → `ATOMIX_PROJECT_ROOT` env → `process.cwd()`. Optional: `workspaceRoot` (absolute path to repo root), `output` (default `./tokens.css`), `format` (default `css`), `skipTokens` (if true, only writes skills and manifest).
+**syncAll** is the single sync tool: tokens file, AI rules, `.cursor/skills/atomix-ds/SKILL.md`, and **atomix-dependencies.json**. The manifest records icon library, font families, and the skill path. The **/--sync** prompt invokes it. All paths are resolved under a project root so files are written **inside the repo** (committable). Project root is: `workspaceRoot` argument → `ATOMIX_PROJECT_ROOT` env → `process.cwd()`. Optional: `workspaceRoot` (absolute path to repo root), `output` (default `./tokens.css`), `format` (default `css`), `skipTokens` (if true, only writes skills and manifest).
 
 **Skill versioning:** Synced skills get frontmatter `atomixDsVersion` and `atomixDsExportedAt` (from the design system at sync time). The manifest’s `skills.syncedAtVersion` matches. The AI can compare the skill’s `atomixDsVersion` to **getDependencies**’ `meta.designSystemVersion`; if the design system is newer, it can suggest running **syncAll** to update.
 
@@ -98,13 +96,11 @@ Run these prompts from your AI tool (e.g. **/--hello**, **/--get-started**):
 
 | Prompt | Description |
 |--------|-------------|
-| **/--hello** | Get started — overview, tokens, essential commands (including **/--sync-to-figma**). Run this first. |
+| **/--hello** | Get started — overview, tokens, and essential commands. Run this first. |
 | **/--get-started** | Get started with design system in project. Three phases; creates files only after you approve. |
 | **/--rules** | Governance rules for your AI tool (Cursor, Copilot, Windsurf, etc.). |
 | **/--sync** | Sync tokens, AI rules, skills files, and dependencies manifest (icons, fonts). Use **/--refactor** to migrate deprecated tokens. |
 | **/--refactor** | Migrate deprecated tokens in codebase. Run after **/--sync**. |
-| **/--sync-to-figma** | Push design system to Figma. Requires bridge + Atomix plugin; see [Sync to Figma](#sync-to-figma) below. **Available on all tiers (Free and Pro).** |
-| **/--design-in-figma** | Load the Figma design skill and use the **designInFigma** MCP tool to design UI in the connected Figma file (catalog, query, execute). **Pro only.** |
 
 ## --get-started (get started)
 
@@ -119,31 +115,7 @@ The **/--get-started** prompt suggests dependencies for your design system so yo
 5. **Optional: suggest global typeset** — If the project has no global styles that use the design system tokens, offer to build a full typeset (Display, Heading, body, caption) from the DS typography tokens via getToken/listTokens, including fontFamily, fontSize, fontWeight, lineHeight, letterSpacing—not just font imports.
 6. **Report what was created** — After any install/copy steps, list what was created or updated (e.g. "Installed: lucide-react. Added: .cursor/skills/atomix-ds/SKILL.md. Synced: tokens.css.").
 
-**SKILLs:** The get-started flow suggests adding two skills: `.cursor/skills/atomix-ds/SKILL.md` (generic, platform-agnostic; call `getRules` for governance rules) and `.cursor/skills/atomix-ds/figma-design-SKILL.md` (Figma design — advisory and generative UI). Run /--sync to write both skills; .rules files (e.g. .cursorrules) are no longer written.
-
-## Sync to Figma
-
-**/--sync-to-figma** (or the **syncToFigma** tool) pushes your design system into the open Figma file: color variables, paint styles, number variables (spacing, radius, borders, sizing, breakpoints), text styles, and shadow effect styles. The **Figma bridge runs inside this MCP server** (no separate process). You only need the Atomix Figma plugin and "Connect to Cursor" (no Figma REST API or token).
-
-**Tier:** Sync to Figma is available on **all tiers** (Free and Pro).
-
-**Flow:**
-
-1. **Plugin not connected?** The tool checks first. If the plugin is not connected, the response includes `bridgeNotRunning`, `agentInstruction`, and `userInstruction`. Ensure Cursor has this MCP server running, then in Figma run the Atomix plugin and click **Connect to Cursor**, then call **syncToFigma** again.
-2. **Only if that fails** should the user check MCP configuration and plugin connection manually.
-
-## Design in Figma
-
-**/--design-in-figma** (or the **designInFigma** tool) loads the Figma design skill into context and directs the AI to use the designInFigma MCP tool to create or edit UI in the connected Figma file. The prompt injects the full Figma design skill content and instructs the agent to call designInFigma with `action: "catalog"` first, then `"query"` (e.g. get_selection, get_design_screenshot) or `"execute"` (design steps).
-
-**Tier:** Design in Figma is **Pro only**. Free users do not see this prompt or the designInFigma tool in their MCP session.
-
-**User steps (when needed):**
-
-1. **Ensure MCP is running** — Cursor should have this MCP server configured and running (the bridge is built in; no separate bridge process).
-2. **Install and run the Atomix plugin** — In Figma: Open Plugins and run the Atomix plugin (Atomix Token Extractor). If it's not installed yet, install it from the Figma Community or your team's plugin library, then run it.
-3. **Connect** — In the plugin UI, tap **Connect to Cursor** and wait until the status shows "Connected".
-4. Run **Sync to Figma** again.
+**SKILL:** The get-started flow suggests `.cursor/skills/atomix-ds/SKILL.md` (generic, platform-agnostic; call `getRules` for governance rules). Run **/--sync** to write the skill via **syncAll**; .rules files (e.g. .cursorrules) are no longer written.
 
 ## Token Categories