Connect a client
Add the Nuvelics MCP server to an AI assistant, sign in, and approve the connection.
Every MCP client, whatever its shape, connects to the same address. You add it in the client's own connector settings and sign in when it asks; there is no configuration file to edit and no API key to copy.
The server URL
https://api.nuvelics.com/api/tenant/mcpEnter it exactly as shown, with no trailing path and no typos in the host. An owner or admin can copy the same address from the MCP tab of the organization's settings once MCP is on; see MCP.
Add it to your assistant
- Open your assistant's settings for remote MCP servers or connectors.
- Add a new one and paste the server URL.
- Start the connection. Your assistant sends your browser to Nuvelics.
- Sign in with your normal Nuvelics account, if you are not already signed in. See Sign in.
- On the consent screen, check the application's name, choose the organization, and choose Allow. The screen is described in Authorize an application.
- Your browser returns to the assistant, which is now connected.
One connection per organization
A connection belongs to one organization. If you belong to several, add the connector once per organization. Each one is its own consent: approving the first does not extend access to a second, and you always make that choice yourself on the consent screen.
Reconnecting
If you belong to exactly one organization, reconnecting an application you already approved skips the consent screen, as long as it asks for no more than you approved before. If you belong to more than one organization you always see the screen, even for one you connected before, because choosing the organization is the part you are being asked to decide.
A connection that stops working, or asks you to sign in again, is reconnected the same way you made it the first time; nothing about the setup needs to change. See Troubleshooting.
When there is no browser
A command-line tool, a script or an unattended job cannot complete this flow. See Without a browser.