deplo.sh is a deployment platform designed for AI agents and automated workflows. It lets you deploy static files, HTML sites, and JSON data to a live URL with a single API call — no Git repo, no build step, no config files needed.

How do I use deplo.sh with Claude or Cursor?

Add the deplo.sh MCP server URL (https://mcp.deplo.sh) to your Claude Desktop or Cursor MCP configuration with your API key. Your AI assistant will then have access to deploy, rollback, and project management tools.

Yes, deplo.sh offers a free tier. Visit deplo.sh/pricing for details on plans and limits.

Do I need a Git repository to deploy?

No. deplo.sh does not require Git. You can deploy files directly via the API, SDK, CLI, or MCP server. Just send the file content and get a URL back.

Authentication — Deplo Docs

deplo.sh supports two authentication methods: JWT sessions (web dashboard only) and API tokens (CLI, agents, CI, and scripts).

JWT sessions (web dashboard)

JWT sessions are used exclusively by the web dashboard. JWTs are short-lived (15 minutes) and automatically refreshed using a long-lived refresh token. They are not used by the CLI.

API tokens (`sk_live_`)

The recommended method for agents, CI pipelines, and programmatic access. Tokens are scoped and never expire unless you revoke them.

Creating a token

Via the CLI:

deplo tokens create "My Agent" --scopes deploy
# ✔ Token created (shown once):
# sk_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Via the dashboard: Navigate to Tokens → New Token, select scopes, and copy the token on creation.

Caution: The raw token value is shown only once at creation time. Store it immediately in your secrets manager.

Using a token

Environment variable (recommended):

export DEPLO_KEY=sk_live_xxxxxxxxxxxxxxxx
deplo deploy report.html --project weekly-report

CLI flag:

deplo login --token sk_live_xxxxxxxxxxxxxxxx

HTTP Authorization header:

curl -H "Authorization: Bearer sk_live_xxxxxxxxxxxxxxxx" \
  https://api.deplo.sh/workspaces

Token scopes

Scope	Permissions
`deploy`	Create new deployments
`read`	List projects, deployments, and tokens
`delete`	Archive deployments and delete projects
`admin`	Full access including member and token management

Tokens can be workspace-scoped (access all projects) or project-scoped (access a single project only).

Environment variables

Variable	Description
`DEPLO_KEY`	`sk_live_` token. When set, all commands authenticate with this token.
`DEPLO_API_URL`	Override the API base URL. Defaults to `https://api.deplo.sh`.

Security recommendations

Use the minimum required scope for each token
Rotate tokens regularly for long-running services
Use project-scoped tokens when a process only needs access to a single project
Store tokens in your CI/CD secret store (GitHub Actions secrets, Railway variables, etc.) — never commit them to source control

What's next?

Quickstart — deploy your first file using the CLI
API Tokens — detailed token management (create, revoke, expiry)
REST API — use tokens with the HTTP API directly
Core Concepts — understand workspaces, projects, and scopes

Authentication

On this page