Start here
What is MCP in finance?
MCP (Model Context Protocol) is an open standard that lets AI assistants connect to business systems through a common interface. Instead of copying data into a chat window, an assistant such as Claude, ChatGPT, Copilot, or Gemini requests the data it needs from an MCP server, and the server decides what it can see and do.
In FP&A, that means an assistant can answer questions on actuals, budgets, and forecasts, or write updates back to the plan, using the same governed model the finance team works in. Permissions, business rules, and the audit trail all come from the source system, not the chat.
Connect
One standard connection
Connect every MCP-compatible assistant once, instead of building and maintaining a separate integration for each AI tool.
Govern
Permissions carry over
Each user sees only the entities, accounts, and versions their Cube role allows, in every assistant.
Calculate
Figures of record
Answers come from Cube’s calculated model and business rules, so every assistant returns the same number.
Write back
Edits with approval
Assistants can propose plan and forecast updates that flow back to Cube for finance to review, with every change logged.
Why MCP matters for FP&A
AI assistants are already in use across most finance teams, often on exported spreadsheets that are out of date the moment they are downloaded and carry no permissions. MCP gives those assistants a governed path to live financial data. Finance keeps one source of truth, and the rest of the business gets answers in the tools they already use.
How to use MCP in FP&A
Rolling out MCP works best when the data foundation is already in place. A typical sequence:
-
1.
Unify your financial data. Connect the GL, CRM, HRIS, and billing systems into one governed Cube model.
-
2.
Set roles and permissions. Decide who can see which entities, departments, and plan versions.
-
3.
Connect your assistants. Point Claude, ChatGPT, Copilot, Gemini, or another MCP client at the Cube MCP Server.
-
4.
Start with read-only questions. Variance explanations, budget-to-actual checks, and KPI lookups are easy to verify.
-
5.
Turn on write back. Let assistants submit forecast and plan changes for finance review and approval.
Key terms
- MCP (Model Context Protocol)
- An open protocol that standardizes how AI assistants request data and take actions in external systems.
- MCP server
- The service that exposes a system’s data and actions to AI assistants and enforces what each user can access.
- MCP client
- The AI assistant or app that connects to an MCP server, such as Claude, ChatGPT, Copilot, or Gemini.
- Write back
- An assistant sending an update, like a revised forecast, back into the source system rather than only reading from it.
- Governed data
- Financial data that is reconciled, calculated with agreed business rules, and protected by role-based permissions.
- Audit trail
- A log of every query, edit, and approval, showing who did what and when.
Spreadsheet uploads vs. MCP connected to Cube
|
Uploading files to AI |
Cube MCP Server |
| Freshness |
Stale the moment it is exported |
Live data synced from source systems |
| Permissions |
Anyone with the file sees everything |
Cube roles applied to every answer |
| Consistency |
Each assistant may calculate differently |
Same figure of record in every assistant |
| Write back |
Manual copy and paste |
Proposed changes flow to Cube for approval |
| Audit trail |
None |
Every query and edit logged |
| Setup |
Repeated for every file and tool |
Connect each assistant once |