Connect an assistant
Which assistants each Novi MCP server supports today, and how to add one in Claude, Claude Code or Codex.
Add a Novi MCP server to your assistant with one URL. The assistant then signs you in through Novi, or sends a Novi API token where the server takes one.
Which clients each server supports
Section titled “Which clients each server supports”| Client | Novi Forecasts | Novi EVA | Novi M&A Intelligence |
|---|---|---|---|
| Claude (claude.ai and Claude Desktop), custom connector with Novi sign-in | Supported | Supported | Supported |
| Claude Code, Novi sign-in | Supported | Supported | Supported |
| OpenAI Codex, Novi sign-in | Supported | Supported | Supported |
Any client that sends a Novi API token in an Authorization header |
Supported | Not supported | Supported |
Claude Desktop extension novi-forecasts. |
Supported | Not supported | Not supported |
| Any other client signing in | Not available yet | Not available yet | Not available yet |
An unsupported client sees: “Novi doesn’t recognise the app that sent you here, so it can’t connect to your account.”
Before you start
Section titled “Before you start”- Your company host. Use the host you use for Novi apps in the browser, in the server URL below.
- Permissions. Signing in needs Access MCP plus the product’s own permission: Access Forecasts, Access EVA or Access Intelligence M&A. Your company’s Novi administrator grants them.
- A token, if you skip sign-in. Forecasts and M&A Intelligence also take a Novi API token. See Authentication.
Add a server
Section titled “Add a server”| Server | URL |
|---|---|
| Novi Forecasts | https:/ |
| Novi EVA | https:/ |
| Novi M&A Intelligence | https:/ |
The Forecasts and EVA servers are in preview and not yet available on company hosts. Tools and permissions per server: Agents and MCP.
Add a custom connector with the server URL, connect, sign in with your Novi login and approve Novi’s consent page. On a Claude Team or Enterprise plan, an owner adds the connector first.
Step-by-step screens: Connect Claude to EVA and Forecasts MCP server.
Add the servers you use, then run /mcp in Claude Code and sign in. If no browser opens, copy the URL Claude Code prints.
claude mcp add --transport http novi-forecasts https://<your-company>.novilabs.io/forecasts/api/mcpclaude mcp add --transport http novi-eva https://<your-company>.novilabs.io/eva/api/mcpclaude mcp add --transport http novi-ma https://<your-company>.novilabs.io/intelligence-ma/api/mcpTo send a Novi API token instead of signing in (Forecasts and M&A Intelligence only):
claude mcp add --transport http novi-forecasts https://<your-company>.novilabs.io/forecasts/api/mcp \ --header "Authorization: Bearer <your-token>"Add the server URL as a remote MCP server in Codex and complete the Novi sign-in. Novi shows the same consent page.
After you connect
Section titled “After you connect”| What happens | What to do |
|---|---|
| The sign-in ends after 30 days | Sign in again when the assistant asks |
| Your administrator removes Access MCP or the product permission | Access stops. Ask your administrator |
| The sign-in expired or was revoked | The assistant asks you to sign in again |
| A call fails because Novi could not check your sign-in just then | Retry. You stay signed in |
A sign-in works only for that product, at your company, through its MCP server. It does not work on Novi’s REST APIs.