Use Smithery fork and pre-pack bundled resources

Author: cameroncooke

.github/workflows/ci.yml

@@ -26,6 +26,9 @@ jobs:
     - name: Install dependencies
       run: npm ci
 
+    - name: Use forked Smithery CLI (stdio prepack)
+      run: npm install --no-save --no-package-lock @smithery/cli@github:cameroncooke/cli#stdio-prepack-hook
+
     - name: Bundle AXe artifacts
       run: npm run bundle:axe
 

.github/workflows/release.yml

@@ -42,6 +42,9 @@ jobs:
           rm -rf node_modules package-lock.json
           npm install --ignore-scripts
 
+      - name: Use forked Smithery CLI (stdio prepack)
+        run: npm install --no-save --no-package-lock @smithery/cli@github:cameroncooke/cli#stdio-prepack-hook
+
       - name: Check formatting
         run: npm run format:check
 
@@ -104,6 +107,17 @@ jobs:
           echo "📦 Publishing to NPM with tag: $NPM_TAG"
           npm publish --access public --tag "$NPM_TAG"
 
+      - name: Deploy to Smithery (production releases only)
+        if: github.event_name == 'push'
+        env:
+          SMITHERY_TOKEN: ${{ secrets.SMITHERY_TOKEN }}
+        run: |
+          if [ -z "$SMITHERY_TOKEN" ]; then
+            echo "Missing SMITHERY_TOKEN secret for Smithery deploy."
+            exit 1
+          fi
+          npx smithery deploy --transport stdio
+
       - name: Create GitHub Release (production releases only)
         if: github.event_name == 'push'
         uses: softprops/action-gh-release@v1

docs/dev/SMITHERY_PACKAGING_CONTEXT.md

