Deploy Static Sites Directly from Cursor and Windsurf via Model Context Protocol
DropTheHassle provides a remote Model Context Protocol server enabling Cursor and Windsurf agents to publish static builds to live HTTPS URLs. The initial deployment requires no API keys or accounts, returning an active link and a 7-day claim token.
Impact: Medium
Why it matters
Close your agentic development loop by allowing your IDE assistant to build, verify, and host live prototypes without switching windows.
TL;DR
- 01Cursor and Windsurf agents can deploy static sites directly using an open remote MCP endpoint without signing up.
- 02Unclaimed preview deployments stay live for 7 days under dropthehassle.app with automatic noindex search tags.
- 03Asset directories requiring heavy media uploads should use the local stdio runner to avoid inline MCP payload bloat.
Key facts
- Unclaimed TTL
- 7 days
- Local ZIP upload limit
- 100 MB
- Domain pricing
- €19/yr (EU) / $19/yr (Global)
- Supported stacks
- Static HTML/JS only (No Node/Python/PHP)
Closing the Agentic Build Loop
When developing in Cursor or Windsurf, agents regularly handle project generation, dependency resolution, and build scripts, only to stop once output files land in dist/. Integrating an Model Context Protocol (MCP) server extends the agent's capabilities to deployment execution. The initial deployment requires no pre-configured API keys or registered account tokens.
Editor Configuration
For Cursor, configure the remote server inside .cursor/mcp.json or globally in ~/.cursor/mcp.json:
{
"mcpServers": {
"deploy": {
"url": "https://dropthehassle.com/mcp"
}
}
}Windsurf Cascade uses mcp_config.json with a serverUrl field, while Devin Local leverages the stdio command npx -y dropthehassle-mcp via .devin/mcp_config.local.json. Once loaded, prompting the agent with Build the site and publish the dist folder with DropTheHassle triggers deploy_site.
Limits and Safety Constraints
- Payloads: The remote server receives files inline as UTF-8 or base64 data. Large asset directories must use the local stdio runner (
dropthehassle-mcp), which supports zip packages up to 100 MB. - Lifespan: Unclaimed deployments are served with
noindex, nofollowand expire after 7 days. - Spend Guards: The agent can inspect custom domains using
search_domain, but purchasing requires manual checkout via a payment link (€19/yr in EU, $19/yr internationally).
Try it in 2 minutes
{
"mcpServers": {
"deploy": {
"url": "https://dropthehassle.com/mcp"
}
}
}json
✓ When to use
- Instant vibe coding prototyping when sharing working web links from IDE conversations.
- Verifying built frontend bundles on actual mobile viewports without setting up Vercel or Netlify.
- Checking domain availability and cost directly within agent chat prompts.
✕ When NOT to use
- Dynamic backend architectures requiring server-side rendering in Node.js, Python, or Go.
- Enterprise applications bound to strict custom AWS/GCP CI/CD deployment pipelines.
- Codebases with sensitive assets that cannot be exposed on temporary public URLs.
What to do today
- Add the remote MCP server URL to .cursor/mcp.json or Windsurf config.
- Instruct your coding agent to build and deploy the dist directory via DropTheHassle.
- Claim the site using the returned 7-day claim URL before expiration.
Sources