Cloudflare MCP Server for Windsurf: Setup & Config

What you can do with Cloudflare in Windsurf

Choose curated Cloudflare product endpoints instead of a broad code-execution API interface.

• Investigate Workers logs and application analytics.
• Consult current Cloudflare reference documentation.
• Fetch pages and screenshots with the browser rendering service.

Before you start: Cloudflare in Windsurf

• An MCP-compatible client
• A Cloudflare account for account operations
• npx when using the mcp-remote bridge
• Appropriate API token permissions when using the OpenAI Responses API

This example selects the Observability server. Remote-capable clients can use its URL directly; the npx command is a compatibility bridge. Other product areas use separate URLs.

Cloudflare Windsurf configuration

1. Choose Windsurf configuration scope

   For Cloudflare MCP Server, open macOS/Linux: ~/.codeium/windsurf/mcp_config.json Windows: %USERPROFILE%\.codeium\windsurf\mcp_config.json. Merge into mcpServers; remote endpoints use serverUrl.

2. Add Cloudflare MCP Server to Windsurf

   Use the mcp-server-cloudflare entry below in mcpServers. Keep Cloudflare MCP Server's documented http connection fields and your other Windsurf entries.

3. Check Cloudflare MCP Server in Windsurf

   Cloudflare MCP Server: Refresh MCP in Windsurf settings and inspect Cascade’s tools.

{
  "mcpServers": {
    "mcp-server-cloudflare": {
      "serverUrl": "https://observability.mcp.cloudflare.com/mcp"
    }
  }
}

Troubleshooting Cloudflare in Windsurf

• For Cloudflare MCP Server, Windsurf reads serverUrl (observability.mcp.cloudflare.com), not url. Refresh the connection and check the tools exposed to Cascade.
• Cloudflare MCP Server: check http connectivity to observability.mcp.cloudflare.com from Windsurf; a stdio command is not a replacement for this endpoint.
• Transport mismatch: Cloudflare's catalog lists stdio; the displayed Windsurf configuration uses http.
• Known limitation: Some capabilities require a paid Cloudflare Workers plan.
• Known limitation: Long tool chains can exceed client context limits.
• Known limitation: SSE remains available but is deprecated.
• General Windsurf troubleshooting lives in the /clients/windsurf guide.

Frequently asked questions