--- title: "Control Rock8Cloud from Claude" description: "Connect the Rock8Cloud MCP to Claude and control everything without leaving the chat. Start a prototype from a verified blueprint, ship your repo, read logs and hand tasks to cloud agents." seoTitle: "Deploy from Claude: the Rock8Cloud connector" seoDescription: "Connect the Rock8Cloud MCP from the Claude connector directory or with one command in Claude Code. Deploy apps, prototype from blueprints, read logs and start cloud agent sandboxes from any Claude chat." tech: "Claude" icon: claude category: agents pubDate: 2026-08-10 updatedDate: 2026-10-10 image: /how-to/og/claude.png imageAlt: "Control Rock8Cloud from Claude" headerImage: true ctaTitle: "From idea to production" ctaTitleHighlight: "without leaving Claude." ctaSubtitle: "Connect the Rock8Cloud MCP once. Start a prototype from a verified blueprint or ship your repo, then debug and hand tasks to cloud agents from the same chat." ctaIcons: [claude] order: 1 steps: - name: "Open Rock8Cloud in the Claude directory" text: "Go to claude.ai/directory/rock8cloud, or in Claude open Customize, then Connectors, click + and search for Rock8Cloud." - name: "Connect with OAuth" text: "Click Connect. Claude sends you to Rock8Cloud in the browser. Sign in with GitHub and approve the access. There is no API key to copy or store." - name: "Check the connection" text: "Ask Claude what is running in one of your projects. A reply built from live platform data confirms the connector is authorized." faq: - q: "Does Rock8Cloud have an MCP server?" a: "Yes. Rock8Cloud is the platform - Deployment, Code review, Agent sandbox and Logs & Health - and it exposes a remote Model Context Protocol server at https://app.rock8.cloud/mcp so an MCP client can operate it. That includes Claude, Claude Code, Codex, Cursor and Zed." - q: "What can Claude actually do once connected?" a: "Build a prototype from a verified blueprint, deploy a repo with its database, provision PostgreSQL, Dragonfly or S3 storage, read build and runtime logs, publish pages, attach a custom domain, check uptime and usage, pull code review findings, and start a cloud agent that comes back as a pull request." - q: "Can I build a prototype from a chat?" a: "Yes. Ask for a prototype and Claude starts from a verified blueprint: the stack is forked into your GitHub with its database and deployed to a live URL. Claude Code clones it and keeps building, and every push redeploys." - q: "Is Rock8Cloud in the Claude connector directory?" a: "Yes. Rock8Cloud is in the Claude directory at claude.ai/directory/rock8cloud. Open it, click Connect and sign in to Rock8Cloud. Directory connectors work on every Claude plan. On Team and Enterprise plans an owner enables connectors for the organization first." - q: "Does the connector work on my phone?" a: "Yes. Connect it once in Claude on the web or in Claude Desktop, and it is there the next time you open Claude for iOS or Android, with the same tools and the same permissions. Approvals appear in the conversation, so a phone is enough to grant one." - q: "Where does Rock8Cloud run?" a: "Hosted in the EU, built in Czechia. Your services, databases and pages run in EU data centers, and the MCP server Claude connects to runs on the same platform. What Claude sends and receives in the chat is processed by Anthropic under its own terms." - q: "Do I need an API key?" a: "No. The connection uses OAuth. Claude sends you to Rock8Cloud to sign in, and you approve exactly what it may reach." - q: "Can Claude deploy or change things without asking me?" a: "Only if you let it. Each tool has its own permission: automatic, ask every time, or off. Keep deploys, env var writes and agent tasks on ask and you approve each one in the chat." - q: "The connector will not authorize. What should I check?" a: "Finish the browser sign-in rather than closing the tab, and check that you are signed in to the organization that owns the project. On a Team or Enterprise plan, an owner has to enable connectors first. Disconnecting and connecting again under Customize, Connectors starts a fresh OAuth exchange." --- Claude writes the code, Rock8Cloud gives it a starting stack and real hosting, in the EU. ## What you need - **Claude** on the web, Claude Desktop or the mobile app, on any plan. On Team and Enterprise plans an owner enables connectors first. Or **Claude Code** in a terminal. - **A Rock8Cloud account** with at least one project. You sign in with GitHub during setup. ## Connect the Rock8Cloud MCP to Claude Both paths reach the same server and end with the same GitHub sign-in. ### Claude 1. **Open the listing.** Go to [claude.ai/directory/rock8cloud](https://claude.ai/directory/rock8cloud), or in Claude open **Customize → Connectors**, click **+** and search for Rock8Cloud. 2. **Connect.** Click **Connect**, sign in with GitHub and approve the access. No API key, no token in a config file. The connector follows your Claude account to every Claude app, phone included. ### Claude Code ```bash claude mcp add rock8cloud --transport http https://app.rock8.cloud/mcp ``` Then type `/mcp` in Claude Code, pick Rock8Cloud and sign in in the browser. Add `--scope user` to have it in every project on the machine. ## What you can do with it Every tool, with example prompts, is on the [MCP primitives](/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. **Prompt:** 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. **Prompt:** Deploy acme/shop 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. **Prompt:** 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. **Prompt:** 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. **Prompt:** Publish this summary 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. **Prompt:** Have an agent fix the flaky checkout test ### Check what is running The live state of every service, its uptime, and CPU and memory against the limits. **Prompt:** 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. **Prompt:** Any critical vulnerabilities or review findings on my branch? Good to know: deploys come from GitHub, so install the Rock8Cloud GitHub App when Claude asks and push before you deploy. Anything billed is confirmed with you first. ## Troubleshooting **The connector will not authorize.** Finish the browser sign-in rather than closing the tab. Disconnecting and connecting again under **Customize → Connectors** starts a fresh sign-in. **Connect is greyed out.** On a Team or Enterprise plan, an owner has to enable connectors first. **Claude says it has no tools for this.** The chat started before the connector was added, or the tool is turned off in the connector settings. Start a new chat. **Claude answers about the wrong project.** Name the organization or project in the question. **Nothing shows up on mobile.** Connectors sync with the account, not the device. Check the connector shows as connected on the web or in Claude Desktop, signed in to the same account. [ChatGPT and Codex](/how-to/connect-chatgpt-codex), [Cursor, Zed and IntelliJ](https://docs.rock8.cloud/docs/guides/mcp-integration#setup) connect to the same server through their own config. Next: [talk to your codebase from your phone](/use-cases/codebase-from-your-phone) · [let your agent delegate work to cloud agents](/use-cases/delegate-to-cloud-agents) · [debug a failing deploy from your agent](/use-cases/agent-assisted-debugging).