NOVA MCP Tools

Docs › NOVA MCP

Tools

Everything your AI tool can ask NOVA to do, generated from NOVA MCP itself, so it is always exactly what the server offers. Access is what you allowed when connecting (read, build, deploy). Asks you first means the tool may only run it after you said yes in the chat.

Your account

plan_and_creditsPlan and credits
Needs read accessOnly looks

The person's NOVA plan, credits left today, and every limit that applies to NOVA MCP (projects, app databases, free hosting days, jobs per day, whether a local folder or a GitHub repository may be sent). Call this first.

Projects

list_projectsList projects
Needs read accessOnly looks

The person's NOVA projects: id, name, when last changed, and the live address if one is live.

  • limit (integer, optional)
project_statusProject status
Needs read accessOnly looks

One project: its files count, whether it is live and where, and the most recent NOVA MCP jobs on it.

  • project_id (string, required)
create_projectCreate a project
Needs build access

An empty NOVA project to send code into or build in. Counts towards the plan's active projects.

  • name (string, required)

Getting code in

send_local_folderSend a local folder
Needs build access

Get a one-time link and the exact command that sends the current folder to NOVA (as a zip; .env files, node_modules, .git and build output are left out). Run the command in the project folder; its output says the project_id and version. Give project_id to update an existing project, or name to create a new one. The folder replaces NOVA's copy; the earlier version stays in Version History. Needs the plan's 'send a local folder'.

  • project_id (string, optional)
  • name (string, optional)
import_github_repoImport a GitHub repository
Needs build access

Bring a GitHub repository (owner/name) into a NOVA project: a new one (give name) or an existing one (give project_id; changes made on NOVA are kept on a branch). Uses the GitHub account the person connected in NOVA. Needs the plan's 'import a GitHub repository'.

  • repo (string, required): owner/name or a github.com link
  • branch (string, optional)
  • project_id (string, optional)
  • name (string, optional)
buildBuild with NOVA
Needs build accessUses credits

NOVA builds a new project from a description, on the person's NOVA credits. Returns a project_id and a job_id; poll job_status. Then verify and deploy as usual.

  • prompt (string, required)
  • name (string, optional)

Checking

verifyVerify
Needs build access

Check the project before it goes live: a security scan (leaked secrets, dependencies with known vulnerabilities, risky code and settings), then the app itself (a site: build and a real-browser test; a server app: start it in a sandbox and watch its log). Returns a job_id; poll job_status. Its result says whether it is ready, and what blocks a deploy (a live secret or a critical vulnerability).

  • project_id (string, required)
security_scanSecurity scan
Needs read accessOnly looks

Only the security scan, at once: leaked secrets, dependencies with known vulnerabilities (from osv.dev), risky code and settings. Secrets are masked.

  • project_id (string, required)
job_statusJob status
Needs read accessOnly looks

Where a verify, deploy, fix or build job is: each step so far, then its result. While poll_again is true, wait poll_after_ms milliseconds and ask again (or pass wait_s, up to 10, to have NOVA wait for the next step or the end before answering).

  • job_id (string, required)
  • wait_s (integer, optional): Optional: wait up to this many seconds (max 10) for the job to move on before answering.

Fixing and changing

propose_fixPropose a fix
Needs build accessUses credits

Ask NOVA to fix what verify (or a refused deploy) found, plus anything the person adds in `instruction`. Uses the person's NOVA credits. NOVA's change is kept as a proposal: the project is not changed until apply_fix. Returns a job_id; poll job_status, then show the person the summary and diff.

  • project_id (string, required)
  • job_id (string, optional): The verify or deploy job to fix (default: the latest).
  • instruction (string, optional)
editEdit with NOVA
Needs build accessUses credits

Ask NOVA to change the project ("add a contact form", "make it faster"). Uses the person's NOVA credits. Like a fix, the change is proposed: show the person get_fix, then apply_fix after they agree. Returns a job_id.

  • project_id (string, required)
  • instruction (string, required)
get_fixGet a fix
Needs read accessOnly looks

A proposed fix: NOVA's summary in plain words, the files it changes, and the full diff. Show this to the person before apply_fix.

  • fix_id (string, required)
apply_fixApply a fix
Needs build accessAsks you first

Keep NOVA's proposed fix: it becomes a new version of the project (the previous one stays in Version History). Set open_pull_request for a project linked to GitHub. Call only after the person has seen the diff and said yes. Then apply the same diff to the local folder (git apply) so it matches.

  • fix_id (string, required)
  • open_pull_request (boolean, optional)
  • confirm (boolean, optional): Set true only after the person has said yes to this action.
