Deploy from Codex, Claude Code, Cursor, and more with SiteDropper MCP

Why deploy from your coding agent

If you are already building in Codex, Claude Code, Cursor, or another agentic coding tool, deployment should not require switching context. SiteDropper MCP lets your agent use deployment tools directly after you approve access.

• The agent can create a SiteDropper project for the app you are editing.
• It can package the local files into a ZIP and upload them for analysis.
• It can start the build and deployment flow, then poll status until the work is complete.
• It can give you the final live URL in the same conversation where you asked for the deploy.

Connect the SiteDropper MCP endpoint

Add the hosted SiteDropper MCP endpoint to your MCP-capable client. Use the code snippets below instead of retyping URLs. Most clients will open a browser approval flow the first time the agent tries to use a SiteDropper tool.

https://mcp.sitedropper.com/mcp

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

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

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

npx -y mcp-remote https://mcp.sitedropper.com/mcp

• Codex: configure mcp-remote in your Codex config.
• Claude Code: add SiteDropper as an HTTP MCP server using the snippet below.
• Cursor: paste the JSON into MCP settings or merge it into .cursor/mcp.json.
• More MCP clients: use the mcp-remote bridge when the client expects a local stdio MCP server.

Approve only the access you need

When your client connects, SiteDropper asks you to sign in and approve the agent grant. Normal deploy access is enough for creating projects, uploading ZIPs, building, deploying, polling operations, and reading build logs.

• Keep public visibility changes separate from normal deploy work.
• Only allow project deletion when you explicitly want the agent to clean up a project.
• Start with draft or private visibility until you have checked the live URL.

Ask the agent to deploy

Use a clear prompt that tells the agent what to deploy and how visible it should be. Copy this prompt into your agent after the MCP connection is approved.

Deploy this project with SiteDropper. Keep it draft/private unless I explicitly ask for password-protected or public visibility. Upload a ZIP, poll the operation status, and give me the live URL when deploy succeeds.

• Ask the agent to run the local build first for Node projects so common errors are caught before upload.
• Ask it to keep track of operation IDs if you want a resumable deployment trail.
• Ask it to summarize build logs if a build fails.

Review the result before sharing

Once the agent returns a URL, open it yourself and smoke test the app. SiteDropper is designed to make the deployment path fast, but you still control when the result is ready for teammates, clients, or the public.