@actioneer/ads-mcp 0.1.0 → 0.2.1

package/README.md

@@ -39,8 +39,11 @@ All five tools read the L1 catalog (`ads-manifest.json`).
 }
 ```
 
-`ads-mcp` resolves the catalog from the installed `@actioneer/ads/manifest.json`
-automatically. Override with `ADS_MANIFEST`:
+`ads-mcp` is **self-contained**: it ships a bundled catalog snapshot, so
+`npx -y @actioneer/ads-mcp` works standalone with nothing else installed. When
+`@actioneer/ads` *is* installed alongside it, the server prefers that package's
+`manifest.json` so the catalog matches the exact version you import. Override
+either with `ADS_MANIFEST`:
 
 ```json
 {
@@ -65,8 +68,9 @@ generated repo-root `ads-manifest.json`). A ready-to-copy example lives at
 ## Manifest resolution order
 
 1. `$ADS_MANIFEST` (explicit path)
-2. `@actioneer/ads/manifest.json` (the installed package's catalog)
-3. `<repo>/ads-manifest.json` (local dev — generated by `npm run build:lib` / `prebuild`)
+2. `@actioneer/ads/manifest.json` (the consumer's installed ADS version — exact match)
+3. `<this package>/manifest.json` (the snapshot bundled at publish — the self-contained fallback that makes `npx` work with no ADS installed)
+4. `<repo>/ads-manifest.json` (local dev — generated by `npm run manifest` / `prebuild`)
 
 ## Development
 

package/bin/ads-mcp.mjs

@@ -2,9 +2,14 @@
 // ADS MCP server entry — loads the ADS manifest and starts the stdio server.
 //
 // Manifest resolution order (first hit wins):
-//   1. $ADS_MANIFEST                              (explicit path override)
-//   2. @actioneer/ads/manifest.json              (the installed package's catalog)
-//   3. <repo>/ads-manifest.json                  (local dev, generated by build)
+//   1. $ADS_MANIFEST                     (explicit path override)
+//   2. @actioneer/ads/manifest.json      (the consumer's installed ADS version —
+//                                          preferred, so the catalog matches what
+//                                          they actually import)
+//   3. <this package>/manifest.json      (the snapshot BUNDLED at publish time —
+//                                          makes `npx @actioneer/ads-mcp` work
+//                                          standalone, with no ADS installed)
+//   4. <repo>/ads-manifest.json          (monorepo dev, generated by the build)
 //
 // Wire it into Claude Code / Cursor via .mcp.json (see tools/ads-mcp/README.md).
 
@@ -18,12 +23,19 @@ const __dirname = dirname(fileURLToPath(import.meta.url));
 const require = createRequire(import.meta.url);
 
 function resolveManifestPath() {
+  // 1. Explicit override.
   if (process.env.ADS_MANIFEST && existsSync(process.env.ADS_MANIFEST)) return process.env.ADS_MANIFEST;
+  // 2. The consumer's installed @actioneer/ads (best-effort; it's an optional peer).
   try {
     return require.resolve("@actioneer/ads/manifest.json");
   } catch {
-    /* not installed as a package — fall through to repo dev copy */
+    /* not resolvable from here — fall through */
   }
+  // 3. The snapshot bundled INTO this package by `prepack` — the self-contained
+  //    fallback that guarantees a published install always has a catalog.
+  const bundled = resolve(__dirname, "../manifest.json");
+  if (existsSync(bundled)) return bundled;
+  // 4. Monorepo dev copy (generated at the repo root by `npm run manifest`).
   const repoCopy = resolve(__dirname, "../../../ads-manifest.json");
   if (existsSync(repoCopy)) return repoCopy;
   return null;
@@ -32,8 +44,8 @@ function resolveManifestPath() {
 const manifestPath = resolveManifestPath();
 if (!manifestPath) {
   console.error(
-    "ads-mcp: could not find ads-manifest.json. Set $ADS_MANIFEST, install @actioneer/ads, " +
-      "or run the build so ads-manifest.json exists at the repo root."
+    "ads-mcp: could not find a manifest. This should not happen in a published install " +
+      "(one ships bundled). For local dev, set $ADS_MANIFEST or run `npm run manifest` at the repo root."
   );
   process.exit(1);
 }