vectorvesper 2.1.1 → 2.4.0

package/README.md

@@ -53,6 +53,37 @@ export default function Page() {
 }
 ```
 
+## MCP server — motion advice for your coding agent
+
+The same CLI runs as an [MCP](https://modelcontextprotocol.io) server, so Claude Code, Cursor, Copilot and friends can ask about motion before they write it.
+
+```bash
+npx vectorvesper mcp install
+```
+
+That configures every supported editor it finds. Restart the editor and run `npx vectorvesper mcp status` to confirm. No account or token is needed — the runtime, its contracts and the linter are free.
+
+**Why bother.** Bad motion code does not error. TypeScript passes, the build is green, and the page janks on a mid-range phone six weeks later with nothing connecting the two. An agent has no feedback signal for the one quality dimension that matters here, so this server gives it three:
+
+- **`plan_motion`** — describe what you are building and get told whether it needs a primitive **at all**, which ones, in what order, and when that advice would be wrong. It says "use CSS, not this" for a hover state, a fade on mount, a spinner or a one-time scroll reveal, because those are compositor features that cost no main-thread time. Roughly a fifth of its answers recommend the platform over this library.
+- **`get_hook` / `get_pattern` / `get_component`** — the contract, not the source. Does this need a client boundary, does it own the element's transform, what does it conflict with, which frame lane does it run in, and when should you not use it.
+- **`check_motion`** — a static linter for the failure class that ships silently: a private `requestAnimationFrame` loop outside the shared budget, a discarded unsubscribe, `setState` in a frame callback, layout read in the write lane, one transform with two owners, a `<Canvas>` prop that quietly overrules the adapter that set it, a WebGL scene with nothing watching for a lost context, motion with no reduced-motion guard.
+
+Prefer to wire it by hand? Add this to your client's MCP config:
+
+```json
+{
+  "mcpServers": {
+    "vectorvesper": {
+      "command": "npx",
+      "args": ["-y", "vectorvesper", "mcp"]
+    }
+  }
+}
+```
+
+Full setup notes and the per-client config paths: [vectorvesper.dev/docs/mcp](https://vectorvesper.dev/docs/mcp).
+
 ## CLI Command Reference
 
 | Command | Description |
@@ -63,6 +94,9 @@ export default function Page() {
 | `update [slug]` | Update installed components to the latest version |
 | `diff [slug]` | Check local files against registry updates |
 | `remove <slug>` | Safely remove a component's files from the project |
+| `mcp install [client]` | Configure the MCP server for your editor(s) |
+| `mcp status` | Check which clients are wired up |
+| `mcp` | Run the MCP server on stdio (what the editor invokes) |
 | `info` | Output workspace diagnostics for troubleshooting |
 
 Works out of the box with **npm, pnpm, yarn, and bun** by checking your lockfile.