How-to · 12 Nov
How-to · 3 min read
How to edit a hosted web app from Cursor or Claude Code
You built an app in a browser builder, it is live with a database and sign-in, and now you want to keep working on it from Cursor or Claude Code. Copying files back and forth between the builder and your editor gets old after the second change. Exporting the code means taking over hosting, secrets and the database yourself. What you want is your usual coding assistant working on the hosted project directly.
01
Why it's hard
Most AI app builders keep you inside their own chat window, so your project lives in one place and your preferred tools live in another. The usual workaround is pushing to a repository and pulling it into your editor, which works but loses the live preview and the hosting that made the builder useful. Wiring a coding agent to a remote project yourself usually means tokens, environment variables and a fair amount of trust in what the agent can touch. And when an agent can write files anywhere, one careless change can land in the live app.
This part describes the usual way. It makes no claims about SpinBuild, so nothing is quoted here.
02
How SpinBuild does it
SpinBuild runs an MCP server that connects Cursor, VS Code, Codex CLI, Claude Code or Grok Build to the projects on your own account. You sign in through the browser and approve access, with no token to copy or variable to set. From then on your assistant can list and create projects, read and edit files, set up the private Postgres database, turn sign-in methods on, read build logs and push to your connected GitHub repository. Every write is saved as a new project version, so the change shows up in the builder and its preview. You keep the live link, the preview and the hosting, and only the place you type changes.
Sign in and approve access to connect Cursor, VS Code, Codex CLI, Claude Code, or Grok Build to your own SpinBuild projects.Quoted from spinbuild.ai
You do not need to copy an access token or configure an environment variable.Quoted from spinbuild.ai
MCP writes save directly as project versions. Review your assistant's proposed changes before allowing it to write.Quoted from spinbuild.ai
03
Step by step
- 1Create a SpinBuild account and a project you own, and sign in to your AI client.
- 2Open MCP in the SpinBuild sidebar and pick your client.
- 3In Claude Code, add the server with the claude mcp add command and authenticate from /mcp.
- 4Approve the connection in your browser after checking which client is asking.
- 5Ask your assistant to list your SpinBuild projects to confirm it works.
- 6Request a change, review what the assistant proposes, then let it write the new version.
04
Tips
Read the proposed change before you allow the write. MCP writes skip the accept or reject step you get in the builder and save straight away as a version.
MCP writes save directly as project versions.Quoted from spinbuild.ai
Only approve a connection request you started yourself. The approval screen shows the client name, but that name comes from the requesting app, so check it was really you. If anything looks off, deny it and start the connection again from your own client.
Only approve a request you started.Quoted from spinbuild.ai
Keep in mind where your code goes. Files your assistant reads through the tools can be sent to the AI provider your client uses, while .env values stay hidden from the read tool.
Project content you request through the tools can be sent to the AI provider used by your client.Quoted from spinbuild.ai
Ask for the database setup in plain words, then ask for the tables in a second step. The setup tool creates the Postgres database and writes the connection string, but it does not create any tables on its own. Describing the data you need in that second request gives the assistant enough to write a sensible schema.
It creates no tables.Quoted from spinbuild.ai
05
Questions
Does my assistant use SpinBuild credits for its own model?
No. Your assistant uses its own model access, but SpinBuild hosting and plan limits still apply.
Your assistant uses its own model access; SpinBuild hosting and plan limits still apply.Quoted from spinbuild.ai
Can a connected assistant reach other people's projects?
No. The connection is limited to projects owned by the signed-in account and gives no admin access.
It does not grant admin access or access to projects owned by other accounts.Quoted from spinbuild.ai
Can the assistant push to GitHub on the free plan?
Not on Starter. Pushing depends on plan permissions, and GitHub sync starts on the $5 Spark plan.
Push saved project code to its connected GitHub repository, subject to plan permissions.Quoted from spinbuild.ai