# Cursor hosting for AI-generated static websites

> Give Cursor a scoped StaticX token so it can build, validate, and deploy static sites safely.

Canonical: https://staticx.site/cursor-hosting

## Deploy from the editor context

Cursor already sees the project files, so it can build, inspect, and publish the output when StaticX MCP or CLI access is configured.

## Make actions explicit

A Cursor agent should explain what it will modify, validate the output, deploy a new version, and return logs or API errors.

## Keep tokens out of source

StaticX tokens belong in environment variables or MCP config, never in committed files or prompt text.

## Connect Cursor to a StaticX deploy workflow

Use Cursor for code changes and StaticX for the controlled publish step.

1. **Configure MCP or CLI** — Install staticx-mcp-server or the CLI and provide STATICX_API_TOKEN through the local environment.
2. **Ask for a safe build** — Have Cursor build the project, verify index.html and 404.html, and list changed files before deployment.
3. **Deploy a version** — Let Cursor call StaticX with the scoped token and report the new release, URL, and logs.

## Cursor is strongest when deployment is a tool, not a guess.

Cursor can edit the repo and understand the local file structure, but publishing needs a strict contract so the agent does not ship the wrong folder or expose secrets.

StaticX gives Cursor a bounded action surface: create or update a site, deploy files, inspect logs, manage domains when permitted, and keep every production change visible.

## Cursor agent safety

- **Show changed files** — Ask Cursor to summarize modified files before deploy so accidental edits are visible.
- **Use project-scoped tools** — Prefer a site token or project ID when one Cursor workspace maps to one StaticX site.
- **Return exact errors** — If deployment fails, the agent should return the API error rather than inventing success.

## FAQ

### Can Cursor deploy directly from my repo?

Yes, with StaticX MCP or CLI configured and a scoped token available in the local environment.

### Should Cursor choose the deploy folder automatically?

It can infer it, but your instruction should require verification of the output root before deploy.

### Can Cursor roll back a release?

Only if the token has rollback permission and the prompt explicitly asks for rollback after showing the target version.

### How do I keep Cursor from leaking tokens?

Store tokens in MCP env config or shell environment and never ask Cursor to print the token value.

[View on staticx.site](https://staticx.site/cursor-hosting)