epicflare logo
A starter and reference for building full-stack web applications on Cloudflare Workers
epicflare ships a Remix-powered UI, server routing, and OAuth-protected MCP endpoints so you can build both a user-facing app and tooling APIs on the same Worker.
bunx create-epicflare
This will clone the template, install dependencies, run the guided setup, and start the dev server.
See docs/getting-started.md for the full setup
paths and expectations.
| Layer | Technology |
|---|---|
| Runtime | Cloudflare Workers |
| UI Framework | Remix 3 (alpha) |
| Package Manager | Bun |
| Database | Cloudflare D1 |
| Session/OAuth | Cloudflare KV |
| MCP State | Durable Objects |
| E2E Testing | Playwright |
| Bundler | esbuild |
Request → worker/index.ts
│
├─→ OAuth handlers
├─→ MCP endpoints
├─→ Static assets (public/)
└─→ Server router → Remix components
worker/index.tsis the entrypoint for Cloudflare Workers- OAuth requests are handled first, then MCP requests, then static assets
- Non-asset requests fall through to the server handler and router
- Client assets are bundled into
public/and served via theASSETSbinding
| Document | Description |
|---|---|
docs/getting-started.md |
Setup, environment variables, deploy |
docs/environment-variables.md |
Adding new env vars |
docs/cloudflare-offerings.md |
Optional Cloudflare integrations |
docs/agents/setup.md |
Local development and verification |
Built with ❤️ by Epic Web