What is this project?
It is an example that lets you deploy a remote MCP server without authentication on Cloudflare Workers.
@djaman
基本情報
概要はまだありません
ツール一覧はまだありません
この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。
ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。
This example lets you deploy a remote MCP (Model Context Protocol) server on Cloudflare Workers that requires no authentication. It is aimed at developers who want a simple, publicly accessible MCP server for prototyping or connecting to local and remote MCP clients.
Deploy by clicking the “Deploy to Workers” button or run npm create cloudflare@latest -- my-mcp-server --template=cloudflare/ai/demos/remote-mcp-authless. Customize tools by editing the init() method in src/index.ts. Connect clients by providing the deployed SSE URL (e.g., remote-mcp-server-authless.<your-account>.workers.dev/sse).
src/index.tsmcp-remote proxy to connect Claude Desktop to remote toolsIt is an example that lets you deploy a remote MCP server without authentication on Cloudflare Workers.
Click the “Deploy to Workers” button or run `npm create cloudflare@latest -- my-mcp-server --template=cloudflare/ai/demos/remote-mcp-authless` from the command line.
Edit `src/index.ts` and define tools inside the `init()` method using `this.server.tool(...)`.
Go to the Playground at `https://playground.ai.cloudflare.com/` and enter your deployed MCP server’s SSE URL.
Use the `mcp-remote` proxy (install via npm) and add a configuration entry pointing to your SSE URL (local or remote) in Claude Desktop’s developer settings.
MeroFoundry is a remote MCP server available at https://platform.merofoundry.com/mcp.

Agent-Native Terminal

Multi-zone MCP server for GKE/EKS/AKS: Python tools from git, NeMo guardrails, SSO, autoscaling.

The tools your AI needs to make your games. Turn prompts into production-ready game assets — animated characters with their weapons attached, seamless textures, terrain, VFX, HUDs — and playable game kits Unity, Godot, U

Routebase keeps your API's design, docs, contract tests, mocks and monitoring in one living OpenAPI spec so they can't drift apart. Agents work on that same source of truth, under your team's permissions.
コメント