This guide covers:

1. Initial setup after clicking Deploy to Cloudflare
2. Manual deploy with Wrangler
3. How to connect the OpenSEO MCP server through Cloudflare Access
4. How to update to the latest OpenSEO version
5. How to add teammates

Click the deploy button, there are lots of fields on the deploy form, but you only need to do the below steps.

1. Connect your Git provider (GitHub/GitLab).
2. Leave the resource naming fields as default unless you have a reason to change them.
3. Click Create and Deploy.
4. Wait 1-2 minutes for deployment to finish.

If deploy fails with Cannot provision a KV Namespace with the title "open-seo" because it already exists, use the manual deploy with Wrangler flow instead.

In the Cloudflare dashboard:

1. Go to Compute -> Workers & Pages -> your OpenSEO Worker.
2. Open Settings.
3. In Domains & Routes, enable Cloudflare Access for the workers.dev route.
4. Save the values shown by Cloudflare Access.
5. In Variables & Secrets, add:
   • POLICY_AUD (from Access setup)
   • TEAM_DOMAIN (domain from JWKS_URL, for example https://your-team.cloudflareaccess.com)
   • DATAFORSEO_API_KEY

DataForSEO API responses are cached in R2 under the dataforseo-cache/ prefix. This step is optional, but recommended to automatically clean up expired cache objects:

npx wrangler r2 bucket lifecycle add open-seo dataforseo-cache-expiry dataforseo-cache/ --expire-days 7

If you changed the R2 bucket name during deploy, replace open-seo with your bucket name.

Without a lifecycle rule, cached objects under dataforseo-cache/ will accumulate indefinitely and increase storage costs over time.

1. Open your Worker URL again.
2. Sign in with Cloudflare Access.
3. OpenSEO should load after login.

If login fails, re-check the three secrets and Access toggle.

Use the same Cloudflare Access application that protects your OpenSEO Worker. Managed OAuth is required for MCP clients and is not enabled by default.

1. Open Cloudflare Zero Trust.
2. Go to Access controls -> Applications.
3. Find your OpenSEO application, then select Edit.
4. Go to Additional settings -> OAuth.
5. Turn on Managed OAuth.
6. In Managed OAuth settings, allow the redirect URIs your MCP clients use:
   • Allow localhost / loopback clients — for CLI and desktop agents (Codex CLI, Claude Code) that register http://localhost:PORT/callback.
   • Add HTTPS redirect URIs for web connectors (a path may end in /*).
   • Without this, clients can't finish Dynamic Client Registration and log in but expose no tools.
7. Save.

MCP clients should connect to:

https://YOUR_WORKER_HOSTNAME/mcp

If your repo was created from the Cloudflare Deploy button, use this flow.

Run this once in your local repo:

git remote add upstream https://github.com/every-app/open-seo.git
git fetch upstream

git fetch upstream
cp wrangler.jsonc wrangler.local.backup.jsonc
git checkout main
git reset --hard upstream/main
cp wrangler.local.backup.jsonc wrangler.jsonc
git add wrangler.jsonc
git commit -m "restore Cloudflare settings" || true
git push --force-with-lease origin main

Why this is needed:

• wrangler.jsonc has your Cloudflare resource IDs.
• The update step keeps your IDs while pulling the newest OpenSEO code.

1. Open Cloudflare Zero Trust.
2. Go to Access -> Applications.
3. Open your OpenSEO application.
4. Edit the Allow policy.
5. Add teammate emails (or your company email domain / group).
6. Save.

Screenshots from the setup flow:

• Edit the Access policy
• Add teammate emails to the allow list

After saving, teammates can open your OpenSEO URL and sign in through Cloudflare Access. OpenSEO will use a shared workspace for everyone allowed by the policy.

Use this flow if the Deploy to Cloudflare button fails with Cannot provision a KV Namespace with the title "open-seo" because it already exists. The reliable path is to create Cloudflare resources yourself, put their IDs into wrangler.jsonc, then deploy with Wrangler.

Fork every-app/open-seo on GitHub if you want a repo you control for future updates, then clone it locally:

git clone https://github.com/YOUR_GITHUB_USER/open-seo.git
cd open-seo
corepack enable
pnpm install

If you do not need a fork, clone the upstream repo instead:

git clone https://github.com/every-app/open-seo.git
cd open-seo
corepack enable
pnpm install

pnpm exec wrangler login

Use unique names so they do not collide with resources that already exist in your Cloudflare account. Replace YOUR_SUFFIX with something unique to you, for example your GitHub username or company name.

pnpm exec wrangler kv namespace create open-seo-YOUR_SUFFIX
pnpm exec wrangler kv namespace create open-seo-oauth-YOUR_SUFFIX
pnpm exec wrangler d1 create open-seo-YOUR_SUFFIX
pnpm exec wrangler r2 bucket create open-seo-YOUR_SUFFIX

Save the IDs and names printed by Wrangler:

• The first KV namespace ID is for the KV binding.
• The second KV namespace ID is for the OAUTH_KV binding.
• The D1 database_id is for the DB binding.
• The R2 bucket name is for the R2 binding.

Open wrangler.jsonc and replace only your Cloudflare resource values. Keep the binding names exactly as shown below, because the application code expects those names.

"kv_namespaces": [
  {
    "binding": "KV",
    "id": "YOUR_KV_NAMESPACE_ID",
  },
  {
    "binding": "OAUTH_KV",
    "id": "YOUR_OAUTH_KV_NAMESPACE_ID",
  },
],
"d1_databases": [
  {
    "binding": "DB",
    "database_name": "open-seo-YOUR_SUFFIX",
    "database_id": "YOUR_D1_DATABASE_ID",
    "migrations_dir": "drizzle",
  },
],
"r2_buckets": [
  {
    "bucket_name": "open-seo-YOUR_SUFFIX",
    "binding": "R2",
  },
],

Do not use wrangler deploy --update-config for this step. Edit wrangler.jsonc manually so "migrations_dir": "drizzle" stays in the D1 database config.

pnpm run deploy

In the Cloudflare dashboard:

1. Go to Compute -> Workers & Pages -> your OpenSEO Worker.
2. Open Settings.
3. In Domains & Routes, enable Cloudflare Access for the workers.dev route.
4. Save the values shown by Cloudflare Access.

Then set the same values as Worker secrets with Wrangler:

pnpm exec wrangler secret put TEAM_DOMAIN
pnpm exec wrangler secret put POLICY_AUD
pnpm exec wrangler secret put DATAFORSEO_API_KEY

Use the domain from JWKS_URL for TEAM_DOMAIN, for example https://your-team.cloudflareaccess.com. Use the Access application audience value for POLICY_AUD.

DataForSEO API responses are cached in R2 under the dataforseo-cache/ prefix. This step is optional, but recommended to automatically clean up expired cache objects:

pnpm exec wrangler r2 bucket lifecycle add open-seo-YOUR_SUFFIX dataforseo-cache-expiry dataforseo-cache/ --expire-days 7

1. Open your Worker URL again.
2. Sign in with Cloudflare Access.
3. OpenSEO should load after login.

If login fails, re-check the three secrets, the Access toggle, and the binding values in wrangler.jsonc.