Cloudflare stack for hackathon teams

Launch Cloudflare agent projects faster, without hunting across docs.

This kit collects the best official Cloudflare starters for Agents, MCP, Sandboxes, Dynamic Workers, Workers for Platforms, VibeSDK, and Cloudflare Skills so teams can get from kickoff to demo faster.

Set up your agent

Install Cloudflare Skills before the hack starts

Cloudflare Skills bundles contextual platform guidance, slash commands, and remote MCP servers so Claude Code and Cursor can build on Workers with less ramp time and fewer stale assumptions.

Claude Code

Official setup guide
Install the Cloudflare plugin

Cloudflare Skills gives Claude Code persistent platform context, bundles the remote MCP servers, and adds slash commands for common build paths.

Setup
claude
/plugin marketplace add cloudflare/skills
/plugin install cloudflare@cloudflare
Try it
/cloudflare:build-agent
  • Run Claude Code from the root of your Workers project so it sees wrangler.jsonc and your bindings.
  • Use claude mcp list if you want to confirm the Cloudflare servers are connected.
  • The bundled wrangler skill helps Claude choose deploy and resource commands automatically.

Cursor

Marketplace or command install
Install Cloudflare in Cursor

The Cursor plugin path installs Cloudflare Skills and registers the MCP servers so Composer can generate, deploy, and debug on the platform with current docs.

Setup
/add-plugin cloudflare
Try it
Build a multi-tenant SaaS backend where each customer gets an isolated D1 database.
  • Alternative path: Cursor Marketplace -> Cloudflare, if you prefer installing visually.
  • Manual path: Settings -> Rules -> Add Rule -> Remote Rule (Github) -> cloudflare/skills.
  • Add @wrangler.jsonc to Composer prompts when you want Cursor to reason from your current bindings.

What it enables

What Cloudflare Skills accelerates for hackathon teams

The point is not just installation. It shortens ramp-up time, keeps the agent on live Cloudflare docs, and gives teams a reliable path from prompt to deployment.

Auto-load 8 Cloudflare skills

The agent picks up Cloudflare platform guidance contextually instead of making you restate Durable Objects, Wrangler, or Agents SDK conventions every time.

Bundle 5 MCP servers

The plugin wires in Cloudflare API, docs, bindings, builds, and observability MCP servers so teams can build and debug with live platform access.

Use slash commands for scaffolding

Hackathon teams can call /cloudflare:build-agent or /cloudflare:build-mcp to jump directly into working project structures.

Reach 2,500+ APIs with Code Mode

The Cloudflare API MCP server uses search plus execute so the agent can access the full API surface in a token-efficient way.

Stay current with live docs

The cloudflare-docs MCP server keeps the agent aligned with current platform behavior, which is especially useful during a fast-moving hackathon.

Pick the right interface automatically

Skills help the agent decide when to use Wrangler, MCP, or direct SDK patterns, which reduces wandering and speeds up shipping.

cloudflareagents-sdkdurable-objectssandbox-sdkwranglerweb-perfbuilding-mcp-server-on-cloudflarebuilding-ai-agent-on-cloudflare

Tracks

Choose the build path that matches the idea

Teams do not need every product. This section narrows each product family to the project shapes it fits best.

Agents

Starter repo: 1.2k stars
Agents plus Agents SDK

Use this track when teams want stateful chat, long-lived agent identity, scheduling, approvals, WebSockets, and easy Workers AI integration.

Starter path: Start with cloudflare/agents-starter, then branch into MCP, callable methods, or Codemode once the base chat flow is working.

Internal copilot with approval-gated actionsCustomer support triage agent with tool callsIncident helper with MCP-connected data sources

MCP

Official example-based path
Remote MCP servers and Codemode

This is the highest-leverage extension path for hackathon teams that want agents to call structured tools or orchestrate many tool calls through code generation.

Starter path: Use the Agents MCP examples for server and client patterns, then layer Codemode when the model needs to write TypeScript to coordinate tool chains.

A repo-aware coding assistantAn approval-aware infra operatorA multi-tool research assistant with MCP backends

Sandboxes

SDK repo: 998 stars
Sandboxes plus Sandbox SDK

Pick this track when teams need secure execution, file systems, preview URLs, code interpreters, or agent-driven coding loops.

Starter path: Start with the minimal template, then jump to Code Interpreter, Analyze Data with AI, Claude Code, OpenAI Agents, or OpenCode examples.

Code interpreter for support engineersData analysis agent with CSV uploadsSelf-healing dev sandbox for generated apps

Dynamic Workers

Cloudflare reference platform template
Workers for Platforms

Use this when hackathon teams need to deploy many generated or user-authored apps behind one platform with dynamic dispatch routing.

Starter path: Begin with the Worker Publisher template, then customize routing by path, subdomain, or KV and add per-user bindings or outbound worker controls.

Per-team app hosting platformGenerated mini-app showcaseUser-specific AI tools deployed on demand

VibeSDK

Repo: 5k stars, 1.2k forks
End-to-end app generation

VibeSDK is the most complete example in the stack: a production-grade text-to-app system built entirely on Cloudflare services.

Starter path: Use it when the team wants the whole architecture already composed: Agent, sandbox preview, data layer, and Workers for Platforms deployment.

A constrained internal app builderA customer-facing text-to-tool prototypeA hackathon project factory for demos

Build order

A simple path from agent to platform

This is the shortest path from prototype to something demoable on the public internet.

Step 01

Start with an agent

Use the Agents Starter to get a real-time chat loop, tool calling, and state sync working in minutes.

Step 02

Add secure execution

Bring in Sandbox when your agent needs to run code, inspect files, or host previews safely.

Step 03

Host many outputs

Use Workers for Platforms when the hackathon project needs to deploy many generated or user-owned apps.

Step 04

Use VibeSDK when you want the whole stack

Skip composition work and deploy the full app-generation platform when speed matters more than minimalism.

Compare

What each starter really gives you

Use this matrix to route teams quickly during kickoff, office hours, or judging prep.

Product Starter Best for Includes Needs
Agents SDK cloudflare/agents-starter Chat agents, tool calling, scheduling, approvals React UI, Workers AI, state sync, vision, WebSockets Workers only
Sandbox SDK examples/minimal Secure code execution, previews, data analysis Containers, file system, exec, code interpreter Workers Paid plan and Docker for local dev
Dynamic Workers worker-publisher-template Routing many user apps behind one platform Dispatch namespace, deploy API flow, path router Workers for Platforms
VibeSDK cloudflare/vibesdk Full text-to-app platform Agents, Sandbox, D1, KV, R2, WfP, SDK Workers Paid plan, WfP, custom domain, secrets

Build on Cloudflare

Build at the hackathon, deploy on Cloudflare.

Use Cloudflare Skills to onboard quickly, start from official templates, and ship real demos to the public edge without building the platform from scratch.