Remote MCP Server on Cloudflare

Created By
threepointonea year ago
Overview

what is Remote MCP Server on Cloudflare?

Remote MCP Server on Cloudflare is a tool that allows users to set up a remote Model Context Protocol (MCP) server using Cloudflare Workers, complete with OAuth login functionality.

how to use Remote MCP Server on Cloudflare?

To use the Remote MCP Server, clone the repository, install dependencies, and run the server locally. You can then connect to the server using the MCP Inspector or integrate it with Claude Desktop for enhanced functionality.

key features of Remote MCP Server on Cloudflare?

  • Easy setup of a remote MCP server on Cloudflare Workers.
  • OAuth login integration.
  • Local development and testing capabilities.
  • Compatibility with MCP Inspector and Claude Desktop.

use cases of Remote MCP Server on Cloudflare?

  1. Setting up a remote server for model context protocol applications.
  2. Connecting various clients like Claude Desktop to the MCP server.
  3. Debugging and testing MCP functionalities locally before deployment.

FAQ from Remote MCP Server on Cloudflare?

  • Can I run the MCP server locally?

Yes! You can develop and test the MCP server locally before deploying it to Cloudflare.

  • How do I connect Claude Desktop to my MCP server?

You need to update the Claude configuration file with your MCP server's URL and restart Claude.

  • What should I do if I encounter issues?

Restarting Claude or connecting directly via command line can help resolve issues.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
threepointone
Star
2
Language
TypeScript
License
-

Recommend Servers

View All
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)

2 days ago