chore(distribution): Remove Smithery integration and references

Remove Smithery from build scripts, release workflow, package metadata,\nand source entrypoints.\n\nDelete Smithery-specific docs and update remaining docs and tests to\nreflect the supported distribution paths without Smithery artifacts.

Co-Authored-By: Claude <noreply@anthropic.com>

Author: cameroncooke

.github/workflows/release.yml

@@ -50,7 +50,7 @@ jobs:
       - name: Bundle AXe artifacts
         run: npm run bundle:axe
 
-      - name: Build Smithery bundle
+      - name: Build package
         run: npm run build
 
       - name: Run tests
@@ -119,18 +119,6 @@ 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'
-        continue-on-error: true
-        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/TROUBLESHOOTING.md

@@ -27,7 +27,7 @@ It reports on:
 
 ### UI automation reports missing AXe
 UI automation (describe/tap/swipe/type) and simulator video capture require the AXe binary. If you see a missing AXe error:
-- Ensure `bundled/` artifacts exist when installing from Smithery or npm.
+- Ensure `bundled/` artifacts exist in your installation.
 - Or set `XCODEBUILDMCP_AXE_PATH` to a known AXe binary path (preferred), or `AXE_PATH`.
 - Re-run the doctor tool to confirm AXe is detected.
 

docs/dev/ARCHITECTURE.md

@@ -486,10 +486,6 @@ describe('Tool Name', () => {
    └── *.js.map         # Source maps
    ```
 
-### Smithery entrypoint
-
-Smithery deployments build from source using the Smithery CLI. The CLI discovers the TypeScript entrypoint from `package.json#module`, so this repository intentionally points `module` to `src/smithery.ts`. The npm runtime entrypoint is defined by `exports` and targets the compiled `build/` output.
-
 ### npm Package
 
 - **Name**: `xcodebuildmcp`

docs/dev/CLI_CONVERSION_PLAN.md

@@ -887,7 +887,7 @@ xcodebuildcli build-sim --help
 ## Invariants
 
 1. **MCP unchanged**: `xcodebuildmcp` continues to work exactly as before
-2. **Smithery unchanged**: `src/smithery.ts` continues to work
+2. **Build/runtime separation unchanged**: MCP and CLI continue to use shared tool handlers
 3. **No code duplication**: CLI invokes same `PluginMeta.handler` functions
 4. **Session defaults identical**: All runtimes use `bootstrapRuntime()` → `sessionStore`
 5. **Tool logic shared**: `src/mcp/tools/*` remains single source of truth

docs/dev/PROJECT_CONFIG_PLAN.md

@@ -62,7 +62,7 @@ Notes:
 
 ## Precedence (Operational)
 Runtime config precedence for all non-session defaults:
-1. Programmatic overrides (e.g., Smithery config)
+1. Programmatic overrides
 2. Config file (`.xcodebuildmcp/config.yaml`)
 3. Environment variables
 4. Hardcoded defaults
@@ -117,9 +117,9 @@ Responsibilities:
 - Persist session defaults through config store API.
 - Keep `deleteKeys` for mutual exclusivity.
 
-### 7) Smithery overrides
-**File:** `src/smithery.ts`
-- Pass overrides into bootstrap/config store, so Smithery has highest precedence.
+### 7) Runtime overrides
+**File:** runtime entrypoints
+- Pass overrides into bootstrap/config store, so explicit runtime overrides have highest precedence.
 
 ### 8) Documentation updates
 - Update `docs/CONFIGURATION.md`, `docs/GETTING_STARTED.md`, `docs/SESSION_DEFAULTS.md`.

docs/dev/README.md

@@ -9,7 +9,6 @@
 ## Build and tooling
 - [ESLint and type safety](ESLINT_TYPE_SAFETY.md)
 - [Node.js and runtime notes](NODEJS_2025.md)
-- [Smithery integration notes](SMITHERY.md)
 
 ## Release and maintenance
 - [Release process](RELEASE_PROCESS.md)

docs/dev/RELEASE_PROCESS.md

@@ -29,7 +29,7 @@ Production release behavior:
 - Builds and verifies portable macOS artifacts (`arm64`, `x64`, `universal`).
 - Uploads portable artifacts to GitHub release assets.
 - Updates the Homebrew tap repository (`cameroncooke/homebrew-xcodebuildmcp`) directly when `HOMEBREW_TAP_TOKEN` is configured.
-- Attempts Smithery and MCP Registry publishes (best effort based on configured secrets).
+- Attempts MCP Registry publish (best effort based on configured secrets).
 
 ### Manual dispatch (`workflow_dispatch`)
 
@@ -41,7 +41,7 @@ Validation behavior only (no production deployment):
 - Does **not** create GitHub release.
 - Does **not** upload portable assets to a release.
 - Does **not** update Homebrew tap.
-- Does **not** run Smithery or MCP Registry publish jobs.
+- Does **not** run MCP Registry publish job.
 
 ## Step-by-Step Development Workflow