- Home
- MCP servers
- Remote MCP Server Authless
Remote MCP Server Authless
- typescript
0
GitHub Stars
typescript
Language
6 months ago
First Indexed
3 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
You can deploy a remote MCP (Multimodal Conversational Principles) server on Cloudflare Workers that exposes a simple HTTP endpoint for MCP clients. This setup lets you add your own tools and connect from MCP clients or the Cloudflare AI Playground, giving you a lightweight, authless remote MCP server you can customize and extend.
How to use
Connect your MCP client to the remote server using the HTTP endpoint that starts with remote-mcp-server-authless. This server is designed to be accessed by MCP clients via an HTTP URL and to expose tools you define in the server’s init method. From the Cloudflare AI Playground, you can directly load your deployed MCP server by entering the server URL and then invoking the available tools. If you want to use local MCP clients, you can point them at the remote URL to run tools remotely.
How to install
Prerequisites you need before you begin:
- Node.js and npm installed on your machine
- A Cloudflare Workers account or the ability to deploy Workers
- Basic knowledge of editing TypeScript sources (src/index.ts)
Step 1: Create your remote MCP server project on Cloudflare using the following command.
npm create cloudflare@latest -- my-mcp-server --template=cloudflare/ai/demos/remote-mcp-authless
Step 2: Open the generated project and customize your tools. Inside the main source file, add each tool inside the init() method by calling this.server.tool(...). This is how you define the capabilities your MCP server will expose to clients.
Additional content
Connecting from the Cloudflare AI Playground is straightforward: open the playground, enter your deployed MCP server URL (for example remote-mcp-server-authless.your-account.workers.dev/sse), and start using your tools directly from the playground interface.
Connecting from a local MCP client (stdio) is supported via an mcp-remote proxy. If you want to configure a client like Claude Desktop, add a configuration block for your remote server. For example, you can reference the remote URL in your client’s MCP server settings to enable tool access without hosting a local server.
Configuration and notes
The example setup includes a remote server that can be accessed at an HTTP URL. To connect from Claude Desktop, place the remote URL in your client configuration so the local client can reach the server. If you want to run a local proxy, you can point the client to the remote server URL for the sse endpoint.