Migration guide

Upgrade paths for ClawQL MCP server versions and teams moving from ad-hoc MCP integrations.

Detailed Tier 1 upgrade steps live in the Deployment & Operations Guide §1.7. This page covers cross-version and cross-platform moves.

Upgrading clawql-mcp

Check GitHub Releases for breaking changes
Update CLAWQL_* env vars if provider or feature-tier defaults changed — Configuration reference
For Kubernetes/Helm: bump image digest in values, run helm upgrade, verify /healthz
Re-run smoke tests: search on a known operation, execute dry path, vault memory_recall if enabled

From	To ClawQL
Raw OpenAPI in context	`search` + `execute` — specs stay on disk
Single-vendor MCP	`CLAWQL_PROVIDER=all-providers` or narrow preset
Custom tool servers	Proxy via gateway or migrate to `execute` operations
No vault memory	Enable `memory_ingest` / `memory_recall` with Obsidian vault path