Cloudflare MCP Server

Created By
zackbissella year ago
Overview

what is Cloudflare MCP Server?

Cloudflare MCP Server is a repository that provides several Model Context Protocol (MCP) servers for managing context between large language models (LLMs) and Cloudflare's services, allowing users to accomplish tasks using natural language.

how to use Cloudflare MCP Server?

To use the Cloudflare MCP Server, connect your MCP client to the desired server URL provided in the repository. If your client does not support remote MCP servers, configure it using the mcp-remote package to specify accessible servers.

key features of Cloudflare MCP Server?

  • Multiple MCP servers for various Cloudflare services
  • Natural language processing capabilities for task management
  • Integration with Cloudflare's application development, security, and performance services

use cases of Cloudflare MCP Server?

  1. Managing Cloudflare Workers applications
  2. Debugging application logs and analytics
  3. Optimizing DNS performance and monitoring digital experiences

FAQ from Cloudflare MCP Server?

  • What is the Model Context Protocol (MCP)?

MCP is a standardized protocol for managing context between LLMs and external systems.

  • Do I need a paid Cloudflare plan to use all features?

Some features may require a paid Cloudflare Workers plan, depending on the functionality you intend to use.

  • How can I contribute to the Cloudflare MCP Server?

You can contribute by following the guidelines in the CONTRIBUTING.md file in the repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
zackbissell
Star
0
Language
TypeScript
License
Apache-2.0 license

Recommend Servers

View All
Crevio

2 days ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago