How NOVA Uses Your MCP Servers
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.
- 1You ask NOVA something in the project, for example "add the open bugs from our tracker to the status page".
- 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. - 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.
- 4When it is done, NOVA says what it did, as always.
Example: a store that sells from its own catalogue
- 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) andupdate_stock(Changes things), leaving changes off. - 2She asks NOVA: "Build a shop page with every product in the Summer collection." NOVA calls
list_productswith the collection name, gets the names, prices and photos, and builds the page from them. - 3Later: "Mark the blue scarf as sold out everywhere." NOVA cannot use
update_stockbecause 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.
Need help?
Open an issue on GitHub or email support@bridgeye.com.