Custom MCP Servers (Bring Your Own)
Connect any remote MCP server to Nova as a skill: a vendor's hosted server or your own internal tool server. Give Nova the server's address, it discovers the tools, and from then on Nova uses them like a built-in skill, in Nova Cloud, astroctl nova and Slack, under your guardrails. There is no code to write.
When you need it
- Your team has its own tools behind an MCP server, and you want Nova to use them in investigations and answers.
- A vendor offers a hosted MCP server that Nova does not have as a built-in skill.
Before you start
- The Enterprise plan. Custom servers belong to your organization.
- A remote MCP server reachable over Streamable HTTP.
- Its sign-in, if it has one: an API key, a bearer token, or OAuth 2.1 through the server's own sign-in.
In the console
- Open Nova, select Skills in the sidebar, then Add MCP server.
- Fill in:
- Name: how it appears in your skills.
- Description: optional, what the server provides.
- Server URL: the server's address, for example
https://mcp.example.com. - Transport: Streamable HTTP.
- Authentication: No authentication, API key, Bearer token or OAuth 2.1. For an API key or bearer token, paste it in API key or token. For OAuth 2.1, select Connect with OAuth and complete the server's sign-in until it shows Connected.
- Select Discover tools. Nova connects to the server and lists its tools.
- Choose the tools Nova may use and select Create server.
You should see
The server under Skills as a skill card with a health badge, like any built-in skill. Ask Nova in plain words and it uses the server's tools when they fit; you see the skill, not the raw tools.
Manage a server
Open the server's Settings from Skills:
- Health badge: whether the server was reachable at its last successful connection.
- Test connection: checks the connection again and refreshes the tools and their read-only and destructive hints.
- Trust this server: owners and admins only. See below.
- Remove this MCP server: disconnects it. Organization owners only.
What Nova may do with your tools
Until an owner or admin turns on Trust this server, Nova asks a person before every call to the server. Once it is on, Nova reads the hints your server publishes for each tool (the MCP readOnlyHint and destructiveHint annotations), and your guardrails decide the rest:
- A tool marked read-only runs as a read.
- A tool marked destructive follows your Destructive Actions rule, which blocks it by default.
- Any other tool is a change, including one whose server says nothing about it. It follows your Changes & Remediation rule, so by default Nova asks first.
Any change to the server's tools, or to its address, turns trust off again. Nova never decides from a tool's name. If a tool that only reads keeps asking for approval, mark it readOnlyHint: true on your server, then select Test connection.
How your server and credentials are protected
- Credentials kept out of reach. The key, token or OAuth sign-in is encrypted when stored, added to each call by Nova, and never shown back or given to the AI model.
- Private networks are off limits. Nova checks every address the server resolves to, and every redirect, so a server cannot point Nova at a private, loopback or cloud metadata address. Its OAuth addresses are checked the same way.
- Calls are checked before you approve. Each call is checked against the parameters the server publishes, so an approval always shows a call the tool can run.
- Bounded results. Very large results are cut, with a note of what was left out.
- Every call recorded. Each call, and who approved it, is in your organization's record.
- Your organization only. A custom server is visible to and used by your organization alone.
See Security controls.
Popular public servers are built in
The public servers platform teams ask for most are already built-in skills, free on every plan, with no sign-in. Open Skills, find the one you want and select Connect; it is then on for everyone in your organization.
- AWS Knowledge: AWS documentation, and which services and features each region offers.
- Microsoft Learn: Azure and Microsoft documentation and code samples.
- Cloudflare Docs: Cloudflare product documentation.
- Context7: current documentation for open source libraries and frameworks, by version.
- DeepWiki: questions about any public GitHub repository.
- Hugging Face: models, datasets and papers on the Hugging Face Hub.
- Pulse Benchmarks: GPU and inference price indices across clouds.
These skills only read public information, so every call runs as a read under your guardrails. When Nova uses one, the provider receives what Nova asks it, such as a search phrase or a library name. Each provider publishes its own server address if you want to use it from another MCP client.
If it's refused
A server whose name or address matches one you already have is refused, so tools never clash. If discovery fails, check the URL and sign-in and select Test connection: Nova shows the server's own error.