MCP

Start the server

@all2cf/send-mcp is public on npm. Its command entrypoint has been verified from a clean installation; npx and pnpm dlx resolve the same package.

ALL2CF_SEND_URL=https://your-runtime.workers.dev \
ALL2CF_SEND_KEY=send_live_xxx \
npx -y @all2cf/send-mcp
# pnpm: pnpm dlx @all2cf/send-mcp

The MCP server connects to your Runtime. It does not receive a Cloudflare OAuth token.

Scope access

• Use a dedicated Runtime key.
• Grant only the tools the client needs.
• Rotate the key without changing the Runtime URL.
• Keep Cloudflare credentials out of MCP configuration.

Available tools

The server can send one message, send a batch of up to 100, list/get/cancel/reschedule email, and manage the supported templates, webhooks, API keys, domains, logs, suppressions and topics. Domain verification and template publication are explicit tools.

Start with a sending-only key if the AI only sends and reads messages. Resource creation, updates and deletion require a key with matching permission. Review every destructive tool confirmation in the MCP client.

Verify the connection

List emails before enabling write tools. Then send one message to a verified destination with a stable idempotency key and confirm its ID in the CFsend console. 401 usually means the MCP process did not receive the key; a network error usually means the Runtime URL is wrong or unreachable. The MCP server never needs a Cloudflare OAuth token.