How NOVA Uses Your MCP Servers

Docs › NOVA MCP

How NOVA uses your servers

Your servers' tools sit beside NOVA's own (reading files, editing, running the app). NOVA decides when one helps, writes the inputs from the tool's own description, reads the answer and carries on, the same way Claude uses a connected server.

From the first message. NOVA knows which servers the project has connected and what their tools do, even before anything is built. Ask for work in the service itself, for example Draw a color-coded flowchart of our order process on this Miro board with the board's link, and NOVA does it there instead of offering to build a website. Making things on a service needs Tools that change things to be allowed for that server.

  1. 1You ask NOVA something in the project, for example "add the open bugs from our tracker to the status page".
  2. 2NOVA sees your server's tools (named after the server, like mcp_Acme__search_tickets) and calls the one that helps, with the inputs it needs. You see Asking Acme: search tickets in the progress.
  3. 3The answer comes back to NOVA marked as information from a third party. NOVA uses it to make the change, and can call again if it needs more.
  4. 4When it is done, NOVA says what it did, as always.
Only what you addedNOVA sees only the tools you accepted, with the descriptions you saw. A tool the server adds later is not used until you accept it with Check for new tools.
Changes need your sayTools marked Changes things are only offered to NOVA when you allowed them for that server.
Answers are information, not ordersWhatever a server sends back reaches NOVA labelled as third-party data. Text in it that tries to give NOVA instructions is not treated as coming from you or from NOVA.
Checked every timeThe address is checked again on every call, so a server that later points into a private network is refused.
Sign-ins renewedAn expired sign-in is renewed before the call. If the service refuses it, NOVA tells you to press Reconnect.
CreditsCalling your server costs no credits by itself. NOVA's own work on your request uses credits as usual. Anything the service charges for its own use is between you and that service.

Example: a store that sells from its own catalogue

  1. 1Meera runs her product catalogue behind an MCP server at https://catalogue.meera-crafts.com/mcp. In her NOVA project she opens Connectors, adds it, signs in with her catalogue account in the popup, and adds the two tools it offers: list_products (Reads) and update_stock (Changes things), leaving changes off.
  2. 2She asks NOVA: "Build a shop page with every product in the Summer collection." NOVA calls list_products with the collection name, gets the names, prices and photos, and builds the page from them.
  3. 3Later: "Mark the blue scarf as sold out everywhere." NOVA cannot use update_stock because she did not allow changes, so it updates the site and says the catalogue itself was not changed. She ticks Let NOVA use the tools that change things and asks again; this time NOVA updates the catalogue too.

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.