cf-webmcp
Install

Five minutes to deploy.

Fork the repo, fill in one TOML file, and run wrangler deploy. No SDK install on your site, no plugin in your CMS.

1. Clone

The build and the npm scripts need Node.js 22 or later.

git clone https://github.com/basgr/cf-webmcp
cd cf-webmcp
npm install

2. Pick a template

Three starters ship:

cp templates/wordpress.toml webmcp.toml
cp wrangler.example.toml wrangler.toml

3. Edit

Open webmcp.toml and set:

Open wrangler.toml and set the route for your domain.

4. Preflight

npm run preflight -- --config=webmcp.toml

Reports OK / merge / COLLISION per path the Worker wants to claim. Exits non-zero on hard collisions unless you pass --force.

5. Deploy

The templates turn on the fallback widget for desktop MCP clients (fallback_widget = true), and its file has to be in R2 before you deploy. Create the R2 bucket that wrangler.toml names (cf-webmcp-assets in wrangler.example.toml), then pin and upload the widget. Take <version> and <sha256> from the version and sha256 fields of vendor/webmcp/current.json:

wrangler r2 bucket create cf-webmcp-assets
npm run update-widget -- --version=<version> --sha256=<sha256>
npm run upload-widget

See Pin the fallback widget. If you do not need desktop pairing, set fallback_widget = false instead.

npm run deploy

This chains npm run build (compiles TOML to TypeScript modules) and wrangler deploy. Hit /_webmcp/health on your domain to confirm the deploy landed.

Verify

After deploy, hit these URLs on your domain:

For local dev, see the docs.