@flareum/mcp 0.2.1 → 0.2.2

package/README.md

@@ -13,7 +13,7 @@ typing literal values.
 2. Copy the command it shows you. It looks like this:
 
 ```bash
-claude mcp add flareum --env FLAREUM_TOKEN=pk_… -- npx -y @flareum/mcp
+claude mcp add flareum --env FLAREUM_TOKEN=pk_… -- npx -y -p @flareum/mcp flareum-mcp
 ```
 
 3. Run it in **your project's** terminal — the repo where you write CSS/SCSS, not the Flareum repo.
@@ -29,7 +29,7 @@ The key is shown once and cannot be retrieved again. If you lose it, revoke it a
 the newest:
 
 ```bash
-npx -y @flareum/mcp@latest --help
+npx -y -p @flareum/mcp@latest flareum --help
 ```
 
 Naming `@latest` is what refreshes the cache. Then restart your editor session — a running MCP
@@ -39,7 +39,7 @@ Check which version you are actually on:
 
 ```bash
 npm view @flareum/mcp version   # the newest published
-npx -y @flareum/mcp@latest --version
+npx -y -p @flareum/mcp@latest flareum --version
 ```
 
 If you installed it globally instead of through `npx`:
@@ -80,8 +80,8 @@ The tools tell an agent what a token is CALLED. The stylesheets that give those
 from a Push, and this fetches them:
 
 ```bash
-npx flareum pull                 # into src/styles/flareum
-npx flareum watch                # and again every time you Push in Flareum
+npx -y -p @flareum/mcp flareum pull    # into src/styles/flareum
+npx -y -p @flareum/mcp flareum watch   # and again every time you Push in Flareum
 ```
 
 Then import them once, in your global stylesheet:
@@ -126,7 +126,7 @@ and it prints where it wrote (or why it could not) on stderr.
 
 | What you see | Cause |
 |---|---|
-| The server fails to connect / closes immediately | The package is not installed. Check `npx -y @flareum/mcp` resolves — if it 404s, it has not been published yet. |
+| The server fails to connect / closes immediately | The package is not installed. Check `npx -y -p @flareum/mcp flareum-mcp` resolves — if it 404s, it has not been published yet. |
 | A command the docs describe is not recognised | `npx` is running a cached older copy. Re-run it as `@latest` — see Updating. |
 | The agent types literal values anyway | The skill did not land. Look for `[flareum] skill written to …` in the MCP server's stderr. |
 | Values labelled with long ids instead of mode names | The Flareum server is older than the client. Restart it. |

package/dist/server.js

@@ -1,6 +1,7 @@
 #!/usr/bin/env node
 // Transport glue only. Every behaviour worth guarding lives in client.ts and tools.ts, which have
 // no SDK dependency and are tested without one.
+import { readFileSync } from 'node:fs';
 import { Server } from '@modelcontextprotocol/sdk/server/index.js';
 import { StdioServerTransport } from '@modelcontextprotocol/sdk/server/stdio.js';
 import { CallToolRequestSchema, ListToolsRequestSchema } from '@modelcontextprotocol/sdk/types.js';
@@ -12,7 +13,9 @@ const client = new FlareumClient({
     api: process.env.FLAREUM_API,
     projectId: process.env.FLAREUM_PROJECT,
 });
-const server = new Server({ name: 'flareum', version: '0.1.0' }, { capabilities: { tools: {} } });
+// Read, never restated: the hardcoded 0.1.0 kept reporting itself from a 0.2.1 package.
+const { version } = JSON.parse(readFileSync(new URL('../package.json', import.meta.url), 'utf8'));
+const server = new Server({ name: 'flareum', version }, { capabilities: { tools: {} } });
 server.setRequestHandler(ListToolsRequestSchema, async () => ({
     tools: [
         {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@flareum/mcp",
-  "version": "0.2.1",
+  "version": "0.2.2",
   "description": "Connect a coding agent to a Flareum project's design tokens.",
   "license": "MIT",
   "author": "Flareum",