Skip to main content

ClawQL 7.0 setup guide

Requirements and upgrade steps for clawql-mcp 7.0.0 — npm, Docker, Helm, and the optional operator.

What changed

Area7.0.0
Default mergeCloudflare, GitHub, Slack, Linear, Notion, Onyx (provider: default)
Full bundleCLAWQL_PROVIDER=all-providers or helm --set provider=all-providers
SecretsVault-backed by default (requireVaultBackedSecrets: true)
Legacy envCLAWQL_* onlyAPI_BASE_URL, OPENAPI_SPEC_URL, google-top50 removed

npm / stdio

npx -p clawql-mcp clawql onboard --interactive
npx -p clawql-mcp clawql doctor --smoke

Helm

provider: default # chart default — matches npm
envFromSecret: clawql-provider-env
secretSourcing:
  requireVaultBackedSecrets: true

Full IDP lab: --set provider=all-providers or values-idp-full.yaml.

Populate HashiCorp KV secret/clawql/providers and sync to clawql-provider-env before expecting Ready pods. Lab opt-out: requireVaultBackedSecrets: false (not for production).

Operator auth reconciliation

When using ClawQLInstance, the operator sets ProviderSecretsReady:

  • documents.enabled: false — default-stack vault keys only
  • documents.enabled: true — default stack + all IDP provider keys
clawql operator status

Upgrade checklist

  1. Migration guide
  2. Replace legacy env aliases
  3. Wire Vault → clawql-provider-env
  4. helm upgrade with default or all-providers
  5. Confirm ProviderSecretsReady=True if using the operator