waxmcp

waxmcp is an npm launcher for the Wax MCP server.

Usage

npx -y waxmcp@latest mcp serve

For Claude Code / Codex installs, prefer:

npx -y waxmcp@latest mcp install --scope user

That install flow stages the bundled runtime into a stable local directory and registers the staged wax-mcp binary, so regular MCP sessions do not keep launching through raw npx.

Note: waxmcp currently supports Apple Silicon macOS only (darwin-arm64).

To publish a new version:

cd /path/to/Wax/Resources/npm/waxmcp
npm version patch   # or minor/major/1.2.3 (requires npm publish access)
npm publish --access public

This repo also ships a release script that updates version, syncs Sources/WaxMCPServer/main.swift's serverVersion, and rebuilds the Darwin binaries and resource bundles:

cd /path/to/Wax
./scripts/release-waxmcp.sh 0.1.18
git add Resources/npm/waxmcp/package.json Sources/WaxMCPServer/main.swift Resources/npm/waxmcp/dist
git commit -m "release: bump waxmcp version"

package.json and Sources/WaxMCPServer/main.swift are required to stay in lockstep; the release workflow checks this before publishing.

Artifacts are packaged with wax-cli.sha256 and wax-mcp.sha256 checksums generated by the release scripts for each platform binary.

MCP mode (default)

When invoked with no arguments or with mcp serve, the launcher directly invokes the wax-mcp binary using this search order:

1. $WAX_MCP_BIN
2. Bundled dist/darwin-arm64/wax-mcp or dist/darwin-x64/wax-mcp
3. wax-mcp in PATH
4. ./.build/debug/wax-mcp (current working directory)

CLI mode

For all other subcommands (remember, recall, search, etc.), the launcher invokes the wax-cli binary using this search order:

1. $WAX_CLI_BIN
2. Bundled dist/darwin-arm64/wax-cli or dist/darwin-x64/wax-cli
3. wax-cli in PATH
4. ./.build/debug/wax-cli (current working directory)

Vector-capable CLI commands now auto-start and reuse a background daemon by default, so coding agents can keep calling normal wax-cli/waxmcp commands without learning a separate workflow.

You can still run the daemon directly when you want an explicit long-lived session:

waxmcp daemon --store-path ~/.wax/memory.wax

The daemon keeps one MemoryOrchestrator open, so repeated remember / search / recall requests do not reload the CoreML embedder every time. Simple text-only usage still runs one-shot. Hybrid/vector searches now fail explicitly if vector search is unavailable instead of silently degrading to text-only mode.

Local development

cd /path/to/Wax
swift build --product wax-cli --traits MCPServer
swift build --product wax-mcp --traits MCPServer
export WAX_CLI_BIN=/path/to/Wax/.build/debug/wax-cli
npx --yes ./npm/waxmcp mcp doctor