discard_fixDiscard a fix
Needs build access

The person does not want NOVA's proposed fix. Nothing in the project changes.

  • fix_id (string, required)

Going live

deployDeploy
Needs deploy accessAsks you first

Put the project live on NOVA: a security scan first (a live secret or a critical vulnerability stops it), then the same checks as Play (build, browser test), then hosting on the person's plan (free hosting window, sizes, monthly bill). Returns a job_id; poll job_status. Ask the person first.

  • project_id (string, required)
  • confirm (boolean, optional): Set true only after the person has said yes to this action.
rollbackRoll back
Needs deploy accessAsks you first

Put the previous live version back (or a specific deployment_id from list_deploys). Nothing is deleted. Ask the person first.

  • project_id (string, required)
  • deployment_id (string, optional)
  • confirm (boolean, optional): Set true only after the person has said yes to this action.
list_deploysList deploys
Needs read accessOnly looks

The project's deploys, newest first, with which one is live.

  • project_id (string, required)
logsLogs
Needs read accessOnly looks

What the live app printed (server apps), with secrets replaced by their names, and the app's recent events (deploys, restarts, crashes).

  • project_id (string, required)
  • limit (integer, optional)

Environment

list_envList environment variables
Needs read accessOnly looks

The project's environment variable names (values masked) and secret file names.

  • project_id (string, required)
set_envSet environment variables
Needs deploy accessAsks you first

Set one or more environment variables for the app (stored encrypted, given only to the app's own server, never shown back). Takes effect on the next deploy or restart. Ask the person first.

  • project_id (string, required)
  • variables (object, required): NAME: value pairs
  • confirm (boolean, optional): Set true only after the person has said yes to this action.
delete_envDelete an environment variable
Needs deploy accessAsks you first

Remove one environment variable. Ask the person first.

  • project_id (string, required)
  • name (string, required)
  • confirm (boolean, optional): Set true only after the person has said yes to this action.

Hosting

hosting_statusHosting status
Needs read accessOnly looks

The project's hosting as in Manage Site, Hosting: what kind of app it is, its size and plan state, whether it is live and where, the free hosting window, usage, and the commands it builds and starts with.

  • project_id (string, required)
restart_appRestart the app
Needs deploy accessAsks you first

Start the live server app again as it is: no new build, no new code. Use it after set_env. Ask the person first.

  • project_id (string, required)
  • confirm (boolean, optional): Set true only after the person has said yes to this action.
set_auto_deployAuto-deploy on or off
Needs deploy accessAsks you first

Deploy automatically on every push to a branch (from GitHub, checked every two minutes, or a NOVA CLI push), or stop doing so. Ask the person first.

  • project_id (string, required)
  • on (boolean, required)
  • branch (string, optional): Default: main
  • confirm (boolean, optional): Set true only after the person has said yes to this action.

Version History

list_versionsList versions
Needs read accessOnly looks

The project's saved versions on its main branch, newest first: number, what changed (message), where it came from (NOVA, NOVA CLI, NOVA MCP, a merge) and when.

  • project_id (string, required)
  • limit (integer, optional)
restore_versionRestore a version
Needs build accessAsks you first

Put an earlier version's files back as a NEW version (nothing is deleted; the current files stay in history). The live site does not change until a deploy. Ask the person first.

  • project_id (string, required)
  • version (integer, required)
  • confirm (boolean, optional): Set true only after the person has said yes to this action.

How the site is doing

site_analyticsSite analytics
Needs read accessOnly looks

Visits to the live site over the last 30 days: total, unique visitors, each day, and the top referrers. Needs the plan's Analytics.

  • project_id (string, required)
list_domainsList domains
Needs read accessOnly looks

The domains the project answers on, besides its NOVA address: whether DNS is verified, whether its hosting is active, and which one is primary. Buying a domain is done in NOVA (it needs a payment).

  • project_id (string, required)

Project memory

project_memoryProject memory
Needs read accessOnly looks

The project's memory: rules NOVA must follow, notes NOVA keeps in mind, and what NOVA learned. The same memory Play and NOVA CLI use.

  • project_id (string, required)
add_memoryAdd to project memory
Needs build access

Add a rule (NOVA must follow it on every change, like "never change the logo") or a note (background NOVA keeps in mind, like "the café opens at 8").

  • project_id (string, required)
  • kind (rule or note, required)
  • text (string, required)

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.