How do I test my server locally?
Run `npx @modelcontextprotocol/inspector`, select SSE transport, and enter `http://localhost:8787/sse`. A mock login screen appears; input any credentials to connect.
@MCP-Mirror
Basic information
Mirror of
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"cyyzpanpan_remote-mcp-server": {
"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 scaffold to get a remote MCP server running on Cloudflare Workers with OAuth login. It provides local development, deployment, and connection to MCP clients like Claude Desktop.
Clone the repo, install dependencies, and run locally with npx nx dev remote-mcp-server. Deploy with npm run deploy after creating a Cloudflare KV namespace. Connect tools via SSE at the /sse endpoint using the MCP Inspector or Claude Desktop.
Run `npx @modelcontextprotocol/inspector`, select SSE transport, and enter `http://localhost:8787/sse`. A mock login screen appears; input any credentials to connect.
Edit Claude Desktop’s config file to add an `mcpServers` entry using `npx mcp-remote` with the SSE URL of your local or deployed server.
Create a KV namespace with `npx wrangler kv namespace create OAUTH_KV`, add its ID to `wrangler.jsonc`, then run `npm run deploy`.
Run `npx mcp-remote http://localhost:8787/sse` directly, or clear cached auth files with `rm -rf ~/.mcp-auth`.
It uses SSE (Server‑Sent Events) at the `/sse` endpoint.
Model Context Protocol (MCP) server for Kubernetes and OpenShift

Web hosting for websites built with AI. Connect your HostingFor.AI account and your AI assistant can publish and maintain your site directly: upload files, manage DNS records for custom domains, run SQL against your MySQ

Build and run websites, APIs, automations, and admin tools from chat. Your agent creates the data, logic, pages, and scheduled jobs; Tessryx hosts them on your own domain. No code generated, nothing to deploy.

Nippy is drag-and-drop hosting (nippy.host) with an MCP server: connect it and your assistant can publish HTML, folders of photos, or file downloads to a live *.nippy.site URL — and keep editing the site in place at the
MCP server connecting to Kubernetes
Comments