Skip to main content

Step 0: Get set up

By the end you will be able to:

  • Log in to Wrangler and see your own team account
  • Connect your coding agent to live Cloudflare docs and this event’s MCP server
  • Have your agent deploy and delete a throwaway Worker to prove the whole chain works
Your system:Every command in the guide shows only this one. Change it any time.
Your team and account

Checking your assignment… If it cannot load, ask a host and continue with the guide.

The account id and hostname below are placeholders. They appear here once a host assigns you to a team.

Account
shown here once your team is assigned
Account id
TEAM_ACCOUNT_ID
Demo hostname
TEAM_HOSTNAME

Use the Cloudflare account on your team card (also on the Workspace page). No account yet? Ask a host: you can read on, but you can't deploy until it is ready.

Why it matters​

  • Your time is short. Nobody's first hour should go on a Node install or a blocked login.
  • Do it once. It takes about ten minutes. The laptop part is also on Get ready, which is open before the day, so you can do it early.
  • Every later step gets smaller. Each one becomes a small change to something that already works.

The concepts​

Four things, in this order:

  • Your laptop: Node and Wrangler (the Cloudflare CLI), logged in with the email your team's Cloudflare invitation went to.
  • Your team account: every team builds in its own Cloudflare account, so nobody can touch another team's work and every example in this guide works unchanged. A host invites you; only the account id and your demo hostname differ from team to team.
  • Your coding agent: pointed at live Cloudflare docs, so it writes against what exists today instead of memory.
  • This event's MCP server (https://build-stockholm.events-cloudflare.com/mcp): the brief, the Idea Gallery, your team card and the steps, as tools your coding agent can call. Nothing here is required for the build: docs, forms and submit all work in the browser.

Do it​

1. Laptop​

  • Node.js 22.12 or newer (nodejs.org) and a terminal (Terminal or iTerm on macOS, PowerShell on Windows).
  • A laptop you can install npm packages on. Nothing to install globally: everything runs through npx.
node -v                  # v22.12 or higher
npx wrangler --version   # confirms npx and npm registry access
npx wrangler login       # opens a browser tab, approve it
npx wrangler whoami      # prints your email and the accounts you can use

Once you have accepted your team's invitation (see Your team account), wrangler whoami lists your team account: its name and id are on your team card. You may see other accounts too; that is normal, and you pin yours in wrangler.jsonc in Step 1.

Clear old settings first if you ever used the old shared Customer Engineering Events account, or any other Cloudflare account, from this terminal. An old CLOUDFLARE_API_TOKEN overrides your login and only works for the account it was made for, and an old CLOUDFLARE_ACCOUNT_ID points commands at the wrong place. Also look in your shell profile and in any .env file.

macOS / Linux
unset CLOUDFLARE_ACCOUNT_ID CLOUDFLARE_API_TOKEN

2. Your coding agent​

Already use Claude Code, Cursor, Windsurf, GitHub Copilot, OpenCode or Codex? Paste this in:

Prompt for your coding agent
Fetch https://developers.cloudflare.com/agent-setup/prompt.md

Paste it into your coding agent: the terminal, the IDE panel or the desktop app all work.

It installs Cloudflare's skills and MCP servers for your agent. Per-agent guides: developers.cloudflare.com/agent-setup.

3. The event MCP server​

Add it to your agent's MCP config. This is the common mcpServers shape (Cursor, Claude Desktop); other tools word it differently:

{
  "mcpServers": {
    "build-stockholm": {
      "url": "https://build-stockholm.events-cloudflare.com/mcp"
    }
  }
}

In Claude Code, run claude mcp add --transport http build-stockholm https://build-stockholm.events-cloudflare.com/mcp instead. In any other tool, ask your agent to add the MCP server at that URL.

Tools: get_brief, list_ideas, get_idea, get_platform_guide, get_step, get_my_kit, get_shield_steps, scope_my_project, search_cloudflare_docs, ask_mentor, check_my_deploys, submit_project. None of them writes anything: submit_project only checks a draft, and you submit on the Submit page.

Check it worked​

Ask your coding agent:

Prompt for your coding agent
In a new empty folder called hello-world, create a Cloudflare Worker named hello-world that returns
"Hello from Build with Cloudflare Stockholm!". Use my team account: put "account_id": "<ACCOUNT ID FROM MY TEAM CARD>"
in its wrangler.jsonc, run `npx wrangler whoami`, and stop if that account is not listed. Then deploy it,
open the URL it prints, and delete it again with `npx wrangler delete`.

Paste it into your coding agent: the terminal, the IDE panel or the desktop app all work.

Paste your real account id in place of the placeholder. The explicit account_id matters: a coding agent that creates a new folder also creates a new wrangler.jsonc, and without it Wrangler can pick any account you belong to.

  • wrangler whoami lists your team account.
  • The agent deploys the Worker, you see it answer, then it deletes it. Works? You are set.
Stuck?
  • npm hangs or errors. Usually a corporate laptop blocking the npm registry. Try a phone hotspot, or ask a host before the day.
  • The wrangler login pop-up is blocked. Wrangler also prints the login address in the terminal: copy it into another browser. Ask a host if that does not work either.
  • wrangler whoami does not list your team account. You have not accepted your team account invitation yet: check your inbox, or open Get ready to see where a host has got to. Then run npx wrangler login again with the same email. Still missing? Tell a host.
  • Wrangler asks you to register a workers.dev subdomain. A new account has none, and a Worker with no routes is published on workers.dev by default, so the throwaway Worker needs one. Choose any name. If your coding agent ran the deploy and it stopped on this question, register the subdomain yourself (dashboard > Workers & Pages > Your subdomain) or run npx wrangler deploy in a terminal and answer there, then ask the agent to continue. The starter does not need it: it keeps workers.dev off and uses your own hostname.
  • A command ran in the wrong account. Check account_id in that folder's wrangler.jsonc, then the clear-old-settings commands above. Delete anything you created in the wrong account.
  • No coding agent, or it cannot reach the MCP server. Skip it: nothing blocks your build without it.
Go further
ServerURLWhat for
Cloudflare APIhttps://mcp.cloudflare.com/mcpThe whole Cloudflare API via search()/execute()
Cloudflare Docshttps://docs.mcp.cloudflare.com/mcpUp-to-date developer docs
Agents SDK Docshttps://agents.cloudflare.com/mcpBuilding the agent itself
AI Gatewayhttps://ai-gateway.mcp.cloudflare.com/mcpSearch gateway logs (handy for Shield 1)
Browser Renderinghttps://browser.mcp.cloudflare.com/mcpFetch pages, markdown, screenshots

Full list: Cloudflare's MCP servers.

Setup done?

Checking your team…

Next: Step 1: Launch your first agent.

Need help? Raise a hand for a host, or ask the Mentor dock (it escalates to a host when unsure). Remote: remote help channel to be confirmed by the event owner.