Control over MCP

Finance skills for your AI client

A skill is reusable instructions saved in your own AI client: which tools of the Control.dev MCP server to use for a finance job, and what to check before presenting the result. It grants no access. MCP (Model Context Protocol) is the open standard AI clients use to connect to tools and data. The product docs publish 13 you can copy into Claude, ChatGPT, Codex or another MCP client, from a variance review to a budget import. Control.dev is a group consolidation and FP&A platform for multi-entity groups. EPM for the AI era. Built in the Nordics.

Start 30-day free trial Book a demo
Skills
13
Financial analysis
9
Planning and approved changes
4
Worked use cases
9
One skill file

Instructions, not access, written once and run on the whole group

A skill is a short text file in plain words. It names the tools, the checks and what the client may not claim. Change a sentence and the next run follows it.

financial-variance-review.mdFrom the product docs
---
name: financial-variance-review
description: Compare group financial statement periods and explain material movements with relevant transaction details.
---

# Financial variance review

1. Confirm the group or entity, statement, reporting currency, current period, and comparison period.
2. Call get_group_statement_actuals for group-wide questions.
3. Reconcile returned totals before calculating differences or percentages.
4. Rank movements by absolute financial effect and keep the five largest material items.

Five more steps, then the rules and the output
Copy the whole skill
  1. 01Which tool for which question

    Group-wide first; an entity tool only when the user names the entity.

  2. 02What to check before answering

    Totals reconcile before any difference or percentage is calculated.

  3. 03What it may not claim

    An empty transaction result is not evidence. A missing value is not zero.

The skills

13 skills for the recurring finance jobs

The 13 sample skills the product docs publish, in the docs’ own two groups. Each title opens the copyable skill; each tool name opens its row in the tool catalog.

Docs: all skills

Financial analysis 9

Read, reconcile and explain. These skills only read.

  1. 01

    Explain changes in financial results

    Compare periods and explain the largest changes using supporting transactions.

    Try it

    Compare June 2026 with May 2026 for the group and investigate the five largest operating-expense movements.

    What comes back

    A compact comparison table, the evidence for each movement investigated, caveats and links back to Control.

    Tools it calls
  2. 02

    Prepare a monthly management report

    Build an editable report from reconciled financial results, once Control says the month is ready.

    Try it

    Create the June 2026 management report as an editable PowerPoint outline. Compare with May, budget, and June 2025.

    What comes back

    An executive summary, a KPI table, material variances, cash and balance sheet highlights, risks, caveats and Control links.

    Tools it calls
  3. 03

    Compare budget with actual results

    Compare planned and recorded amounts on the same reporting basis.

    Try it

    Compare the June 2026 P&L with the approved budget and explain the five largest variances.

    What comes back

    The plan and scope used, a reconciled variance table, explanations for the largest movements and the exact filters.

    Tools it calls
  4. 04

    Compare company performance

    Compare companies using consistent periods, currencies and layouts.

    Try it

    Compare Finland Oy and UK Ltd revenue and operating profit for Q2 2026 in group currency.

    What comes back

    A side-by-side table, absolute and relative observations, evidence for an entity when asked, and scope caveats.

    Tools it calls
  5. 05

    Review cash flow

    Review opening cash, movements and closing cash.

    Try it

    Explain the change in group cash during Q2 2026 and identify the three largest monthly drivers.

    What comes back

    The cash bridge, the largest drivers with their evidence, the reconciliation result and any coverage caveats.

    Tools it calls
  6. 06

    Investigate transactions

    Find the transactions behind an account balance, a supplier expense or an unusual change.

    Try it

    Investigate the June increase in software expenses and group the evidence by counterparty.

    What comes back

    The scope, a grouped summary, a short evidence table, reconciliation notes and what is still unknown.

    Tools it calls
  7. 07

    Review duplicate supplier spending

    Find possible duplicate costs and the contract or usage checks they need.

    Try it

    Review the last twelve months of vendor spend and show where we pay two vendors for the same service.

    What comes back

    A table by category: suppliers, spend for the period, evidence, the follow-up and a confidence level for each.

    Tools it calls
  8. 08

    Review invoices across accounting systems

    Compare invoices across connected systems and inspect the invoice lines behind them.

    Try it

    Show net invoiced revenue by source system for Q2 2026 and explain the largest monthly change.

    What comes back

    Monthly totals first, then the breakdown asked for, the drill-down evidence and coverage caveats.

    Tools it calls
  9. 09

    Review Stripe journal entries

    Check revenue, fees, cash, disputes, VAT and exchange-rate differences from Stripe.

    Try it

    Reconcile April 2026 Stripe processing fees and cash-to-bank movements.

    What comes back

    The monthly summary, the reconciliation result, the supporting lines and any missing-data caveats.

    Tools it calls

