These pages are the copy you paste into an editor, and a browser that calls the tools.
This build is mcp-reference-server 1.0.2. A server you host yourself answers at https://<your-app>.onrender.com/mcp on Render, or https://<app>.<id>.<region>.codeengine.appdomain.cloud/mcp on Code Engine.
~/.cursor/mcp.json or .cursor/mcp.json. stdio through npx, or a hosted URL.
VS Code
User or workspace mcp.json, with type set to stdio or http.
Claude Desktop
A local npx process, or mcp-remote when the desk is hosted.
Windsurf
One global file. A remote server uses serverUrl, not url.
Browser
A page with forms to set the rate limit, list and create users and API keys, search tickets and run any tool. It sends a bearer key or HTTP Basic.
Dashboard
Memory, CPU and disk, tickets, timers, and the event log. It reads them with tools by default, or follows the event stream when the server is publishing.
Chat
Qwen, or another Ollama model, calls the tools. The MCP URL can be this desk or a deployed MCP server.
Command line
npx mcp-reference-server status, call, users, keys, demo apply. A client for a local or hosted server, with --json for scripts.
Settings
Query settings and update_settings. Auth mode, rate limit, and the call trace. Saving needs an admin key.
Open these pages
With the HTTP server running, open /clients/ on that host. The browser page then calls /mcp on the same origin.
cd server npm run http
Or serve this folder by itself. A loopback page may call the server. A page hosted elsewhere is refused until CORS_ORIGINS lists that origin. Opening the file directly sends no usable origin.
cd server/clients python3 -m http.server 8765
Then open http://127.0.0.1:8765/. Point the browser page at http://127.0.0.1:8787/mcp.
The desk log at /log is the call trace. The dashboard follows tickets, timers and system.info either by calling the tools or by listening to the event stream.