NOVA MCP: Versions, Hosting, Analytics & Memory

Docs › NOVA MCP

Versions, hosting, analytics & memory

Beyond building and deploying, your AI tool can look after a project the way you would in NOVA.

Version History

list_versions shows every saved version: its number, what changed, and where it came from (NOVA, NOVA CLI, NOVA MCP or a merge). restore_version puts an older version's files back as a new version, so nothing is lost; it asks you first. The live site only changes when you deploy again.

Hosting

hosting_statusEverything Manage Site, Hosting shows: the kind of app, its size and plan, whether it is live and where, the free hosting window, usage, and the build and start commands.
restart_appStarts the live server app again as it is, with no new build. Use it after set_env so the app reads its new values. Asks you first.
set_auto_deployDeploy automatically on every push to a branch (GitHub is checked every two minutes; a NOVA CLI push deploys at once), or stop. Asks you first.

How the site is doing

site_analyticsVisits over the last 30 days: total, unique visitors, each day and the top referrers. Included where your plan includes Analytics.
list_domainsThe domains a project answers on besides its NOVA address: verified or not, hosting active or not, which is primary. Buying a domain is done in NOVA, because it needs a payment.

Project memory

project_memory reads the project's memory, the same one NOVA and NOVA CLI use. add_memory adds a rule NOVA must follow on every change ("never change the logo") or a note it keeps in mind ("the café opens at 8"). You can edit or delete anything in NOVA's Memory panel.

Join our Discord

Chat with our engineers and become part of the active NOVA developer community.

Join Discord

Need help?

Open an issue on GitHub or email support@bridgeye.com.

Get help
Bridgeye • Autonomous Software Engineering.