Planning and approved changes 4

Context, models and changes. The ones that write stop and show the exact change first.

  1. 10

    Prepare financial context for an AI client

    Give a client dated context about your reporting structure and accounting choices.

    Try it

    Build a context pack for our default P&L and balance sheet, including the main account groups and department dimension.

    What comes back

    A short Markdown document with a review checklist and a section for open definitions, dated, with no ledger rows in it.

    Tools it calls
  2. 11

    Build an Excel financial model

    Build an editable model with source values, formulas and reconciliation checks.

    Try it

    Build an editable Excel model with monthly P&L actuals, budget, variance, and cash flow for January through June 2026.

    What comes back

    The workbook, a summary of its sheets and checks, the reconciliation results and the assumptions used.

    Tools it calls
  3. 12

    Import budget values

    Review proposed mappings and values, with a reason on each, before a budget import.

    Try it

    Preview this workbook against the Approved Budget for July through December 2026. Do not write anything.

    What comes back

    A preview and validation report first; after the import, committed batches, the reconciliation and rows to review.

    Tools it calls
  4. 13

    Propose a financial adjustment

    Review the accounts, amounts and reason of an adjustment in Control before it is written.

    Try it

    Investigate Norwegian salaries posted to the intercompany account in June and propose a correcting manual transaction. Do not write it yet.

    What comes back

    A proposal and a validation checklist; after the write, the accepted rows, their ids and the reconciliation.

    Tools it calls

The same idea carries a forecast: the logic written as prose in a skill file, changed by the controller and checked against actuals before anyone relies on it. The planning page shows this in full: when the forecast logic changes. Every tool the skills call is listed on MCP tools.

Worked use cases

9 jobs, start to finish

Each one is a session written out step by step in the product docs: what to ask, what the client calls and what to check.

Reviews that run in Control

When you ask, and on a schedule

A skill runs in your client when you ask. A review will run in Control on the schedule you set, with its scope and permissions checked before you turn it on. Reviews are launching soon.

Launching soon

Reviews that run on a schedule in Control

Four review templates will run on the schedule you set and flag what they find: the ledger against the account guide, supplier spend and duplicate billing, revenue by dimension, and budget against actual by entity.

  • Ledger review against account guide
  • Supplier spend and duplicate billing
  • Revenue by dimension watch
  • Budget versus actual by entity
Book a demo
In development

Scheduled agents that update the forecast

A monthly forecast update will run on a schedule and ask in plain language, with the latest actuals in and proposed changes with evidence out, applied only after a person approves.

Book a demo
Before you rely on it

Four checks before a skill’s answer counts

The checklist the product docs put in front of every skill. An explanation from a client is not proof; the statement and the entries behind it are.

  • 01Name the scopeConfirm the period, the companies, the currency and the statement layout before the client starts.
  • 02Reconcile firstTotals tie to Control before anyone reads the narrative or the report.
  • 03Missing is not zeroReview missing data and incomplete coverage. A gap is a caveat, never a zero.
  • 04Check the exact changeLook at the exact values before a client writes, and keep reports editable until someone has read them.

Connect a client first: Claude, ChatGPT, Codex, or see every client and ledger on Control over MCP.

Questions

What teams ask about skills

Ask us about your workflow
What is a skill, and where do I save it?

Reusable instructions for a recurring finance task: which Control tools to use and what to check before presenting results. Save them as a skill if your client supports skills, or add them to its project instructions.

Do skills work in ChatGPT and Codex?

Yes. Where a client has no skills, the same instructions go into its project instructions. The tools are the same in every client, because they come from the Control.dev MCP server.

Can we write our own?

Yes. The product docs show the format: a name, a description, numbered steps, rules and the output. Keep materiality thresholds and your preferred layout in your own instructions, and keep credentials out of them.

Does a skill see more than the user?

No. A skill grants no access. The client works with the permissions of the connected workspace and the tools its session has, so a read-only session runs the analysis skills and stops at the ones that write.

What happens when a tool in a skill is missing?

The client stops and says so. The docs tell it to check the connection and the permissions rather than invent a replacement; a missing write tool usually means a read-only session or a role without that right.

Do skills cost extra?

No. The skills are free to copy, and MCP access, budgets and forecasts come with every plan, so there is nothing to add per skill.

From trial to your first skill

Start the trial, connect one ledger, add Control to your client and save one skill. Or book a demo and we run a skill on a sample group in the call.

Start 30-day free trial Book a demo
  • 1. Start the 30-day trial. No card needed.
  • 2. Connect your first ledger. Yourself, or with us on a call.
  • 3. Add Control to your client. The server URL and the client ID are on the MCP Server page.
  • 4. Save one skill. Ask it about a month you already know.

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.