Back to Browse

Blitz Cloud MCP Server

Developer ToolsModerate6.0MCP RegistryRemote
Free

Server data from the Official MCP Registry

Host apps in the EU from your assistant: App Store, Docker, GitHub, code without GitHub, databases.

About

Host apps in the EU from your assistant: App Store, Docker, GitHub, code without GitHub, databases.

Remote endpoints: streamable-http: https://mcp.blitz.cloud/mcp

Security Report

6.0
Moderate6.0Moderate Risk

Valid MCP server (4 strong, 1 medium validity signals). 5 known CVEs in dependencies (0 critical, 3 high severity) Imported from the Official MCP Registry.

Endpoint verified · Requires authentication · 6 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Found in Source Code

Found by scanning the linked source code. This listing connects to a hosted endpoint, so none of this runs on your machine: it describes what the server software does where it is hosted.

env_vars

Applies to the server that hosts this plugin, not to your machine.

HTTP Network Access

Connects to external APIs or services over the internet.

How to Connect

Remote Plugin

No local installation needed. Your AI client connects to the remote endpoint directly.

Add this to your MCP configuration to connect:

{
  "mcpServers": {
    "cloud-blitz-mcp": {
      "url": "https://mcp.blitz.cloud/mcp"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

blitz.cloud MCP server

Host apps by asking your AI assistant.

blitz.cloud is a hosting platform in the EU with a free plan. Its MCP server lets Claude, ChatGPT, Cursor, VS Code and any other MCP client do what you can do in the dashboard: put an app online from the App Store, a Docker image, a GitHub project or code your assistant just wrote, give it a database, change its settings, and read its logs when something goes wrong.

Ask "put Uptime Kuma online at uptime" and your assistant installs it from the App Store under uptime.<your name>.prod.page, with HTTPS, and tells you when it answers.

This repository has the setup for each client, examples for scripts, the tool reference, and how sign-in and permissions work. The server itself is hosted by blitz.cloud, so there is nothing here to install or run.

Connect in one minute

You need a blitz.cloud account with its address claimed. Sign up for free if you don't have one. Your server address is https://mcp.blitz.cloud/<your name> and is shown on the AI tools page.

Most clients sign in with your blitz.cloud account: you add the address, a browser window opens, you sign in and allow the app. There is no key to copy.

Claude (web and desktop)

Settings → Connectors → Add custom connector. Paste your server address, click Connect and sign in.

Claude Code

claude mcp add --transport http blitz https://mcp.blitz.cloud/<your name>

Then run /mcp, pick blitz and sign in.

Claude Code (plugin)

/plugin marketplace add blitzworks-io/blitz-cloud-mcp
/plugin install blitz-cloud@blitz-cloud-mcp

This also adds a skill that knows how to deploy an app and give you its address.

Codex: add to ~/.codex/config.toml, then run codex mcp login blitz

[mcp_servers.blitz]
url = "https://mcp.blitz.cloud/mcp"
auth = "oauth"

See examples/codex for a ready-made config.toml and an AGENTS.md with the deploy steps.

Cursor: add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "blitz": { "url": "https://mcp.blitz.cloud/<your name>" }
  }
}

VS Code: add to .vscode/mcp.json

{
  "servers": {
    "blitz": { "type": "http", "url": "https://mcp.blitz.cloud/<your name>" }
  }
}

ChatGPT and other clients: add a connector or remote MCP server with your server address and sign in when asked.

Ready-made files are in examples/.

Things to ask

  • "What do I have running, and is anything broken?"
  • "Put Vaultwarden online at vault and tell me when it's up."
  • "Deploy my GitHub repo acme/shop at shop, with a PostgreSQL database."
  • "Put the app we just built online at todo. I don't have GitHub."
  • "My blog stopped working. Look at its logs and tell me why."
  • "Set SMTP_HOST on the blog to smtp.example.com."
  • "Add a TXT record for _dmarc so my mail provider can verify me."
  • "How much of my plan am I using?"

What your assistant can do

ToolsWhat they do
apps_*List apps, show one, deploy from the App Store, a Docker image, a GitHub project or code sent in the chat, change name, address, port or nightly updates, restart, pause, resume, delete
apps_source_*Read, change and download the code of an app kept at blitz.cloud, or get a one-hour token to git push it
store_*Search the App Store and Docker Hub
builds_*Build an app's code again, list its builds and why one failed
dbs_*List, create, connect to an app, restart and delete PostgreSQL, MariaDB and Redis databases, and open one to your own computer over your private network
env_*List, read, set and remove an app's environment variables
domains_*List, add and remove DNS records under your address
network_*See your private networks and make an app private or public
logs_tailThe last lines an app printed, or what it printed before its last restart
usage_getYour plan and how much of it is used

That's the short version. All 195 tools with their arguments are in docs/tools.md. The server's own list, which is always current, is on the AI tools page in the dashboard.

Put code online without GitHub

Your assistant can host an app it wrote for you even if you have no GitHub account. blitz.cloud keeps the code, builds it from the Dockerfile at the top of the project and runs it under your address.

  • In a chat client such as Claude or ChatGPT, the assistant sends the files inside a tool call with apps_deploy_code, up to 4 MB at a time. Later changes go in with apps_source_write. A new chat can pick up where the last one stopped, because it reads the saved code back with apps_source_list and apps_source_read.
  • Agents with a shell, such as Claude Code, Codex or Cursor, can use git. apps_source_git_access returns an address on git.blitz.cloud and a token that works for one hour, for that one app. Pushing the app's branch saves a new version and builds it.
  • You can take the code with you at any time: apps_source_download returns a link to a ZIP of any saved version.

Passwords and keys never go in as files: the server refuses .env and key files, and the values go into the app's settings instead. Each app keeps 50 MB of code and its last 20 versions on the free plan, 500 MB and 100 versions on Pro.

A plain website (HTML, CSS, pictures, nothing that runs on a server) is simpler still: apps_site_upload_start and apps_deploy_site put a ZIP of it online.

You stay in control

  • Deleting, restarting and pausing ask you first. If your client can show a question from the server, the question goes to you and the assistant cannot answer it. Other clients have to repeat the call with confirm: true, which a well-behaved assistant only does after checking with you.
  • The consent screen tells you who is asking. Claude Code and VS Code are recognised by their publisher's domain. Any other app registered itself, and the page says its name is unchecked.
  • Disconnect works immediately. Every app you sign in is listed under Connected apps on the AI tools page. Disconnecting it stops the next request, not the next hour.
  • Your plan is the limit. An assistant can't put more apps online than you could, and it can't reach the dashboard's own API.
  • Everything is on record. Each change is logged under the app or key that made it.

How this works in detail, and how to report a security issue, is in docs/security.md and SECURITY.md.

Scripts and clients without sign-in

Make an API key on the AI tools page and send it in the Authorization header:

claude mcp add --transport http blitz https://mcp.blitz.cloud/<your name> \
  --header "Authorization: Bearer $BLITZ_API_KEY"

A key is shown once, only its hash is stored, and you can have five. examples/python and examples/typescript list your apps with the official MCP SDKs.

Limits

  • 120 calls a minute for each key or connected app, 20 of which may change something.
  • Changes need a confirmed email address.
  • Adding a WireGuard device or uploading your own WireGuard config happens in the dashboard, because those hold a private key that doesn't belong in a chat. Tailscale works from the chat: network_connect_tailscale returns a link you sign in with.

Links

License

The examples and documentation in this repository are released under the MIT License. The blitz.cloud service is covered by its own terms.

Reviews

No reviews yet

Be the first to review this server!