Skip to main content
Novaplan ships a native MCP server. MCP (the Model Context Protocol) is an open standard that lets an AI assistant call external tools. By connecting your own MCP-capable client (Claude, or any assistant that speaks MCP) to Novaplan, you give it governed access to your FP&A data and a set of safe actions, all under your permissions. This is the same data and the same guardrails as Ask Nova, exposed to the copilot you already use day to day.

​
What you get

Once connected, your assistant can query Novaplan and run a curated set of operations as MCP tools. At a high level, the surface covers:
  • Identity and orientation. Confirm who you are, list budget versions, departments, dimensions, and the metrics catalog.
  • Read your numbers. Pull headcount summaries and snapshots, GL actuals and summaries, revenue and ARR breakdowns, comparison overviews, P&L templates, currency rates, and variance decompositions.
  • Plan operations. Create and update budget versions, and manage dimension and currency reference data.
  • Data operations. Inspect an upload, suggest column mappings, run a curation, ingest a source, and revert an ingestion batch.
  • Skills and search. List and fetch Novaplan skills (the prebuilt analysis recipes) and search across the workspace.
Every MCP call runs under your role’s data access, exactly like Nova in the app. The server never returns a figure your permissions mask. A read your role cannot see in the UI is a read it cannot make over MCP either.

​
Set it up

You manage access from your account settings. Tokens live at Account, then MCP access tokens, and the connections you have authorized live at Account, then LLM connections.
1

Create an access token

Open Account, then MCP access tokens and create a token for your copilot. Give it a recognizable name (for example “Claude desktop”) so you can revoke just that one later. Copy the token when it is shown; you will not be able to read it again.
2

Add Novaplan to your MCP client

In your assistant’s MCP settings, add Novaplan as a server and paste the token. Claude and other MCP-capable clients each have a connectors or MCP servers panel where you register an external server.
3

Ground the assistant

Ask your copilot to confirm the connection by identifying you (a “who am I” check). A healthy connection returns your name and workspace, which means the token and permissions resolved correctly.
4

Operate

Now ask your copilot to query plans, pull a revenue breakdown, or check a comparison overview, all on your live Novaplan data. Review the connections you have authorized any time at Account, then LLM connections.

​
Example prompts for your copilot

  • “Using Novaplan, list my budget versions and tell me which one is live.”
  • “Pull the headcount summary for the rolling forecast and summarize the trend.”
  • “Compare planned versus actual spend by department for Q2 from Novaplan.”
  • “Get the ARR breakdown for this quarter and explain the largest movement.”

​
Manage access

Treat an MCP token like a password. It carries your permissions. If a token is exposed or a device is lost, revoke it at Account, then MCP access tokens and create a new one. Revoking a token immediately cuts off any copilot using it.
  • Create a separate token per client so you can revoke one without disrupting the others.
  • Review Account, then LLM connections periodically and remove anything you no longer use.
  • Permissions changes apply on the next call. Lower a role’s access and the copilot’s reach narrows automatically.

Ask Nova

The same governed intelligence, built into the Novaplan app.

Core concepts

Budget versions, dimensions, and lock levels that the MCP tools read against.