blitz.cloud
cloud.blitzPublished by blitz.cloudOfficial publisherv1.0.0Updated Oct 27, 2026
Host apps in the EU from your assistant: App Store, Docker, GitHub, databases, logs.
Overview
Remote blitz.cloud MCP server that lets an assistant deploy and manage EU-hosted apps, databases, DNS and logs from the chat.
- What you can do
- List, inspect, deploy, restart, pause, resume and delete apps from the App Store, a Docker image or a GitHub project
- Search the App Store and Docker Hub for images to install
- Rebuild GitHub projects and review builds and failure reasons
- Create, connect, restart and delete PostgreSQL, MariaDB and Redis databases
- List, read, set and remove app environment variables, and manage DNS records and private networks
- Tail app logs and check plan usage
- When to use it
- Useful when you want to put an app online, attach a database, fix a broken deployment or read logs without leaving the assistant, on a blitz.cloud account with a claimed address.
- Requirements
- A blitz.cloud account with its address claimed; the remote endpoint is your personal server address shown on the AI tools page. Sign-in is OAuth in the browser, or an API key sent in the Authorization header for scripts. Changes require a confirmed email address.
Installation
In SourceWeft
- Open blitz.cloud in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/cloud.blitz%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"blitz-cloud": {
"type": "http",
"url": "https://mcp.blitz.cloud/mcp"
}
}
}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 or a GitHub project, 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>.blitz.cloud, 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
Then run /mcp, pick blitz and sign in.
Claude Code (plugin)
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
See examples/codex for a ready-made config.toml and an AGENTS.md with the deploy steps.
Cursor: add to ~/.cursor/mcp.json
VS Code: add to .vscode/mcp.json
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."
- "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
Every tool with its arguments is in docs/tools.md. The server's own list, which is always current, is on the AI tools page in the dashboard.
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:
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.
- Connecting a Tailscale or WireGuard network isn't a tool. It needs a secret or a config file, which belongs in the dashboard rather than in a chat.
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.
Source: README.md at commit 8536f4b
Tools
0Version history
1- v1.0.0LatestSep 25, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Other Blitz integrations
Blitz Wings
Published by GitHub account scheur
A remote MCP server for AI-generated presentations and reports, producing slides, diagrams, PPTX export and a live preview app.
Blitz
Published by GitHub account blitzdotdev
Lets an AI assistant drive iOS and macOS app release work through a native macOS app: simulators, in-app purchases, screenshots, TestFlight, and App Store…