Cursor hosting with a permanent URL and a real backend.
Your Cursor preview URL expires — get a permanent URL, with a real backend (database, functions, email) the app you built in Cursor actually needs. Publish to shiply.now in a single call: no account to start, a flat bill, and re-publishing updates the same URL.
Publish my site to shiply.now and give me the live URL. Read https://shiply.now/skill.md first — it is the live API map. Before publishing, look for .shiply.json and existing Shiply credentials; if MCP is connected, call whoami. If no valid credential is available, publish anonymously immediately — never block the first live URL. Then show me Shiply’s REAUTH_REQUIRED verification link so I can claim it. If I choose email reconnect, request the six-digit code, wait for me to paste it, verify it, and securely save the returned API key. In a cloud sandbox, use the raw HTTP API only (no npm or install scripts). Follow Shiply’s JSON errors and docs pointer; don’t guess.
No credit card · No account to start · Live at a real URL in one call
From Cursor to a permanent URL
Three steps, all driven by the agent you already have open.
Connect or paste
Add the shiply MCP server at https://shiply.now/mcp, or paste the publish prompt straight into Cursor's chat.
Cursor publishes
The agent publishes your built app in one call — via the publish_site MCP tool, the shiply CLI, or a raw POST to /api/v1/publish.
A permanent, claimable URL
The first publish returns a live <slug>.shiply.now URL instantly. Anonymous for 24 hours, claimable in one click, and re-publishing updates the same slug.
Want the click-by-click version? See the step-by-step publish guide →
A permanent URL — with the backend static hosts skip
Static-only hosts serve files and stop. shiply gives the Cursor app a real backend, in the same one call.
Database, functions, and email — not just files
The app you built in Cursor usually needs more than static files. shiply gives it a Cloudflare D1 database on every plan, Neon Postgres on Developer, Workers Lite edge functions for dynamic endpoints, and a per-site inbox so forms can receive email — the part static-only rivals leave out.
- D1 on every plan, Neon Postgres on Developer
- Workers Lite functions for dynamic endpoints
- A per-site inbox for form and contact email
One call, three ways to make it
However Cursor reaches out, the result is the same: a permanent URL in a single call. Use the shiply MCP server, the CLI (npm i -g shiply-cli, then shiply publish ./dir), or a raw POST /api/v1/publish. Re-publishing the same site updates the same URL — never a new one.
- MCP: the publish_site tool at https://shiply.now/mcp
- CLI: npm i -g shiply-cli, then shiply publish ./dir
- HTTP: POST /api/v1/publish — no token for the first site
Why shiply for Cursor projects
The backend is the difference versus static-only hosts — real, factual, on the plans below.
Real databases
Cloudflare D1 on every plan, with Neon Postgres on Developer — real SQL data, not just static files.
Edge functions
Workers Lite functions run dynamic endpoints at the edge. No server to provision or keep running.
Per-site inbox email
Every site gets its own inbox, so a form or contact endpoint can receive email without a third-party service.
Custom domains
Point your own domain at any site. DNS is provisioned through Cloudflare and SSL is issued for you.
No account to start
The first publish needs no sign-up. You get a live URL instantly, valid for 24 hours, claimable to keep forever.
Flat price, no meter
Flat $0 / $8 / $24 a month with no usage meter. A viral day moves your traffic, not your invoice.
Re-publish, same URL
Push an update from Cursor and the same URL refreshes — no new link to pass around.
Instant SSL
Every site is served over HTTPS from the moment it is live — on the shiply.now slug and on your custom domain.
What Cursor does well
Cursor is a strong AI code editor — it is where the app gets built, edited, and made ready to ship.
Cursor is excellent at writing and refining the app itself — editing across a codebase with the model in the loop and running the build. shiply.now handles the other half: it gives what Cursor builds a permanent home with a real backend, so the two fit together in a single call.
Cursor hosting — common questions
How do I host an app I built in Cursor?
Have Cursor publish to shiply.now in one call. Add the shiply MCP server at https://shiply.now/mcp and Cursor gets a publish_site tool; or run the CLI (npm i -g shiply-cli, then shiply publish ./dir); or POST to /api/v1/publish. Each returns a permanent <slug>.shiply.now URL, and no account is needed to make the first site. For the step-by-step publish flow, see the guide at /host-your-cursor-project.
Does a Cursor preview URL expire?
A local preview or a temporary sandbox URL is not permanent hosting. A shiply.now URL is: the first anonymous publish is live for 24 hours, and one click claims it to keep it forever on a free account. Re-publishing updates the same slug in place, so the link you share never changes.
Can a Cursor app have a real backend on shiply?
Yes. Static-only hosts stop at files. shiply gives the app you built in Cursor a real backend: a Cloudflare D1 database on every plan, Neon Postgres on the Developer plan, Workers Lite edge functions for dynamic endpoints, a per-site inbox for email, and custom domains through Cloudflare.
What does Cursor hosting on shiply cost?
A flat price with no usage meter: $0 on Free, $8 a month on Hobby, $24 a month on Developer. The number on the card is the number you pay whether the app gets ten visitors or ten thousand on its best day — no per-request billing and no surprise spike.
Host your Cursor app on a permanent URL.
No account needed. A real backend on a flat bill, live in a single call.