Remote MCP Server Authless
Deploy and run a remote MCP server on Cloudflare Workers, enabling AI agents to interact with custom tools without authentication.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Remote MCP Server Authlessdeploy a new remote MCP server on Cloudflare"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Remote MCP Server on Cloudflare (Without Auth)
A remote MCP server with no authentication, deployed on Cloudflare Workers.
Public endpoint: /mcp exposes three demo tools only: add, calculate, and greet. It has no access to any external service or credentials.
Get started
Deploy to Workers:
Or create a local copy from the template:
npm create cloudflare@latest -- my-mcp-server --template=cloudflare/ai/demos/remote-mcp-authlessOnce deployed, the server is at https://<your-worker>.<your-account>.workers.dev/mcp.
Related MCP server: remote-mcp-server-authless
Local development
npm install
npm run dev # wrangler dev, serves on http://localhost:8787
npm run type-check
npm testCustomizing
Add tools inside init() in src/index.ts using this.server.registerTool(...).
Connect a client
Cloudflare AI Playground: go to https://playground.ai.cloudflare.com/, enter your /mcp URL, and use the tools.
Claude Desktop (via mcp-remote): open Settings > Developer > Edit Config and add:
{
"mcpServers": {
"remote-mcp-server": {
"command": "npx",
"args": [
"mcp-remote",
"http://localhost:8787/mcp"
]
}
}
}Replace the URL with your deployed /mcp URL when not running locally. Restart Claude Desktop to load the tools.
Executive Operator (Zenzap agent): switched off
src/operator.ts and related files contain a Claude-powered agent that was designed to watch a Zenzap control topic and act on it. It is switched off (owner decision, 2026-10-11):
wrangler.jsonchas no cron triggers ("crons": []).scheduled()insrc/index.tsdoes nothing.The Zenzap tools are not exposed through
/mcp.
To re-enable it, restore the cron in wrangler.jsonc and the calls noted in the comment in src/index.ts. Its secrets are set with wrangler secret put: ZENZAP_API_KEY, ZENZAP_API_SECRET, ANTHROPIC_API_KEY, and optionally OWNER_MEMBER_ID. Those secrets must be set before it will run.
Known assumptions (for when it's re-enabled)
The response shapes of Zenzap's list endpoints and the request bodies for tasks and polls were not confirmed when this was written. normalizeMessage and extractList in src/zenzap.ts accept common field-name variants and log the raw payload when they find no messages. Tasks and polls use the generic zenzap_request tool.
This server cannot be deployed
Maintenance
Related MCP Connectors
9 remote MCP servers on Cloudflare Workers for AI agents. Free tier + Pro API keys.
Cloudflare Workers MCP server: ai-gateway
Cloudflare Workers MCP server: ai-agent-scratchpad
Cloudflare Workers MCP server: ai-guardrails
Related MCP Servers
- FlicenseNot gradedqualityCmaintenanceDeploys a remote MCP server on Cloudflare Workers without authentication, allowing connection to AI Playground or Claude Desktop.-
- FlicenseNot gradedqualityCmaintenanceDeploys a remote MCP server on Cloudflare Workers without authentication, enabling integration with AI Playground and Claude Desktop.-
- FlicenseNot gradedqualityCmaintenanceDeploy a remote MCP server on Cloudflare Workers without authentication, enabling connection to AI Playground and Claude Desktop.-
- FlicenseNot gradedqualityDmaintenanceDeploys a remote MCP server on Cloudflare Workers without authentication, enabling connection to Cloudflare AI Playground and Claude Desktop.-