Agent setup

Vault-first onboarding: one home for memory, provider secrets, and MCP wiring — better than pasting API keys into client config.

Run clawql init before connecting Cursor. Secrets live in ~/.ClawQL/vault/providers.json (same shape as HashiCorp secret/clawql/providers). Memory tools use ~/.ClawQL/Memory/. Default install loads the opinionated stack (Cloudflare, GitHub, Slack, Linear, Notion, Onyx). Use CLAWQL_PROVIDER=all-providers only for every bundled vendor plus Google top-50 and AWS top-50.

CLI (recommended)

npx -p clawql-mcp clawql init --interactive
npx -p clawql-mcp clawql doctor
npx -p clawql-mcp clawql mcp-config

Paste mcp-config output into Cursor MCP settings, then restart the client.

Quickstart MCP clients Vault memory

Copy-paste prompt

For agent-guided setup, copy the full prompt from the repo: agent-setup-prompt.md

Highlights the agent should run:

clawql init --interactive — ~/.ClawQL, memory path, provider vault
clawql doctor — verify memory + secrets coverage
clawql mcp-config — secret-free MCP JSON
Smoke search + read-only execute on one default-stack vendor
Optional clawql init --push-vault when HashiCorp Vault is available (K8s)

Local vs cluster secrets

Mode	Secrets store
Local stdio	`~/.ClawQL/vault/providers.json` (loaded at MCP startup)
Kubernetes	HashiCorp Vault → ESO → `clawql-provider-env`
Dashboard	Provider secrets UI → Vault KV

Guide: local-provider-vault.md

Health check (HTTP)

PORT=8080 npx -p clawql-mcp clawql-mcp-http
CLAWQL_MCP_URL=http://127.0.0.1:8080 npx -p clawql-mcp clawql doctor