@manudota/artist-mcp 1.5.2-staging.72 → 1.5.2

package/dist/calendar.js

@@ -374,6 +374,20 @@ const draftFrom = (params) => {
     if (new Date(end).getTime() < new Date(start).getTime()) {
         throw failure('The event ends before it starts.');
     }
+    // Equal ends are the subtler half, and they differ by kind.
+    //
+    // Google treats an all-day `end.date` as exclusive: a gig on the 11th ends on
+    // the 12th. `end` equal to `start` is an empty range, which Google refuses —
+    // and a model that does not know the convention writes it without hesitating.
+    // A timed event of zero length is not a gig either. Refused here rather than
+    // surfacing as a Google 400 that says nothing about what to do.
+    if (end === start) {
+        throw failure(allDay
+            ? `An all-day event ends on the following day: Google reads the end date as ` +
+                `exclusive, so a single day on ${start} is start ${start}, end ` +
+                `${new Date(new Date(start).getTime() + 86_400_000).toISOString().slice(0, 10)}.`
+            : 'The event starts and ends at the same moment. Give it a duration.');
+    }
     return {
         calendar_id: calendarId,
         summary: text(params.summary, 'summary', true),

package/dist/config.d.ts

@@ -6,6 +6,22 @@ export declare const ENTRY_NAME = "artist-notes";
  * that read this file except against the developer's own Claude Desktop config,
  * which a test suite has no business touching.
  */
+/**
+ * Where Claude Desktop keeps its config on Windows, which is not one place.
+ *
+ * A packaged install — the one that appears under `AppData\Local\Packages` —
+ * has a **virtualised** `%APPDATA%`. Desktop reads
+ * `…\Packages\Claude_<id>\LocalCache\Roaming\Claude\`, while this process
+ * is an ordinary Node program whose `%APPDATA%` is the real `Roaming` folder.
+ * Writing to the obvious path therefore produced two config files that were
+ * each internally consistent and never the same one: `init` and `status` agreed
+ * with each other about a grant that Claude Desktop had never seen.
+ *
+ * Found the hard way, and the symptom is maddening — every check passes and the
+ * tools do not appear — so the packaged location wins when it exists rather
+ * than being offered as a fallback.
+ */
+export declare const windowsConfigPath: (home: string) => string;
 export declare const configPath: () => string;
 type Config = {
     mcpServers?: Record<string, unknown>;

package/dist/config.js

@@ -1,6 +1,7 @@
 /** Locating and editing the Claude Desktop config, without trampling it. */
 import { homedir, platform } from "node:os";
 import { join } from "node:path";
+import { existsSync, readdirSync } from "node:fs";
 import { mkdir, readFile, writeFile } from "node:fs/promises";
 import { dirname } from "node:path";
 export const ENTRY_NAME = "artist-notes";
@@ -10,6 +11,45 @@ export const ENTRY_NAME = "artist-notes";
  * that read this file except against the developer's own Claude Desktop config,
  * which a test suite has no business touching.
  */
+/**
+ * Where Claude Desktop keeps its config on Windows, which is not one place.
+ *
+ * A packaged install — the one that appears under `AppData\Local\Packages` —
+ * has a **virtualised** `%APPDATA%`. Desktop reads
+ * `…\Packages\Claude_<id>\LocalCache\Roaming\Claude\`, while this process
+ * is an ordinary Node program whose `%APPDATA%` is the real `Roaming` folder.
+ * Writing to the obvious path therefore produced two config files that were
+ * each internally consistent and never the same one: `init` and `status` agreed
+ * with each other about a grant that Claude Desktop had never seen.
+ *
+ * Found the hard way, and the symptom is maddening — every check passes and the
+ * tools do not appear — so the packaged location wins when it exists rather
+ * than being offered as a fallback.
+ */
+export const windowsConfigPath = (home) => {
+    const roaming = process.env.APPDATA ?? join(home, "AppData", "Roaming");
+    const plain = join(roaming, "Claude", "claude_desktop_config.json");
+    const packagesRoot = process.env.LOCALAPPDATA ?? join(home, "AppData", "Local");
+    try {
+        const packages = readdirSync(join(packagesRoot, "Packages"))
+            .filter((name) => /^Claude_/i.test(name))
+            .map((name) => join(packagesRoot, "Packages", name, "LocalCache", "Roaming", "Claude", "claude_desktop_config.json"));
+        // An existing packaged config is the one Desktop reads. If more than one
+        // package directory exists, prefer one that already holds a config over an
+        // empty shell left by an uninstall.
+        const written = packages.find((candidate) => existsSync(candidate));
+        if (written)
+            return written;
+        // A packaged install with no config yet: still the right place to write,
+        // since the plain path would be ignored.
+        if (packages.length > 0 && !existsSync(plain))
+            return packages[0];
+    }
+    catch {
+        // No Packages directory at all — an ordinary install. Fall through.
+    }
+    return plain;
+};
 export const configPath = () => {
     const override = process.env.ARTIST_MCP_CONFIG;
     if (override)
@@ -19,7 +59,7 @@ export const configPath = () => {
         case "darwin":
             return join(home, "Library", "Application Support", "Claude", "claude_desktop_config.json");
         case "win32":
-            return join(process.env.APPDATA ?? join(home, "AppData", "Roaming"), "Claude", "claude_desktop_config.json");
+            return windowsConfigPath(home);
         default:
             // Claude Desktop ships on macOS and Windows only; this keeps the error
             // legible rather than writing a config nothing will ever read.

package/dist/init.js

@@ -2,6 +2,7 @@ import { resolve } from "node:path";
 import { fileURLToPath } from "node:url";
 import { DEFAULT_EDITABLE_DIRECTORY, describeSeed, seedEditablePack } from "./agents.js";
 import { isStagingVersion, packageVersion } from "./client.js";
+import { sep } from "node:path";
 import { configPath, ENTRY_NAME, readConfig, writeConfig } from "./config.js";
 import { connectedProviders } from "./dispatch.js";
 import { describeGrants, setGrants } from "./grants.js";
@@ -65,6 +66,12 @@ export const runInit = async ({ local = false, editableDir, grants = [], } = {})
     config.mcpServers = servers;
     await writeConfig(path, config);
     console.log(`\nWrote "${ENTRY_NAME}" to ${path}`);
+    if (path.includes(`${sep}Packages${sep}`)) {
+        // Worth naming. A packaged Windows install virtualises %APPDATA%, so the
+        // obvious path is a different file that Claude Desktop never opens — and
+        // writing there fails invisibly: every check passes and no tool appears.
+        console.log("           (packaged Claude install — this is the config it reads)");
+    }
     if (seeded) {
         console.log("");
         describeSeed(seeded);

package/dist/server.js

@@ -103,7 +103,7 @@ const selectNotebook = async (call, notebook, tool) => {
         : null;
     return { pages, scope };
 };
-const serverVersion = '1.5.2-staging.72'; // x-release-please-version
+const serverVersion = '1.5.2'; // x-release-please-version
 const errorResult = (err) => {
     const message = err instanceof GraphError ? err.message : `Unexpected error: ${err}`;
     return { content: [{ type: "text", text: message }], isError: true };
@@ -809,7 +809,11 @@ const createServer = async (call) => {
             start: z
                 .string()
                 .describe("YYYY-MM-DD for an all-day event, or an RFC3339 date-time such as 2026-10-16T20:00:00"),
-            end: z.string().describe("The same kind as start: both dates, or both date-times"),
+            end: z
+                .string()
+                .describe("The same kind as start: both dates, or both date-times. For an all-day " +
+                "event Google reads this as EXCLUSIVE, so a gig on 2028-09-11 is " +
+                "start 2028-09-11, end 2028-09-12"),
             time_zone: z
                 .string()
                 .optional()
@@ -870,7 +874,10 @@ const createServer = async (call) => {
             source_page: z
                 .string()
                 .optional()
-                .describe("The OneNote page this came from, recorded locally so the write can be traced back"),
+                .describe("The page id from list_notes or read_note, so the write can be traced back " +
+                "weeks later. The id, not the title: a notebook can hold two pages with " +
+                "the same or nearly the same name, which is exactly when tracing matters. " +
+                "Add the title after it if you like"),
         }, async (params) => {
             try {
                 const { created, link, calendar_id, written } = await call("create_calendar_event", params);
@@ -936,7 +943,8 @@ const createServer = async (call) => {
             source_page: z
                 .string()
                 .optional()
-                .describe("The OneNote page this relates to, recorded locally"),
+                .describe("The page id from list_notes or read_note, not the title — a title does not " +
+                "identify a page in a notebook holding near-duplicates"),
         }, async (params) => {
             try {
                 const { deleted, calendar_id } = await call("delete_calendar_event", params);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@manudota/artist-mcp",
-  "version": "1.5.2-staging.72",
+  "version": "1.5.2",
   "description": "MCP server that reads your OneNote notes, with optional Gmail and Calendar as supporting evidence, via a hosted connection.",
   "repository": {
     "type": "git",