Remote MCP Server on Cloudflare with Stainless
Remote MCP servers require OAuth, so this flow implements a local version of the OAuth redirects, but instead accepts theAPI token and any other client configuration options that you'd need to instantiate your TypeScript client.
Usage
The recommended way to use this project is to use the below "deploy to cloudflare" button to use this repo as a template for generating a server.
Develop locally
# install dependencies
npm install
# run locally
npm run dev
You should be able to open http://localhost:8787/
in your browser
Connect the MCP inspector to your server
To explore your new MCP api, you can use the MCP Inspector.
- Start it with
npx @modelcontextprotocol/inspector
- Within the inspector, switch the Transport Type to
SSE
and enterhttp://localhost:8787/sse
as the URL of the MCP server to connect to, and click "Connect" - You will navigate to a (mock) user/password login screen. Input any email and pass to login.
- You should be redirected back to the MCP Inspector and you can now list and call any defined tools!
Connect Claude Desktop to your local MCP server
The MCP inspector is great, but we really want to connect this to Claude! Follow Anthropic's Quickstart and within Claude Desktop go to Settings > Developer > Edit Config to find your configuration file.
Open the file in your text editor and replace it with this configuration:
{
"mcpServers": {
"teardown_mcp_api": {
"command": "npx",
"args": ["mcp-remote", "http://localhost:8787/sse"]
}
}
}
This will run a local proxy and let Claude talk to your MCP server over HTTP
When you open Claude a browser window should open and allow you to login. You should see the tools available in the bottom right. Given the right prompt Claude should ask to call the tool.
Deploy to Cloudflare
If you want to manually deploy this server (e.g. without the "deploy to cloudflare" button)
npx wrangler@latest kv namespace create remote-mcp-server-oauth-kv
- Follow the guidance to add the kv namespace ID to
wrangler.jsonc
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.
Connect Claude Desktop to your remote MCP server
Update the Claude configuration file to point to your workers.dev
URL (ex: worker-name.account-name.workers.dev/sse
) and restart Claude
{
"mcpServers": {
"teardown_mcp_api": {
"command": "npx",
"args": ["mcp-remote", "https://worker-name.account-name.workers.dev/sse"]
}
}
}
Debugging
Should anything go wrong it can be helpful to restart Claude, or to try connecting directly to yourMCP server on the command line with the following command.
npx mcp-remote http://localhost:8787/sse
In some rare cases it may help to clear the files added to ~/.mcp-auth
rm -rf ~/.mcp-auth