Bring Your Own MCP Server

Docs › NOVA MCP

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.

Paste the server's address in Connectors, sign in to it in a popup if it asks, review its tools marked Reads or Changes things, then NOVA uses them while it works.

Add a server

  1. 1Open your project, then Connectors. Under Your own MCP servers, press Add an MCP server.
  2. 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.
  3. 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.
  4. 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.
  5. 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.
  6. 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.

AI & researchDeepWiki, Exa, Hugging Face
AnalyticsGrafana, PostHog
AutomationPipedream, Zapier
Design & mediaCloudinary, Miro, Mux
Developer toolsAWS Knowledge, Buildkite, Cloudflare Docs, Cloudflare Observability, Cloudflare Workers, Context7, Globalping, Jam, LaunchDarkly, Microsoft Learn, Neon, Netlify, Prisma Postgres, Sentry, Stytch, Supabase, Twilio Docs
Docs & knowledgeAirtable, Notion
FinanceMercury, Ramp
MeetingsFireflies
Payments & commercePayPal, Plaid, Stripe
Project managementAtlassian, ClickUp, Linear, monday.com
Sales & CRMAttio, Close
SchedulingCal.com
Websites & contentContentful, Sanity, Webflow, Wix

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):

Asanawon't register outside apps; works only with an app you create there (Advanced, client ID)
Boxwon't register outside apps; works only with an app you create there (Advanced, client ID)
Calendlyno MCP server answers at its published address
Canvaits sign-in refuses NOVA's return address or request today
Dropboxwon't register outside apps; works only with an app you create there (Advanced, client ID)
Figmawon't register outside apps; works only with an app you create there (Advanced, client ID)
GitHubwon't register outside apps; works only with an app you create there (Advanced, client ID)
HubSpotwon't register outside apps; works only with an app you create there (Advanced, client ID)
Intercomwon't register outside apps; works only with an app you create there (Advanced, client ID)
Semgrepits sign-in refuses NOVA's return address or request today
Shopify Devno MCP server answers at its published address
Squarewon't register outside apps; works only with an app you create there (Advanced, client ID)
Vercelwon't register outside apps; works only with an app you create there (Advanced, client ID)
Vimeoits sign-in refuses NOVA's return address or request today

Which servers work

Remote MCP serversAny MCP server reachable over the internet with an https:// address. NOVA speaks the current MCP transport (Streamable HTTP, protocol versions 2025-06-18 and 2025-03-26) and the older HTTP with server-sent events (2024-11-05), and picks the right one by itself.
Servers with a sign-inServers that use the MCP sign-in standard (OAuth 2.1). NOVA finds the sign-in, registers itself with the service automatically, and signs in with PKCE so the code can only be used by NOVA. Sign-ins are renewed automatically when they expire.
Servers with a keyUnder Advanced, paste an access token you already have. NOVA sends it as a Bearer token on every call.
Services that need an appA few services do not let apps register themselves. NOVA tells you; create an app on that service whose redirect (callback) address is the address you open NOVA at followed by /agents/callback, then paste its client ID (and secret, if it has one) under Advanced and press Connect again.
Not supportedServers that only run on your own computer (stdio), addresses that are an IP number, use a port, carry a username or password, or point inside a private network. A server that redirects somewhere else is not followed.

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.

The switchTurns the server on or off for this project. Off means NOVA does not see or call it. Nothing is deleted.
Tool permissionsTools are grouped into Read-only tools, which NOVA may always use, and Tools that change things. Open a group to see its tools, one per line; press a tool for its full description and inputs.
Tools that change things: Allowed / Not allowedAllows, or stops allowing, the tools that change things. Turning it off also removes them from Also run before every build.
Also run before every buildOptional, and folded away. Lists the tools that need no inputs. Tools ticked here run at the start of every build, and their answer goes into the build. Useful for a standing question like "what are the current design tokens". NOVA can use every tool anyway, so most people leave this empty.
Check for new toolsAsks the server what it offers today and shows what is new and what is gone. Nothing changes until you press Use this list, so a server cannot change its own tools behind your back.
ReconnectFor a server you signed in to: signs in again, for example after you revoked NOVA on that service or changed accounts.
RemoveDeletes the server from the project, together with its sign-in or token.

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

ServersUp to 10 per project.
ToolsUp to 100 from one server.
CallsUp to 25 calls to your servers while NOVA works on one request, and up to 8 before a build for Run before every build.
Time and sizeEach call has 30 seconds and up to 512 KB of answer. NOVA reads up to 12,000 characters of one answer; images and audio are named, not shown.

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.

Join Discord

Need help?

Open an issue on GitHub or email support@bridgeye.com.

Get help
Bridgeye • Autonomous Software Engineering.