Codex writes the code, Rock8Cloud gives it a starting stack and real hosting, in the EU. In the ChatGPT and Codex apps the answers render as live cards, not walls of text.
What you need#
- ChatGPT on the web or in the desktop app, or Codex, the app or the CLI, signed in with your ChatGPT account.
- A Rock8Cloud account with at least one project. You sign in with GitHub during setup.
Connect the Rock8Cloud MCP to ChatGPT or Codex#
Both reach the same server and end with the same GitHub sign-in.
- Add the server. Open ChatGPT Plugins, select +, then Add custom MCP server. If the option is missing, turn on Developer mode under Settings → Apps → Advanced settings.
- Point it at Rock8Cloud. Name it
rock8cloud, enterhttps://app.rock8.cloud/mcpas the endpoint and pick OAuth. - Sign in. Select Create as a plugin. Rock8Cloud opens in your browser. Sign in with GitHub and approve the access. No API key, no secret in a file.
- Start a new conversation and ask what is deployed.
When Rock8Cloud ships new tools, select Refresh on the plugin to pick them up.
The Codex app and the Codex CLI read the same configuration, so this is a one-time setup for both.
- Add the server. In a terminal:
codex mcp add rock8cloud --url https://app.rock8.cloud/mcpOr add it to ~/.codex/config.toml yourself:
[mcp_servers.rock8cloud]
url = "https://app.rock8.cloud/mcp"- Sign in. Codex opens Rock8Cloud in your browser. Sign in with GitHub, approve the access, and the token stays with Codex.
codex mcp login rock8cloud- Restart the Codex app, or start a new CLI session, so it loads the server and its tools.
What you can do with it#
Every tool, with example prompts, is on the MCP primitives page. Some ideas to start with:
Build a proper prototype from a verified blueprint
Start from a verified repository with a local stack, spend tokens on your idea instead of scaffolding, and get a live URL from the first deploy.
Prototype a team dashboard from a blueprint
Ship your repo with its database
Build, database, env vars and a live URL in one step. Every push redeploys, and your own domain is one more prompt.
Deploy this repo on Rock8Cloud with a Postgres database
Find out why a deploy failed
Build and runtime logs read straight into the chat, so the fix starts from the evidence, not a guess.
Why did the last deploy of the API fail?
Add a database, cache or storage
PostgreSQL, Dragonfly (Redis) or S3 storage, linked into your service as env vars.
Add Redis to the API and link it
Share your work as a page
Reports, previews and summaries get their own rock8cloud.page link, public or password-protected.
Publish this report as a page for the team
Hand a task to a cloud agent
An agent works in its own sandbox with its own copy of the repo and comes back with a pull request and a preview.
Have an agent fix the flaky checkout test
Check what is running
A live dashboard of every service, its uptime, and CPU and memory graphs against the limits.
What is running in production, and is anything close to its limits?
Catch problems before they ship
Critical dependency vulnerabilities and code review findings, with the fix to apply.
Any critical vulnerabilities in my services?
Good to know: deploys come from GitHub, so install the Rock8Cloud GitHub App when asked and push before you deploy. Anything billed is confirmed with you first.
Troubleshooting#
ChatGPT has no Add custom MCP server option. Turn on Developer mode under Settings → Apps → Advanced settings.
ChatGPT does not know about a new Rock8Cloud tool. Select Refresh on the Rock8Cloud plugin and start a new conversation.
Codex says the server needs a login. Run codex mcp login rock8cloud and finish the browser sign-in. A new login also fixes a connection that stopped working after a long break.
Codex has no Rock8Cloud tools. Restart the Codex app or start a new CLI session, and check that codex mcp list shows rock8cloud.
The answer is about the wrong organization. Name the organization in the question.
The Codex CLI shows text, not cards. That is expected. The cards render in the ChatGPT and Codex apps.
Next: control Rock8Cloud from Claude · talk to your codebase from your phone · debug a failing deploy from your agent.
