MCP in beta
Get now has a remote MCP server for connecting assistants like Claude or Codex to your workspace.
MCP (Model Context Protocol) lets an assistant understand real Get data and run scoped actions without making you copy and paste context manually. The connection uses OAuth: you sign in to Get, choose the workspace and can revoke access whenever you need to.
For now, MCP is available on the Pro plan and marked as beta while we keep improving permissions, response quality and compatibility with more MCP clients.
What it can do
The first toolset covers the production operating flow:
- Search clients, projects and budgets.
- Read the details of a client, project or budget.
- Create and update clients, folders/projects and budgets.
- Move budgets between projects.
- Record movements and actuals.
- List actuals by workspace, budget, status or date range.
- See a workspace summary with pipeline and real cashflow by currency.
The goal is to let you ask things like "show me sent budgets in USD", "record this real expense against the budget" or "give me a summary of the quarter" from the assistant you already use.
Better financial context
We also improved the data MCP exposes so it is not just a flat list of records.
The workspace summary now separates two important views: pipeline, with open budgets grouped by status, and realized, with paid income and expenses during the selected period. Everything is grouped by currency, so the assistant does not mix CLP, USD or other currencies when answering.
Actuals are now part of the protocol too. You can ask for real expenses across the workspace or filter them by budget, status and date. That makes the assistant useful for day-to-day production questions, not only initial budgeting.
Setup from Settings
We added an MCP section in Settings with the server URL ready to copy.
From there you can choose Claude or Codex, copy the server URL and follow the client-specific steps. For Codex, Get shows the terminal commands to add the server and start the OAuth login flow.
More control and traceability
Each connected app is authorized per workspace. It does not get global access to all your data: you choose the workspace during authorization and can revoke the connection from the same section.
We also added metadata so MCP clients better understand which tools are read-only and which ones write data. Tool calls are audited, and errors now include a request_id so support can find the relevant log faster when something fails.
What's next
We will keep iterating on three fronts: more useful actions, clearer answers for financial workflows and a less manual setup experience as MCP clients mature.
If you already use Claude or Codex for work, this is the first step toward letting the assistant operate with real Get context instead of working blind.