Choose a deployment path, then keep control of the result.

MCP

Connect the hosted endpoint.

Sitedropper is available at https://mcp.sitedropper.com/mcp. Add it to the client you use, reload the client, then sign in and approve scoped access in your browser on the first tool call.

Claude CodeCodexCursorAntigravityPi

Claude Code

Run this command from a terminal where Claude Code is available.

1. Add the hosted endpoint.
2. Restart Claude Code if it is already open.
3. Approve Sitedropper in your browser on first use.

Full setup guide →

TerminalCopy Terminal code

claude mcp add --transport http sitedropper https://mcp.sitedropper.com/mcp

Codex

Add this entry to your Codex configuration file.

1. Add the configuration.
2. Restart or reload Codex.
3. Approve Sitedropper in your browser on first use.

Full setup guide →

~/.codex/config.tomlCopy ~/.codex/config.toml code

[mcp_servers.sitedropper]
command = "npx"
args = ["-y", "mcp-remote", "https://mcp.sitedropper.com/mcp"]

Cursor

Merge this into Cursor’s project MCP configuration.

1. Add the JSON configuration.
2. Reload Cursor.
3. Approve Sitedropper in your browser on first use.

Full setup guide →

.cursor/mcp.jsonCopy .cursor/mcp.json code

{
  "mcpServers": {
    "sitedropper": {
      "url": "https://mcp.sitedropper.com/mcp"
    }
  }
}

Antigravity

Choose the CLI or IDE path that matches how you run Antigravity.

Both paths use the hosted endpoint and the same browser approval flow.

Full setup guide →

CLI

Run this command, then authenticate Sitedropper from the interactive MCP manager.

TerminalCopy Terminal code

agy mcp add sitedropper https://mcp.sitedropper.com/mcp

An Unauthorized status immediately after the add command means Sitedropper was saved and still needs OAuth approval.

1. Start agy, enter /mcp, select sitedropper, and choose Authenticate.
2. Approve Sitedropper in the browser.
3. Copy the browser’s code into the dedicated CLI authentication prompt, then check /mcp again.

IDE

Merge this JSON into Antigravity’s global or workspace raw MCP configuration.

~/.gemini/config/mcp_config.jsonCopy ~/.gemini/config/mcp_config.json code

{
  "mcpServers": {
    "sitedropper": {
      "serverUrl": "https://mcp.sitedropper.com/mcp"
    }
  }
}

1. Reload Antigravity, then open Agent Settings → Customizations.
2. Click Authenticate beside Sitedropper and approve access in the browser.
3. Copy the browser’s code into the settings panel, then click Submit.

Pi

Pi needs an MCP adapter first. Review its third-party source before granting it system permissions.

Pi does not include MCP in core. This is a provisional third-party adapter path, not a first-party Sitedropper package.

1. Review and install the adapter.
2. Add the shared MCP configuration.
3. Restart Pi, then approve Sitedropper in your browser.

Full setup guide →

Install adapter, then add .mcp.jsonCopy Install adapter, then add .mcp.json code

pi install npm:pi-mcp-adapter

# .mcp.json or ~/.config/mcp/mcp.json
{
  "mcpServers": {
    "sitedropper": {
      "url": "https://mcp.sitedropper.com/mcp"
    }
  }
}

On first use, your client opens Sitedropper in a browser. Sign in and approve access there; never paste approval codes or tokens into a prompt.

Make the first deployment safe.

For static front ends, build locally before you package the project. Ask the agent to upload the built output, use Draft visibility, and wait for the deployment to finish through Analyze, Build, and Deploy. A successful result returns the live URL.

Deploy this project with Sitedropper. Build it locally first if it is a static front end, keep the deployment Draft, poll the operation until it finishes, and give me the live URL.

Upload a ZIP from the dashboard.

ZIP upload is the direct browser workflow. For a prebuilt static project, put the contents of the output directory at the archive root so index.html is immediately available. A hand-authored site may instead contain one standalone .html file; Sitedropper uses it as the home page when index.html is absent. Keep secrets out of the archive. This browser workflow does not expose runtime environment or command controls in Project settings.

ZIP deployment at a glance

01

Build and ZIP locally

Build and packageReady

Site

↓

ZIP

✓ Site packaged as project.zip

Run the production build, check the result in your browser, then package the deployable project with the site files at the archive root.

Site → project.zip

02

Upload directly to Sitedropper

Direct ZIP uploadUploading

ZIP

→

Sitedropper

✓ Secure browser handoff

Drop the archive into your project. No agent connection or repository import is required.

project.zip → secure upload

03

Sitedropper prepares your site

DeploymentComplete

AnalyzeComplete

BuildComplete

DeployComplete

Progress100%

Sitedropper checks the project, builds what it needs, and makes it available at an HTTPS URL.

Check → Build → Deploy

04

Share it when it is ready

ShareReady

✓ Sitedropper URL readypreview.apps.sitedropper.com

Optional custom domainwww.yourdomain.comSupported customer-owned subdomains

Review the Sitedropper URL, then choose the sharing level that fits your audience. Eligible accounts can also connect a supported custom subdomain.

URL ready · sharing is your choice

Complete the four dashboard actions.

Create a Draft project, upload the archive, wait for the deployment to finish, and inspect the result before changing visibility.

The dashboard screenshots use fictional project and account data. Yellow outlines identify the documented controls.

1. 01

   Create a project

   Open Projects, choose New project, enter a name, and select the highlighted Create project action. New projects begin as Draft.

   

2. 02

   Upload the ZIP

   Open the project’s Upload and deploy card, then select the highlighted Choose ZIP control or drop the archive into the same area.

   

3. 03

   Open the deployed site

   Wait for Analyze, Build, and Deploy to finish. Then use the highlighted Open Sitedropper site action to review the generated URL.

   

4. 04

   Change visibility to Public

   Open Visibility, select the highlighted Public option, review the access warning, and save the project changes only when anonymous access is intentional.

   

Dashboard screenshot

Dashboard action

Close ×

Use REST for a scripted deployment flow.

Create a scoped REST API credential from Profile, store it securely, prepare an archive upload, keep the returned operation ID, and poll it until the deployment finishes. Dashboard sessions and MCP credentials are separate from REST API credentials.

curl -X GET "https://api.sitedropper.com/api/v1/me" \
  -H "Authorization: Bearer $SITEDROPPER_API_TOKEN"

curl -X POST "https://api.sitedropper.com/api/v1/deploy" \
  -H "Authorization: Bearer $SITEDROPPER_API_TOKEN" \
  -F "[email protected]" \
  -F 'metadata={"name":"studio","visibility":"draft"};type=application/json'

Validation and service errors normally return 400; missing or invalid authentication returns 401; entitlement restrictions return 403; missing resources return 404.

Current runtime support and limits.

• Static HTML, CSS, and JavaScript, including built static output
• Node.js projects including React, Vite, Express, Fastify, Next.js, and NestJS
• Python projects including Flask, FastAPI, and Django
• Projects with an existing Dockerfile

Framework ZIP walkthroughs.

Do not assume databases, persistent volumes, cron jobs, background workers, multi-container applications, multi-region deployment, runtime log retrieval, or rollback controls are available. Starter, Plus, and Pro accounts can connect supported customer-owned subdomains; the generated Sitedropper URL remains available on every plan.

Troubleshooting a deployment.

Start with the deployment step: project checks catch archive-shape problems, build output identifies dependency or command issues, and deployment status shows the final handoff. For static projects, confirm that the selected root contains index.html or one standalone .html file.

For detailed current behavior, use the stable, categorized API reference.