What transport does the server use?
It uses Server-Sent Events (SSE) – connect to the `/sse` endpoint.
@yukikazechan
Basic information
No overview available yet
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"remote-mcp-server-yukikazechan": {
"command": "npx",
"args": [
"nx",
"dev",
"remote-mcp-server"
]
}
}
}Tool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
Fetch the live tool list by running this server in a temporary sandbox using the button above.
A template for deploying a remote Model Context Protocol (MCP) server on Cloudflare Workers, complete with OAuth login. It enables developers to build and host MCP tools that can be called from remote MCP clients over HTTP.
Clone the repository, install dependencies with pnpm, run locally via npx nx dev remote-mcp-server, and connect using the MCP Inspector or Claude Desktop. For deployment, create a KV namespace with wrangler, add its ID to wrangler.jsonc, then run npm run deploy. Clients connect to the /sse endpoint using an SSE transport proxy.
workers.dev URLIt uses Server-Sent Events (SSE) – connect to the `/sse` endpoint.
Add an entry to your Claude Desktop config using `npx mcp-remote` with the server’s `workers.dev` URL ending in `/sse`.
Create a KV namespace via `npx wrangler kv namespace create OAUTH_KV`, add the namespace ID to `wrangler.jsonc`, then run `npm run deploy`.
Restart Claude, test directly with `npx mcp-remote http://localhost:8787/sse`, or clear cached auth files with `rm -rf ~/.mcp-auth`.
It runs at `http://localhost:8787/` when started with the development command.
An MCP server for Azure DevOps
Put the project you are working on online. Deploys the current folder or a GitHub repo to a live HTTPS URL on Dockhold; reads status and logs, sets variables, resizes apps and databases...
Connect Supabase to your AI assistants
Official OutageDeck MCP server for vendor-published cloud and SaaS status, incident timelines, and observed uptime history.
Comments