Remote MCP Server on Cloudflare
The Remote MCP Server on Cloudflare allows developers to create and interact with a Model Context Protocol (MCP) server using Cloudflare Workers. Key capabilities include:
Development and deployment: Develop locally and deploy to Cloudflare Workers for remote access
Authentication: Supports OAuth login and bearer token authentication with a
getTokentoolTool integration: Provides tools like
get_list_tweetsto retrieve tweets from a specified Twitter list with configurable maximum results (1-100)Client connectivity: Connect with MCP Inspector to explore the API or integrate with Claude Desktop
Debugging: Supports troubleshooting options including restart and direct server connections
Enables deployment of the MCP server on Cloudflare Workers infrastructure, providing a serverless environment for hosting the MCP service with OAuth authentication capabilities.
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 on Cloudflare get my current authentication token"
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
Let's get a remote MCP server up-and-running on Cloudflare Workers complete with OAuth login!
Develop locally
# clone the repository
git clone git@github.com:cloudflare/ai.git
# install dependencies
cd ai
npm install
# run locally
npx nx dev remote-mcp-server-bearer-authYou should be able to open http://localhost:8787/ in your browser
Related MCP server: Remote MCP Server on Cloudflare
Connect the MCP inspector to your server
To explore your new MCP api, you can use the MCP Inspector.
Start it with
npx @modelcontextprotocol/inspectorWithin the inspector, switch the Transport Type to
SSEand enterhttp://localhost:8787/sseas the URL of the MCP server to connect to.Add a bearer token and click "Connect"
Click "List Tools"
Run the "getToken" tool, which should return the Authorization header that you set in the inspector
Connect Claude Desktop to your local MCP server
{
"mcpServers": {
"remote-mcp-server-bearer-auth": {
"command": "npx",
"args": [
"mcp-remote",
"http://localhost:8787/sse",
"--header",
"Authorization: Bearer ${AUTH_TOKEN}"
]
},
"env": {
"AUTH_TOKEN": "..."
}
}
}Deploy to Cloudflare
npm run deploy
Call your newly deployed remote MCP server from a remote MCP client
Just like you did above in "Develop locally", run the MCP inspector:
npx @modelcontextprotocol/inspector@latest
Then enter the workers.dev URL (ex: worker-name.account-name.workers.dev/sse) of your Worker in the inspector as the URL of the MCP server to connect to, and click "Connect".
You've now connected to your MCP server from a remote MCP client. You can pass in a bearer token like mentioned above
Debugging
Should anything go wrong it can be helpful to restart Claude, or to try connecting directly to your MCP server on the command line with the following command.
npx mcp-remote http://localhost:8787/sseIn some rare cases it may help to clear the files added to ~/.mcp-auth
rm -rf ~/.mcp-authAvailable Tools
1 toolget_list_tweetsC
Get tweets from a specific list
Inputs: list_id (required), max_results.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined and distinct by default.
A single tool inherently has consistent naming, as there are no other tools to compare it against. The name 'get_list_tweets' follows a clear verb_noun pattern.
One tool is generally too few for a server's purpose, as it limits functionality and suggests an incomplete or narrow scope. This is borderline inadequate for typical MCP server operations.
Inferring the domain as Twitter list management, the tool surface is severely incomplete. It only allows getting tweets from a list, with no capabilities for creating, updating, deleting lists, or interacting with tweets beyond retrieval, leading to significant gaps.
Maintenance
Related MCP Connectors
Remote streamable-HTTP MCP server running on a single Cloudflare Worker. Your assistant gets live Airbnb, Amazon, Booking.com, Google Flights, Maps and Reddit data, social search on X, Instagram and TikTok, the Meta Ad Library, and image/video generation without any keys. Connect your own accounts to let it send WhatsApp or Telegram messages, work an IMAP inbox, manage Meta Ads campaigns and publish to X and LinkedIn. OAuth 2.1 with PKCE; stored credentials are AES-256-GCM encrypted.
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps.
MCP server connecting AI agents to 100+ apps (Gmail, Slack, Notion, GitHub) via one-click OAuth.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that runs on Cloudflare Workers with OAuth login, allowing AI assistants like Claude to execute tools remotely through HTTP connections.-
- FlicenseNot gradedqualityNot gradedmaintenanceA Model Context Protocol server implementation that runs on Cloudflare Workers with OAuth login, allowing Claude and other AI models to access tools via the MCP standard.-
- FlicenseBqualityNot gradedmaintenanceA server that enables Model Context Protocol (MCP) functionality on Cloudflare Workers with OAuth login, allowing applications like Claude Desktop to access custom tools through a standardized interface.2-
- FlicenseNot gradedqualityNot gradedmaintenanceA Model Context Protocol server that runs on Cloudflare Workers, enabling tools integration with Claude AI through OAuth login.-