@flareum/mcp 0.2.4 → 0.2.6

package/README.md

@@ -177,6 +177,11 @@ area — `naming.md` for how a token name is built, `typography.md` for applying
 its class rather than the mixin behind it. The whole folder is rewritten every run, so do not edit
 it, and it prints where it wrote (or why it could not) on stderr.
 
+**`claude mcp add` alone does not write it.** An MCP server starts when a client first connects, so
+nothing runs until you open a session — or run `claude mcp list`, which connects to report status
+and is why the skill sometimes appears then. `flareum pull` writes it too, so one pull sets the
+project up without waiting for a connection.
+
 On the first connection it also **pulls the stylesheets**, once. It looks for the folder this project
 already keeps its styles in — `src/styles`, `app/styles`, `scss`, and the rest — and writes them to
 `<that folder>/flareum`, falling back to `styles/flareum` in a project that has none. It says on

package/dist/cli.js

@@ -6,6 +6,7 @@ import { FlareumApiError, FlareumClient } from './client.js';
 import { CONFIG_PATH, cliErrorReport, parseArgs, resolveConfig } from './config.js';
 import { chooseStylesDir, fileWriter } from './first-pull.js';
 import { isRetryable, pullReport, pullStyles } from './pull.js';
+import { installSkill, skillInstallReport } from './skill.js';
 import { watchIntervalMs, watchPublished, watchStartedReport } from './watch.js';
 // Where the styles go is decided in ONE place, so the CLI and the server never disagree about it.
 const defaultOut = () => chooseStylesDir(path => existsSync(resolve(process.cwd(), path)));
@@ -58,6 +59,9 @@ try {
     const outDir = config.out ?? defaultOut();
     const client = new FlareumClient({ token: config.token, api: config.api });
     const write = fileWriter(resolve(process.cwd(), outDir));
+    // The server writes the skill too, but only when a client connects — `claude mcp add` spawns
+    // nothing, so until now the rules arrived on whatever ran first, which was luck.
+    console.log(skillInstallReport(await installSkill(process.cwd())));
     const runPull = async () => {
         const result = await pullStyles(client, write);
         console.log(pullReport(result, outDir));

package/dist/server.js

@@ -9,11 +9,20 @@ import { FlareumApiError, FlareumClient } from './client.js';
 import { TOOL_DESCRIPTIONS, formatError, formatSearch, formatVariable } from './tools.js';
 import { installSkill, skillInstallReport } from './skill.js';
 import { configuredOut, firstPullReport, runFirstPull } from './first-pull.js';
-const client = new FlareumClient({
-    token: process.env.FLAREUM_TOKEN ?? '',
-    api: process.env.FLAREUM_API,
-    projectId: process.env.FLAREUM_PROJECT,
-});
+// A missing key threw at module load, and an editor shows that as a Node stack trace with the
+// message buried in it. Say it in one line and exit, the way the CLI already does.
+let client;
+try {
+    client = new FlareumClient({
+        token: process.env.FLAREUM_TOKEN ?? '',
+        api: process.env.FLAREUM_API,
+        projectId: process.env.FLAREUM_PROJECT,
+    });
+}
+catch (error) {
+    console.error(`[flareum] ${error instanceof Error ? error.message : String(error)}`);
+    process.exit(1);
+}
 // 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: {} } });

package/dist/skill.d.ts

@@ -7,5 +7,6 @@ export type SkillInstall = {
     reason: string;
 };
 export declare const installSkill: (cwd: string) => Promise<SkillInstall>;
+export declare const installSkillFrom: (source: string, cwd: string) => Promise<SkillInstall>;
 /** Reported on stderr — stdout carries the JSON-RPC stream and must never be written to. */
 export declare const skillInstallReport: (result: SkillInstall) => string;

package/dist/skill.js

@@ -1,3 +1,4 @@
+import { existsSync } from 'node:fs';
 import { mkdir, readdir, readFile, writeFile } from 'node:fs/promises';
 import { dirname, join } from 'node:path';
 import { fileURLToPath } from 'node:url';
@@ -14,11 +15,16 @@ const copyTree = async (from, to) => {
 };
 // Written on every start, not once: a stale copy of the rules is worse than none, and the files are
 // generated rather than hand-edited.
-export const installSkill = async (cwd) => {
-    const source = join(dirname(fileURLToPath(import.meta.url)), '..', 'skill');
+export const installSkill = (cwd) => installSkillFrom(join(dirname(fileURLToPath(import.meta.url)), '..', 'skill'), cwd);
+// The source is a parameter so the "wrote nothing" case can be driven, not just reasoned about.
+export const installSkillFrom = async (source, cwd) => {
     const path = join(cwd, ...SKILL_DIR, 'SKILL.md');
     try {
         await copyTree(source, join(cwd, ...SKILL_DIR));
+        // copyTree makes directories before it writes, so a source that carries none of the files still
+        // leaves a tree that LOOKS installed. Success is the router being on disk, not the walk ending.
+        if (!existsSync(path))
+            return { ok: false, path, reason: `nothing was written — no SKILL.md under ${source}` };
         return { ok: true, path };
     }
     catch (error) {

package/package.json

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