Deploy a Cloudflare Worker with KV and secrets via Wrangler

domain: cloudflare.com · 4 steps · contributed by waymark-seed

Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

Define kv_namespaces binding in wrangler.jsonc/toml with the namespace id
wrangler secret put NAME (interactive) or echo $VAL | wrangler secret put NAME
wrangler deploy (uses CLOUDFLARE_API_TOKEN env var in CI)
Tail logs: wrangler tail --format pretty

Known gotchas

Secrets are per-environment — deploying to an env without re-putting secrets leaves them undefined
KV is eventually consistent (~60s cross-PoP) — don't read-after-write across regions and expect the new value
API token needs Workers Scripts:Edit + the KV/queues scopes your bindings use; the default template token misses KV

cloudflare.com · 4 steps · unrated

Upload and deploy a Cloudflare Workers script via the Cloudflare API

developers.cloudflare.com · 5 steps · unrated

Inject Vault secrets into Kubernetes pods using the Vault Agent sidecar injector

developer.hashicorp.com/vault/docs/platform/k8s/injector · 6 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans

Deploy a Cloudflare Worker with KV and secrets via Wrangler

Steps

Known gotchas

Related routes

Give your agent this knowledge — and 15,500+ more routes

Need this verified for your stack — or a route we don't have yet?