Publish the folderCursor just wrote
Add dplooy's MCP server to Cursor and the agent can deploy the project on your disk without leaving the editor. Prefer to do it yourself? Drop the build folder into the dashboard instead.
The gap between working locally and being online
Cursor is excellent at writing the site. Getting it in front of someone still usually means a detour through a dashboard, a CLI or a git remote.
The usual detour
- localhost:5173 works for exactly one person
- Sharing means a screen recording or a git push first
- Every hosting provider wants its own CLI and login
- A throwaway prototype needs a repo it doesn't deserve
- Nothing tells you whether anyone opened it
With dplooy connected
- Cursor deploys the folder it just built, from the chat pane
- A real HTTPS URL comes back in the same reply
- No repo needed for something you're throwing away next week
- Analytics, SEO tools and a visual editor come with it
- Redeploy the same project and the URL never changes
Connect it once, deploy forever
Get an API key
In dplooy, go to Settings → API Keys and create one. It starts with dpk_live_. The local MCP server uses it to act on your account, so treat it like a password and keep it out of anything you commit.
Add the server to Cursor
Cursor reads MCP servers from ~/.cursor/mcp.json for every project, or .cursor/mcp.json inside one project. Add an entry named dplooy that runs npx -y @dplooy/mcp-server with DPLOOY_API_KEY in its env block — the same shape every other MCP server in that file uses.
Ask Cursor to deploy
"Deploy this folder to dplooy as my-portfolio." The local server runs on your machine, so unlike a remote connector it can read the files already on your disk and push the whole folder up — no zipping, no uploading by hand.
Keep going
Cursor gets the live URL back and can keep working: change the copy, redeploy to the same project, attach a form endpoint, turn on the chatbot. The URL stays put and the analytics keep counting.
Deploy the build output, not the source
Dplooy serves static files. A folder with vite.config.ts and a src directory is source code — we reject it with an explanatory message rather than hosting a broken site. Run npm run build first and deploy dist (or out for a Next.js static export, build for Create React App). Tell Cursor that once and it will remember to build before deploying.
What the deployed project gets
Every site gets the same treatment whether a human uploaded it or an agent did.
Your own subdomain
yourname.dplooy.com instead of a link that names somebody else's product. Point a custom domain at it on Pro.
Free SSL, always on
Every site is served over HTTPS with a certificate we manage. Nothing to buy, configure or renew.
Real analytics
Views, unique visitors, countries, referrers and devices — for the whole site, exported as CSV whenever you want it.
Findable in search
robots.txt and sitemap.xml are generated for you, and the SEO analyser scores 25 checks and tells you what to fix.
Editable after publishing
Change text, images and colours on the live page with the visual editor, on any plan. Pro adds a full in-browser code editor.
Private when you need it
Password-protect the whole site on Pro, or put an email gate in front of it and collect the addresses.
Frequently asked questions
Do I have to use MCP?
No. Click Choose folder on the dashboard and pick your build output — that's the whole flow, and it needs no API key at all. MCP is worth setting up when you deploy often enough that leaving the editor gets annoying.
Why the local MCP server rather than the remote one?
They expose the same tools, but the remote server can't see your disk. The local one runs on your machine via npx, which is what lets Cursor deploy a folder that already exists locally instead of asking you to paste file contents into the chat.
Can Cursor do more than just deploy?
Yes. The same tool set creates projects, updates files on an existing site, uploads images to your media library, creates form endpoints and booking pages, and configures the AI chatbot. It's the full platform, not a deploy button.
Is my API key safe in mcp.json?
It's a plain file on your machine, so treat it like any other credential: keep it in the global ~/.cursor/mcp.json rather than a project file you might commit, and add .cursor/ to .gitignore if you use the project-scoped version. You can revoke a key from Settings → API Keys at any time.
Does this work in Windsurf, Claude Code or VS Code?
Yes. Any MCP-capable client can use the same server. Claude Code takes it as a one-line claude mcp add command; Claude Desktop and Windsurf use the same JSON block as Cursor. claude.ai and ChatGPT connect to the remote server over OAuth instead, with nothing to install.
Is it free?
Yes, on the free plan: 3 hosted projects, free SSL and analytics. Free-plan sites are removed after 3 days. Plus and Pro sites stay up indefinitely, and Pro adds custom domains and password protection.
Can I connect a git repo instead?
Yes. Click Deploy from GitHub, pick the repo and branch, and turn on Deploy on every push. If the repo is framework source rather than built output, Dplooy detects the framework from package.json and offers to commit a workflow that builds it on GitHub and deploys the result.
Other ways to get there
Hosting for the other AI builders
Same platform, same free plan. Whichever tool wrote the site, it ends up on an address you own.
Stop leaving the editor to ship
Create a free account, paste one block into mcp.json, and ask Cursor to deploy.