Add the Control.dev MCP server to Codex and work on every entity’s ledger, already consolidated, from the terminal or the IDE: statements by layout, transactions with the entries behind each figure, budgets and the Control API. It signs in with your own Control login, and your role applies.
Control.dev is a group consolidation and FP&A platform for multi-entity groups. EPM for the AI era. Built in the Nordics. MCP (Model Context Protocol) is the open standard AI clients use to connect to tools and data. Works in the Codex CLI and Codex in the IDE.
Pivot September R&D costs by cost centre and entity, then open the largest cell to its suppliers.
get_group_transactions_browseget_entity_transactions_browse| Cost centre | Finland | Services | US | UK | Total |
|---|---|---|---|---|---|
| Hardware engineering | −65 | · | −25 | · | −90 |
| Software | −45 | · | −20 | −5 | −70 |
| Test lab | · | −20 | · | −15 | −35 |
| R&D | −110 | −20 | −45 | −20 | −195 |
Hardware engineering in Finland Oy: components and materials €38k, €24k of it Example Components AB in 12 entries.
Connect Codex
Copy the server URL and the client ID from Data outputs, then MCP Server, in Control. If the page shows no client ID yet, ask us: registering your client is part of setup.
codex mcp add control-mcp \
--url '<workspace-server-url>' \
--oauth-client-id '<client-id>'
codex mcp login control-mcp[mcp_servers.control-mcp]
url = "<workspace-server-url>"
http_headers = { "Mcp-Requested-Access" = "read" }Keep the URL and OAuth settings of the existing entry; add only the header.
Which ledgers: Netvisor, Procountor, Fortnox, NetSuite, Xero, QuickBooks and 8 more, each read by Control and consolidated before Codex asks. See all 14 ledger pages.
Taito.ai · The team can also query its financial data through the MCP integration, bringing the same structured numbers into the AI tools it already uses.
Codex works with files in its own environment, so the jobs that start from a workbook or an export fit it best. Each job below is in the product docs with its prompt and checks.
Codex checks the workbook against the group accounts without writing, shows what does not map, and imports the rest with the source row noted on every value. The workbook stays attached to the budget.
Budget import guideCodex reads a DATEV account-ledger export, asks about the rows that need a decision, loads every posting with its booking text and document number, and ties the result out against the export.
DATEV upload guideCodex builds an editable workbook in its own environment: source sheets from Control’s statements, budgets and cash flow, formulas for every derived value, and reconciliation checks.
Excel model skillCodex reads the consolidated statements and cash flow, budgets, comments and transactions in pages of up to 5,000 rows. In a write session it can import files, save budget values and manual transactions, and call the Control API tools, as your role allows.
Your role in Control sets the ceiling, a read-only session gets no write tools, and a locked version refuses every write. Every client gets the same tools: the full read and write list.
For the engineer and the finance-ops builder: what the server gives a script or an agent, in the server’s own terms.
get_group_transactions_browse and get_entity_transactions_browse take limit from 1 to 5000 and offset, with filters, groupBy and a pivot mode. Statements come back as JSON by layout, with every subtotal row.
control_api_endpoint_catalog lists the allowlisted endpoints, control_api_get reads them, and control_api_request calls the same operations the Control app uses, excluding billing, invitations, admin, credential and file-upload endpoints. The tool tells Codex to confirm with you before a write call; your role and the lock decide what goes through.
Codex uploads a transaction or budget file straight to api.control.dev from its own environment, not through MCP: prepare_file_upload, then validate_bulk_file_import, then submit_bulk_file_import once you confirm the validation result.
Already wired your own agents to a ledger? Keep them, and give them a consolidated group to read: Control.dev vs building it yourself compares the two row by row.
Show consolidated revenue by month for January through June 2026.
Why did personnel costs change between May and June? Show the supporting transactions.
Compare operating profit for Finland Oy and US Inc.
Name a company and Codex picks the entity tools; otherwise it answers for the whole group. On Stripe or Odoo? Stripe MCP and Odoo MCP show what Codex gets from each system alone and what the group adds.
Save the instructions for a recurring job in your project instructions: which Control tools to call and what to check before answering. They grant no access of their own. Three to start with:
All thirteen with the tools each calls: Finance skills. Every finance tool the server exposes: MCP tools. The other clients and the ledger pages: MCP. Copyable instructions: skills in the product docs.
Yes. Production connections use a pre-registered OAuth client: pass it with --oauth-client-id, and have the callback URL that codex mcp add prints registered before you sign in.
Add http_headers = { "Mcp-Requested-Access" = "read" } to the [mcp_servers.control-mcp] entry in ~/.codex/config.toml, reconnect and refresh the tool list. A read-only session receives no write tools.
Yes: prepare_file_upload, then validate_bulk_file_import, then submit_bulk_file_import after you confirm the validation result. The file goes straight to api.control.dev, and a locked budget refuses the import.
JSON. Statements come by layout with every subtotal and formula row, and transaction browsing pages with limit up to 5000 and offset. The tool list (tools/list) is the source of truth for what your session can call; the tool catalog lists them by group.
OpenAI processes what Codex reads under your agreement with OpenAI, and Control’s own AI processes data in the EU (security at Control.dev).
There is no separate MCP fee: MCP access, budgets and forecasts come with every plan. The pricing page lists the self-serve plans, a group with more than the five ledgers the Enterprise plan includes gets a quote, and the 30-day trial needs no card.
Start the trial and connect one ledger, or book 30 minutes and we connect Codex to a four-ledger sample group with you.
MCP access is in every plan. Self-serve plans are on the pricing page; groups with more than the five ledgers the Enterprise plan includes get a quote.