How to set up SiteDropper MCP for your coding agent

Start with the hosted SiteDropper MCP server

You do not need to install a deployment server inside your application. SiteDropper hosts the MCP server for you. Your coding agent connects to the hosted endpoint below, you approve access, and then the agent can deploy your local project through SiteDropper.

https://mcp.sitedropper.com/mcp

• Use this when you want an agent to package and upload your project instead of manually creating the ZIP yourself.
• Keep the project in draft or private visibility until you verify the live URL.
• Use an existing SiteDropper beta account when the approval flow asks you to sign in.

Set up Codex

Codex can connect through mcp-remote. Add the TOML below to your Codex config so Codex launches the bridge when it needs deployment tools.

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

• Start a new Codex session after updating ~/.codex/config.toml.
• Approve the SiteDropper browser flow the first time Codex calls a deployment tool.

Set up Claude Code

Claude Code can connect to the hosted SiteDropper MCP endpoint as an HTTP MCP server. Run the command below once, then ask Claude to deploy the current project with SiteDropper and approve the browser sign-in flow when prompted.

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

• Return to Claude Code after approving SiteDropper access in the browser.
• Ask Claude to upload a ZIP, poll operation status, and return the live URL.

Set up Cursor

In Cursor, add SiteDropper as an MCP server in settings or merge the JSON below into your .cursor/mcp.json file. Once connected, Cursor can use the SiteDropper tools from the same workspace where your app lives.

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

• Use the server name sitedropper so it is easy to reference in prompts.
• Ask Cursor to deploy the current workspace and keep visibility private until you review it.

Set up more MCP clients

Other MCP-capable clients can use the same hosted endpoint and OAuth approval flow. Use the bridge command below when your client expects a local stdio MCP server.

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

• Use mcp-remote when the client expects a local stdio MCP server.
• Use the hosted URL directly when the client supports remote HTTP MCP servers.
• After setup, run a small Hello World deploy to verify the connection before relying on it for important projects.

Use a deployment prompt that protects visibility

A good first prompt is below. It keeps the app draft/private by default unless you explicitly ask for password-protected or public visibility, and asks the agent to poll status until SiteDropper returns a URL. For Node projects, also ask the agent to run the local build before uploading.

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. For Node projects, run the local build before uploading.