@@ -0,0 +1,83 @@
+# Smithery stdio packaging: problem domain and handoff
+
+## Audience
+This document is for a new AI agent with no context about the prior investigation.
+
+## Original problem
+XcodeBuildMCP is a **local stdio** MCP server deployed via the Smithery CLI. The server depends on bundled non-code assets (e.g., `bundled/` with an `axe` binary and frameworks). When deploying with the Smithery CLI, the resulting `.mcpb` bundle **does not include** these bundled assets, so the installed server lacks required resources at runtime.
+
+## Key facts about the current Smithery CLI (v3.x)
+The Smithery CLI now builds and packs local stdio servers by:
+1) Building the stdio bundle into an output directory (default `.smithery/stdio`).
+2) Packing only that output directory into `server.mcpb` using `@anthropic-ai/mcpb`.
+3) Uploading the `server.mcpb` in `smithery deploy --transport stdio`.
+
+Important constraints:
+- The CLI **does not read `smithery.config.js`** or run any custom build hooks for asset staging.
+- The CLI only reads `smithery.yaml` for metadata (e.g., name/target), not for a prepack step.
+- The pack step includes only what is inside `.smithery/stdio`.
+
+## What we did
+1) Confirmed the repository uses `@smithery/cli` v3.x and targets a local stdio server.
+2) Verified that `smithery build --transport stdio` produces `.smithery/stdio/server.mcpb` **without** `bundled/`.
+3) Confirmed that the previous `smithery.config.js` copy approach is obsolete because the CLI no longer loads that config.
+4) Opened a Smithery CLI issue to request an official asset-staging hook:
+   - https://github.com/smithery-ai/cli/issues/524
+
+## How to reproduce the missing-assets behavior
+From the XcodeBuildMCP repo:
+1) `npx smithery build --transport stdio -o .smithery/stdio`
+2) `unzip -l .smithery/stdio/server.mcpb`
+   - The bundle contains the compiled entrypoint and manifests only.
+   - `bundled/` is missing.
+
+## Workaround (local validation only)
+This is **not** compatible with `smithery deploy`, but it proves the bundle can contain assets:
+1) Build the stdio bundle:
+   - `npx smithery build --transport stdio -o .smithery/stdio`
+2) Copy assets into the stdio output directory:
+   - `cp -R bundled .smithery/stdio/bundled`
+3) Temporarily replace `manifest.json` with `mcpb-manifest.json` for packing:
+   - `cp .smithery/stdio/manifest.json .smithery/stdio/manifest.payload.json`
+   - `cp .smithery/stdio/mcpb-manifest.json .smithery/stdio/manifest.json`
+4) Re-pack using the official `mcpb` CLI:
+   - `npx @anthropic-ai/mcpb pack .smithery/stdio .smithery/stdio/server.mcpb`
+5) Restore the original manifest:
+   - `mv .smithery/stdio/manifest.payload.json .smithery/stdio/manifest.json`
+
+Result: `server.mcpb` now contains `bundled/` and its frameworks.
+
+## Why the workaround cannot be used for deployment
+`smithery deploy --transport stdio` rebuilds and repacks in its own flow, and provides no prepack hook to stage assets. As a result, there is no official way to inject `bundled/` into the `.mcpb` during deploy.
+
+## How we likely want to proceed
+### Option A: Upstream fix (recommended)
+Add an official asset staging hook or prepack command in the Smithery CLI:
+- Example: `smithery.yaml` fields like `build.assets` or `build.prepackCommand`.
+- The hook should run before `packExtension()` in `src/lib/bundle/stdio.ts`.
+- This would allow asset copying into `.smithery/stdio` during `smithery deploy`.
+
+Issue to track:
+- https://github.com/smithery-ai/cli/issues/524
+
+### Option B: Fork the CLI
+If the upstream fix is slow, fork `smithery-ai/cli` and add:
+- A prepack hook (env var or `smithery.yaml` field).
+- A deterministic asset staging step inside `buildStdioBundle` before the pack step.
+Then consume the fork in CI:
+- Publish the fork under a scoped npm package, or
+- Install the fork from GitHub release in the release workflow.
+
+Current implementation (forked CLI):
+- Added `build.prepackCommand` support in `smithery.yaml` (plus env var overrides).
+- CI/release workflows install the forked CLI before `smithery build`.
+- This repo wires `smithery.yaml` to `scripts/smithery-prepack.sh` to bundle/copy assets.
+
+## Current repo state that matters
+- `smithery.config.js` exists but is **ignored** by v3.x CLI.
+  - Any asset copy logic in this file does not run in deploy.
+- Release workflow currently publishes npm and MCP registry, but **does not** run Smithery deploy.
+- `npm run build` uses Smithery’s default transport (shttp) unless explicit `--transport stdio` is used.
+
+## Summary
+The problem is not an outdated CLI version. The CLI is current, but the integration strategy is obsolete because v3.x no longer honors `smithery.config.js`. The deploy flow packs only `.smithery/stdio`. Until Smithery adds an official prepack/assets hook (or a fork is used), correct bundling for local stdio deployments is not achievable via `smithery deploy`.

package.json

