MCP server hosting, both ways round
Two different things go by this name. You might want to put your own MCP server online so your assistant can reach it, or you might want an assistant to run your hosting. Redon3 does both, and the first one is what most people arrive looking for.
Put your MCP server on a public URL
An MCP server that speaks HTTP is just a small web service. A panel gives it a hostname, a certificate, and a process that keeps running.
- Write it in Node.js 20 or Python 3.11. Use the official SDK or anything that serves HTTP. Dependencies install from package.json or requirements.txt when the panel starts.
- Set the panel to web and pick the port. Tell the panel which port your server listens on, from the Startup tab or over MCP.
- Reserve a name. Claim yourserver.redon3.com and it is served over HTTPS with the certificate handled, or point a domain you own at it.
- Add it to your client. Give your assistant the URL and the path you serve MCP on. WebSocket upgrades pass straight through, so streaming transports work too.
The parts you would otherwise set up yourself
- HTTPS on a subdomain, with the certificate managed for you.
- A process that is restarted on failure up to five times.
- Recent logs kept after the process exits, with the exit code.
- Secrets stored as encrypted environment variables, never readable back.
- An isolated container with its own RAM and CPU limit.
- A real terminal in the browser when you need to poke at it.
- A web panel serves one port, so give a separate app its own panel.
Or use our MCP server to run your hosting
Redon3 also runs an MCP server of its own at https://redon3.com/mcp. Add it as a connector in ChatGPT or Claude, sign in with OAuth, and your assistant gets 28 tools on your account: write files, set the runtime and start file, start and restart panels, read crash logs with the exit code, and manage domains.
It cannot delete a panel, cannot spend money, cannot read back a stored secret, and cannot reach anything outside your own panel folder. That is the whole reason it is safe to hand over.
The two uses stack. Plenty of people host their own MCP server on a panel and let Claude deploy and restart that panel over our MCP server.
Common questions
- Can I host my own MCP server on Redon3?
- Yes. Write it in Node.js 20 or Python 3.11, set the panel type to web, tell it the port, and reserve a subdomain. It is served over HTTPS and kept running.
- Do I get HTTPS?
- Yes, on yourserver.redon3.com with no certificate work from you. You can also add a domain you own once its DNS points at us.
- Which transports work?
- Anything you serve over HTTP, including streamable HTTP. WebSocket upgrades are passed through to your process, so socket based transports work as well. A stdio only server will not, since there is no client attached to the container.
- Will it be stopped when idle?
- No. A web or worker panel runs until you stop it or the panel expires. It is restarted on failure up to five times rather than left dead.
- How do I keep API keys out of the code?
- Store them as environment variables on the panel. They are encrypted at rest, and there is no API or tool that reads a value back once it is saved.
- What is the difference from your own MCP server?
- Ours manages Redon3 hosting: panels, files, logs, domains. Yours does whatever you write. They are unrelated except that both speak MCP.