NOVA MCP Use Cases

Docs › NOVA MCP

Use cases

Three examples, one per plan, from the first line to a live app.

Free: a café site from Claude

  1. 1Riya adds NOVA in Claude (Connectors, Add custom connector, https://runnova.ai/mcp) and signs in with her NOVA account.
  2. 2She asks: "Build a one-page site for my café, Brew and Bloom in Pune, with the menu and opening hours, and put it on NOVA." Claude calls build; NOVA builds it on her 40 daily credits and the result says how many it used.
  3. 3Claude runs verify: the build and browser test pass and the scan is clean.
  4. 4Claude asks "Deploy it now?" She says yes; it goes live on her one NOVA address, with her plan's 15 free hosting days.

Starter: a Next.js app with a database from Claude Code

  1. 1Arjun runs claude mcp add --transport http nova https://runnova.ai/mcp and says "Deploy this on NOVA."
  2. 2Claude Code calls send_local_folder and runs the upload command it returns (Starter includes sending a folder).
  3. 3verify finds two problems: the app crashes at start because DATABASE_URL is not set, and an old auth library has a critical vulnerability, which blocks a deploy.
  4. 4Claude Code calls propose_fix and shows the diff (a one-line upgrade). He says yes; apply_fix keeps it and Claude Code applies it to his folder too. He connects Neon in NOVA for the database.
  5. 5verify passes; he approves the deploy. It runs on his plan's free window for server apps, and later he picks an always-on size on his monthly bill.

Pro: a team deploying a Python API from GitHub

  1. 1The lead connects NOVA in Codex and calls import_github_repo (Pro includes importing a repository).
  2. 2She makes an API key with deploy on the NOVA MCP page, for their CI. Each merge calls the API's deploy.
  3. 3One merge opens the API to every website (CORS * with cookies). It is high, not critical, so the deploy goes ahead and the report says how to fix it.
  4. 4A week later the app crashes. logs shows why; propose_fix makes the fix, and apply_fix with open_pull_request sends it to GitHub for review. A bad release? rollback puts the last good one back.

Any plan: looking after a live site

  1. 1"How is the café site doing?" Your tool calls site_analytics (where your plan includes Analytics) and hosting_status, and tells you the visits, top referrers and how much of the free hosting window is left.
  2. 2"From now on, never change the logo." It calls add_memory with a rule; every later fix or edit by NOVA follows it.
  3. 3"Yesterday's menu was better." list_versions finds it, restore_version brings it back after you say yes, and a deploy puts it live.
  4. 4"I changed the API key; use it." set_env stores it, then restart_app starts the app with it, both after you say yes.

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.