@@ -15,7 +15,7 @@
     "xcodebuildmcp-doctor": "build/doctor-cli.js"
   },
   "scripts": {
-    "build": "npm run build:tsup && npx smithery build",
+    "build": "npm run build:tsup && npx smithery build --transport stdio",
     "dev": "npm run generate:version && npm run generate:loaders && npx smithery dev",
     "build:tsup": "npm run generate:version && npm run generate:loaders && tsup",
     "dev:tsup": "npm run build:tsup && tsup --watch",

scripts/smithery-prepack.sh

@@ -0,0 +1,33 @@
+#!/usr/bin/env bash
+
+set -euo pipefail
+
+SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+PROJECT_ROOT="$(dirname "$SCRIPT_DIR")"
+OUT_DIR="${SMITHERY_STDIO_OUT_DIR:-$PROJECT_ROOT/.smithery/stdio}"
+BUNDLED_DIR="$PROJECT_ROOT/bundled"
+DEST_DIR="$OUT_DIR/bundled"
+
+if [ ! -d "$OUT_DIR" ]; then
+  mkdir -p "$OUT_DIR"
+fi
+
+if [ ! -f "$BUNDLED_DIR/axe" ]; then
+  echo "Bundled AXe artifacts missing; running bundle:axe..."
+  npm run bundle:axe
+else
+  echo "Bundled AXe artifacts already present."
+fi
+
+if [ ! -f "$BUNDLED_DIR/axe" ]; then
+  echo "Bundled AXe artifacts are still missing after bundle:axe"
+  exit 1
+fi
+
+if [ -d "$DEST_DIR" ]; then
+  rm -r "$DEST_DIR"
+fi
+
+cp -R "$BUNDLED_DIR" "$OUT_DIR/"
+
+echo "Copied bundled artifacts to $DEST_DIR"

scripts/verify-smithery-bundle.sh

@@ -3,33 +3,44 @@
 set -euo pipefail
 
 PROJECT_ROOT="$(cd "$(dirname "${BASH_SOURCE[0]}")/.." && pwd)"
-BUNDLE_DIR="$PROJECT_ROOT/.smithery/bundled"
+SMITHERY_DIR="$PROJECT_ROOT/.smithery"
+STDIO_DIR="$SMITHERY_DIR/stdio"
+BUNDLE_DIR="$STDIO_DIR/bundled"
+
+if [ ! -f "$BUNDLE_DIR/axe" ]; then
+  echo "Missing bundled AXe artifacts under $STDIO_DIR"
+  if [ -d "$SMITHERY_DIR" ]; then
+    echo ".smithery contents:"
+    ls -la "$SMITHERY_DIR"
+  fi
+  exit 1
+fi
 AXE_BIN="$BUNDLE_DIR/axe"
 FRAMEWORK_DIR="$BUNDLE_DIR/Frameworks"
 
 if [ ! -f "$AXE_BIN" ]; then
-  echo "❌ Missing AXe binary at $AXE_BIN"
+  echo "Missing AXe binary at $AXE_BIN"
   if [ -d "$PROJECT_ROOT/.smithery" ]; then
-    echo "🔍 .smithery contents:"
+    echo ".smithery contents:"
     ls -la "$PROJECT_ROOT/.smithery"
   fi
   exit 1
 fi
 
 if [ ! -d "$FRAMEWORK_DIR" ]; then
-  echo "❌ Missing Frameworks directory at $FRAMEWORK_DIR"
+  echo "Missing Frameworks directory at $FRAMEWORK_DIR"
   if [ -d "$BUNDLE_DIR" ]; then
-    echo "🔍 bundled contents:"
+    echo "bundled contents:"
     ls -la "$BUNDLE_DIR"
   fi
   exit 1
 fi
 
 FRAMEWORK_COUNT="$(find "$FRAMEWORK_DIR" -maxdepth 2 -type d -name "*.framework" | wc -l | tr -d ' ')"
 if [ "$FRAMEWORK_COUNT" -eq 0 ]; then
-  echo "❌ No frameworks found in $FRAMEWORK_DIR"
+  echo "No frameworks found in $FRAMEWORK_DIR"
   find "$FRAMEWORK_DIR" -maxdepth 2 -type d | head -n 50
   exit 1
 fi
 
-echo "✅ Smithery bundle includes AXe binary and $FRAMEWORK_COUNT frameworks"
+echo "Smithery bundle includes AXe binary and $FRAMEWORK_COUNT frameworks"

smithery.config.js

@@ -1,3 +1,4 @@
-# Smithery configuration file: https://smithery.ai/docs/build/project-config
-runtime: "typescript"
-target: "local"
+runtime: typescript
+target: local
+build:
+  prepackCommand: "bash scripts/smithery-prepack.sh"

smithery.yaml

@@ -24,7 +24,7 @@ async function runDoctor(): Promise<void> {
     // Output the doctor information
     if (result.content && result.content.length > 0) {
       const textContent = result.content.find((item) => item.type === 'text');
-      if (textContent && textContent.type === 'text') {
+      if (textContent?.type === 'text') {
         // eslint-disable-next-line no-console
         console.log(textContent.text);
       } else {

src/doctor-cli.ts

@@ -29,7 +29,7 @@ export async function swift_package_buildLogic(
   const resolvedPath = path.resolve(params.packagePath);
   const swiftArgs = ['build', '--package-path', resolvedPath];
 
-  if (params.configuration && params.configuration.toLowerCase() === 'release') {
+  if (params.configuration?.toLowerCase() === 'release') {
     swiftArgs.push('-c', 'release');
   }