Deloc documentation
Deloc turns anything you build on your machine into a shareable URL. This guide covers the CLI, the MCP server for AI coding tools, every deploy option, server-side Actions, and scheduled data refresh pipelines from BigQuery and other warehouses.
What is Deloc
You build something locally — a dashboard, a prototype, a one-pager. You want to show it to a teammate without spinning up infrastructure, buying a domain, or configuring a build pipeline. Deloc publishes it to a URL in one command.
Every project with an index.html can ship. You do not need a framework, a package.json, or a build system. The free tier gives you three live apps, 100MB storage, 1GB of bandwidth per app per month, and 30-day auto-expiry you can renew.
60-second quickstart
From any project folder:
The CLI auto-detects your framework (Vite, Next, Create React App, static HTML, and more), runs your build command if it needs to, zips the output, uploads it, and prints a live URL. First time? A browser opens for a Google or Microsoft sign-in.
deloc deploy again from the same directory and the app updates in place. The URL, password, and settings stay the same. To publish a second app, pass --name.CLI or MCP: which to use
The CLI and the MCP server expose the same capabilities. Pick by workflow:
- CLI — use from a terminal, a CI pipeline, a shell script, or a build hook. Install once with
npm i -g @deloc/clior call ad-hoc withnpx @deloc/cli <cmd>. - MCP server — use from inside Claude Code, Cursor, Windsurf, or Codex. Say "deploy this to Deloc" and the agent calls the tool. One-line install with
deloc install-mcp.
Both use the same auth token in ~/.deloc/config.json, so logging in via either method works for both. Hit ⌘ K (or Ctrl K) any time in these docs to search.