I built CloudHike: a backend your AI coding agent can set up over MCP

My AI agent can write a whole Next.js app in an afternoon. Then it stops and hands the hard part back to me: make a Postgres database, set up a storage bucket, find a Redis instance, add auth, pick an email provider, and copy a dozen connection strings into.env.local without committing any of them.

That's five dashboards, five sets of keys and five bills, and the agent can't help with any of it. I kept losing my momentum at exactly that point, so I built CloudHike.

I run the TubeGuruji YouTube channel, where I make full-stack tutorials. A big part of every tutorial is the "now go sign up for these services" section. Lately most of my building happens with Cursor and Claude Code, and the backend setup has become the slowest part of the whole process. CloudHike is my attempt to fix that for myself, and hopefully for you. I'm building it solo.

CloudHike is a backend-as-a-service built for people who code with AI agents. Each project can have:

It all lives in one dashboard and comes out of one credit balance. Each project is isolated, so one project can never reach another. App hosting is coming soon, but it isn't live yet.

The part I care about most is the remote MCP server. Once you add it to your editor, your agent can do the backend setup itself.

You get the workspace API key from Connect MCP in the dashboard sidebar. Click Copy with key and the snippet comes with your key already filled in.

claude mcp add --transport http --scope user cloudhike https://cloudhike.dev/api/mcp \ --header "Authorization: Bearer icu_your_api_key" Enter fullscreen mode Exit fullscreen mode Then run /mcp inside Claude Code to check that it's connected.

{ "mcpServers": { "cloudhike": { "url": "https://cloudhike.dev/api/mcp", "headers": { "Authorization": "Bearer icu_your_api_key" } } } } Enter fullscreen mode Exit fullscreen mode Open Cursor Settings → MCP and look for the green dot. The MCP docs also have snippets for Codex, VS Code, Windsurf, Gemini CLI and Claude Desktop.

There are a few guardrails I cared about. query_database always runs in a read-only transaction. Writing SQL ( execute_sql ) is Pro-only, runs in a single transaction, and is marked destructive so your editor asks you first. Nothing can be deleted through MCP. Deleting projects and services only happens in the dashboard. Every.env fetch and every SQL write goes to the audit log, and you can revoke the key with one click.

With the server connected, open your app's folder and paste this prompt (it's from the docs):

Use the cloudhike MCP tools to set up CloudHike.dev as the backend for this app.

Read the app first and deploy only the services it needs. Put the.env into the app's git-ignored env file without showing me the values, then read the matching docs with get_docs and write the code that connects each service.

You review the diff and run the app. You still own the code, so read what it changed. The point is that you no longer need five browser tabs.

If your tool doesn't support MCP, there's also a one-prompt flow. You paste a prompt that points the agent at https://cloudhike.dev/prompt.md, together with a token that can only download that project's.env.

Services are billed by the hour from credits. You can set a monthly spend cap in Settings, and if you run out of credits, nothing gets deleted. The full meter rates are on the Plans and billing page.

App hosting (deploy from GitHub, Docker or a template, with an HTTPS address) is the next big piece. CloudHike is new and I'm building it in public, so I'd really like your feedback:

Try it at cloudhike.dev and tell me in the comments what you built, or what got in your way. I read every comment.