Bring Your Own MCP Server
Bring your own MCP
The other direction. NOVA MCP lets your AI tool use NOVA; Bring your own agent lets NOVA use your MCP servers: your ticket tracker, design tokens, CMS, internal API or anything else that speaks MCP. Adding one works the way it does in Claude: paste the address, sign in if it asks, and NOVA can use it.
Add a server
- 1Open your project, then Connectors. Under Your own MCP servers, press Add an MCP server.
- 2Paste the server's address (for example
https://mcp.example.com/mcp), give it a name if you like, and press Connect. NOVA connects and asks it what tools it offers. - 3If the server needs you to sign in, NOVA says so and shows Sign in. Press it: the service's own sign-in page opens in a small window. Sign in there and approve NOVA. The window closes by itself. There is no token to find or paste.
- 4NOVA shows every tool the server offers, with its description and inputs. Each is marked Reads or Changes things, starting from what the server says about it. Change any you disagree with.
- 5Tick Let NOVA use the tools that change things too if you want NOVA to act on that service (for example, open a ticket). Leave it off and NOVA only uses the tools that read.
- 6Press Add. The server is on straight away. Ask NOVA anything in the project and it uses the server's tools when they help.
Discover: connectors tested with NOVA
In Connectors, Discover lists MCP servers NOVA has tested before listing them: it connected to each with its own connect code, and for those that need a sign-in it registered NOVA as an app and opened their sign-in page to check it accepts NOVA. Search or pick a category, open one to see what it does, who makes it, whether it needs a sign-in, its address and its tools, then press Connect to NOVA (or +). It joins Yours and you sign in as usual. Each is re-tested from time to time; one that stops passing is taken off the list.
Discover also lists NOVA's own connectors, marked Built into NOVA: Google Sheets, Gmail, Stripe, Razorpay, Shopify, WooCommerce, WordPress, Mailchimp, Twilio and Calendly, each with its brand logo. Pressing one opens its own setup (sign in with Google for Sheets and Gmail, or paste a key), the same screen as in Manage Site, Connectors.
Suggest a server (in Discover) asks for a server to be added. Give its connector address and name, and optionally who makes it, what it does and a note. NOVA tests it straight away with the same checks and tells you what it found; then the NOVA team reviews it. Approving tests it once more, so only a server NOVA works with is listed. Your requests and their outcome (waiting, approved, or not added with the reviewer's note) show under the form. You can have up to five waiting at once, and send up to ten a day.
NOVA knows which servers work. For each server on a project NOVA knows whether it is on, switched off, has no tools accepted yet, needs you to sign in again, or has been failing lately, and tells you so instead of trying one that can't work. When a call to a connected server fails, the service, the tool and the error are reported to the NOVA team so they can test it, fix the listing, or take it off Discover.
Tested and not listed today, with the reason (you can still add any of them under Your own MCP servers if you have what it needs):
Which servers work
Managing a server
Each server is a card with the service's own logo, its address, how many tools it has and whether you are signed in. Press the card to open it.
Work you start from Claude, ChatGPT or another AI tool through NOVA MCP is done by the same editor, so it knows the same things about your project as NOVA does in the browser: your connections, plan and credits, whether the project is live, its last build and its Version History.
In the + menu
Every server you connect also appears in the workspace's + menu under Tools, with its logo, beside NOVA's built-in connectors. Its switch there turns it on or off for the project, the same as the switch in Connectors. The list refreshes when you come back to the workspace, so a server you have just connected shows up straight away.
Logos
NOVA shows the service's own logo, found the way a browser finds a site's icon: first the server's address, then the website it belongs to (for mcp.miro.com, miro.com). NOVA's server fetches it, so the service never sees who opened the project, and keeps it for a day. A service with no icon is shown by its first letter.
Limits today
Only the project's owner can add, change or remove its servers. Members of the project benefit from them when NOVA works, but cannot point the project at a server of their own.
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.