Name: API Workers (Cloudflare)
Author: cyanheads

What it does

This skill documents how to deploy an MCP-style server into Cloudflare Workers using the package @cyanheads/mcp-ts-core/worker and its exported helper createWorkerHandler. It explains the per-request McpServer factory pattern, how to register tools/resources/prompts, and how to safely map environment and object bindings into the Worker runtime. Concrete guidance covers lazy env parsing, handling object bindings on globalThis, runtime capability checks (isWorkerLike, isNode), and recommended wrangler.toml settings. The material is aimed at developers who want to run an MCP server in Cloudflare's constrained environment and need practical patterns to avoid common runtime and configuration pitfalls.

When to use it

Use this skill when you are packaging an MCP server for deployment to Cloudflare Workers — for example, when you need a compact, edge-deployed API that registers tools, prompts, and resources per request. It's appropriate when you must support Cloudflare-specific bindings (KV, R2, D1) or when you want safe fallbacks for node-only utilities. If your project requires persistent storage beyond in-memory, follow the storage whitelist guidance in this skill.

What's included

Scripts: none packaged with the SKILL.md, but the skill includes code examples showing createWorkerHandler usage.
References: inline guidance on runtimeCaps, binding types, and wrangler.toml configuration.
Instructions: step-by-step patterns for wiring tools/resources/prompts, mapping env/object bindings, and guarding node-only features.