AI connectors (MCP)
The reads on these pages, offered to an AI client as tools - and, on the Premium edition, the six imports and the consolidation trigger. A client is pointed at one URL, signs a person in through BrizoConsol itself, and then sees only what that person's connection was allowed: the reads its scopes cover, and the writes only where an administrator named the company for writing, the plan includes them, and the client is Zapier's.
An MCP client - Claude, ChatGPT, or anything else that speaks the protocol - answers a question by calling these tools instead of being handed the data. Each tool is one call on this same API, answering the same figure the screen shows and refusing what the endpoint refuses, so a question about a month's revenue and the report for that month do not disagree, and a month imported by a Zap and a month imported by a connector store the same rows.
What the client is told
This is the connector's identity: what a person sees when they add it, and what a model reads before it chooses a tool.
| What | Value |
|---|---|
| Endpoint | POST https://…/mcp - the URL the AI Access screen states, JSON-RPC
over HTTP, no server-to-client stream |
| Name | BrizoConsol |
| Version | 1.0.0 |
| Description | The text under The description, verbatim |
| Tools | Twenty-one reads, and the seven writes the Premium edition allows, listed under The tools. A tool whose scope the connection does not hold is not offered at all, and a write tool is offered to no client but Zapier's, so what a given client sees is usually shorter |
The description
Stated once, when the connection is opened, before any tool is called:
Financial reads for the companies this connection was approved for. Start
with list_organisations and retrieve all pages: its ids are what every
other tool takes as organisation_id, and a company that is not in that
complete list answers not_found. For a question about a group and its
subsidiaries, use
the consolidated organisation's id for group totals and call get_statement
separately for each approved subsidiary's id for entity figures. A
consolidated statement does not mean subsidiary reads are unavailable; only
state an access limitation after checking the complete organisation list.
Group approval does not automatically approve its subsidiaries. A month is
asked for as `Mon-YYYY` such as `Sep-2026`, except get_operation_data, which
takes `YYYY-MM`; list_periods answers the months a company accepts. Lists
page with page and per_page (50 by default, at most 200). Six tools write:
import_accounts, import_trial_balance, import_invoices, import_bills,
import_journal_lines and import_operation_data. They are offered only when
the plan includes the API, the administrator allowed writing to that company
and this client is one writes are allowed for; a company outside that
allowance answers not_found. Each import answers the request's receipt, whose
id reads it back, and an import does not rebuild the group's figures by
itself - call trigger_consolidation after importing when the consolidated
figures must move. A read answers the organisation's own books by default;
consolidated=true on get_statement, get_trial_balance and get_kpi_value
answers a company with companies under it the consolidated figures of its
branch, and changes nothing for a group.
A description of its own sits beside every tool, and what is written under The tools is that description unchanged. It is how a model chooses between two tools that sound alike - the ledger or the reported statement, the document or the ledger line behind it - and how it learns what a tool refuses.
How it is discovered
A client is not configured on a screen here first. It reads what it needs from the endpoint itself:
| Step | Call | Answers |
|---|---|---|
| Probe | GET /mcp | 401 with a challenge naming the document
below; a caller that is already known is told 405, because the transport offers no
stream |
| Who guards it | GET /.well-known/oauth-protected-resource | The authorization server this endpoint belongs to |
| How to authenticate | GET /.well-known/oauth-authorization-server | The
authorization, token and registration endpoints, PKCE S256, and the client authentication
methods accepted |
| Register | POST /oauth/register | A client_id, registered as
the client arrives |
| Sign in | GET /oauth/authorize | The person's BrizoConsol sign-in, then a code sent to the client's redirect URL |
| Token | POST /oauth/token | An access token for one hour and a refresh token for thirty days |
| Use | POST /mcp | initialize, then tools/list and
tools/call |
That answer is one header, and it is the whole discovery:
WWW-Authenticate: Bearer realm="mcp", with resource_metadata pointing at
https://…/.well-known/oauth-protected-resource. Everything below is read from there.
There is no consent page between the sign-in and the code. An administrator has already said what an AI connection may read, and a person approving one chooses nothing of their own, so a second confirmation would only ask them to approve what they were never able to change.
Turning it on
AI Access, in the sidebar under Integrations, for an administrator of the group. Five things are saved together, and an allowance with no company or no read scope is refused rather than saved as a switch that answers nothing:
| Setting | What it decides |
|---|---|
| Allow AI connections | Off, an approved client is refused on every call |
| Companies they may read | The companies a connection may read, the group's own company among them - consolidated figures belong to it, so a connection allowed only subsidiaries answers no group question |
| Read scopes | Which reads are offered at all: a scope not held means its tools are never listed |
| Companies they may write | The companies an import may reach, drawn from the companies they may read. Empty is not an error: it is a group whose AI clients read and do not write |
| Write scopes | Which imports are offered at all, and whether the consolidation trigger is. Shown only on a plan that includes the API |
This is a ceiling, not a grant. A person approving a client gets the intersection of it with their own deployment, so someone deployed to one company reads that one company even when the ceiling names eight. A write narrows further: the person has to be able to administer that company's data, not merely report on it, so a Report Admin connects and reads, and every write is refused. Both are re-read on every call: closing the switch, narrowing a scope, dropping a company from the write list or moving a person ends the access at their next call rather than when their token expires.
AI access has its own switch and does not wait for API access to be turned on. What the two share is the subscription edition that offers either, and the scopes listed on Endpoints. The write half belongs to the Premium edition, and to one client: MCP Client by Zapier. Claude, ChatGPT and the desktop clients are offered the reads and never see a write tool.
Writing through a Zap
One rule explains all of it: a write tool answers the same call the endpoint answers, so an import by a Zap and an import by a connector store the same rows, answer the same receipt and leave the same trail entry. What differs is who is acting - a person's approved connection rather than a credential.
- The company has to be one the connection was approved for writing, and the person has to
be able to administer it. Any other id answers
not_found, the same answer the API gives, so an id cannot be probed. - Check first, then send. Every import takes
dry_run: with it set, the payload is validated and the answer says what would be accepted, and nothing is written. - A retry does not write twice. An import takes an optional
idempotency_key. Without one the payload itself is the key, so a retry of a call that timed out reads the request it already made. Change the payload, or state a key, to write a new request. - One write at a time per company. A second call while one is in flight answers
write_in_flightand writes nothing, rather than holding two workers over the same month. - The group's own limits apply. An import is capped by the group's records per request, the same figure Limits states for the API, and by the group's requests per minute on every call, read or write.
- The receipt names the request. Its
idreads back what was created, updated or rejected, and itsrecalculationsays whether the month has been rebuilt yet. - An import does not consolidate the group. A written month waits for the overnight run.
Call
trigger_consolidationafter importing when the group's consolidated figures have to move; repeating it while one request is pending answers the same request instead of creating another.
What is recorded, and what ends it
Every call is logged - the person, the client, the tool, the company, and whether it was answered, written, refused by the product, or denied before it ran. A write's line names the request it wrote, and the same import lands in the System Audit Trail as one entry naming the connection that sent it. AI Access lists the same calls beside each connection.
A refused call records only the company that was checked: an id for a company this connection does not hold is
answered not_found and records no company and no name, so another group's company cannot be
discovered through a guessed id.
Ending a connection removes the approval, every registration that person's client made, and the tokens the client already holds, so the next call is refused rather than waiting out the hour.
What it never does
- Writes outside its allowance. No tool writes to a company an administrator did not name for writing, to a company the person cannot administer, or on a plan that does not include the API.
- Writes for any client but Zapier's. The write tools are offered to a client whose registered callback host is Zapier's MCP client - the host the authorization code is delivered to, never the name a client gives itself. Every other client is offered the reads and never sees a write tool.
- Reaches another group. A company outside the group answers
not_found, the same answer the API gives, so a connection never learns whether that company exists. - Reads past the installation switch. With AI access off for the installation the
endpoint answers
404before authentication, and with it off for the group every call is refused. Writes have a switch of their own: with it off the write tools are not listed and a call naming one is refused.
The tools
Twenty-one reads over twelve read scopes, and - on the Premium edition, to Zapier's client - seven writes over
seven write scopes. Everything takes organisation_id - the id list_organisations
answers, as it does on the endpoints themselves - and states what it takes where the endpoint does. The whole
surface answers in one page of tools/list, so a client that reads the first page has all of
it.
pingno scope- Answers with the person the connection acts for, the companies it was approved for and the scopes it holds. Use it before reporting figures so the answer names whose data it is, and when a call is refused, to see what the connection actually carries.
list_organisationsreference.read- Lists the companies this connection may read, each with its currency, fiscal month start, reporting month and is_consolidate flag. Start here and retrieve all pages before deciding which entities are available. Each id is an organisation_id for the other tools: use a consolidated organisation for group totals and each approved subsidiary for its own figures. Group approval does not automatically approve its subsidiaries; only a company absent from the complete list is unavailable and will answer not_found.
list_account_typesreference.read- Lists the system account types every account is classified by, each with the side a positive balance sits on (debit or credit) and the statement it is reported in. Use it to interpret the `type` filter of list_accounts and the section names get_statement answers. It reads no figures.
list_sectionsreference.read- Lists the statement sections a figure is reported in, for one statement or for both. These are the section names get_statement returns, and the name to pass as `section` when asking get_statement with detail=true. It reads no figures.
list_tagsreference.read- Lists the tags of the accounting standards this group reports under, each classified by the statement it feeds. Use it to explain what a tagged figure means; no read takes a tag as a filter, so figures are asked for by company, month and account. It reads no figures.
list_currenciesreference.read- Lists the currencies in play for this group and whether a stored rate exists for each. Use it before presenting a figure in another currency: a code with has_rate false is refused as a presentation currency unless it is the company's own, and a missing rate is the usual reason a translated figure cannot be answered.
list_kpisreference.read- Lists the KPI names this group defines. A name here is what get_kpi_value takes as `metric`; a metric that is not in this list is answered not_found. It reads no figures.
list_periodsreference.read- Lists the months one company can report, oldest first, as `Mon-YYYY`. Use it to pick a period for a figure read. A month it does not list is still accepted - it simply has no figures - so this list is where the data is, not a filter the read enforces.
list_yearsreference.read- Lists the fiscal years one company can report, the forecast year first, as the reports label them. Use it when a question is asked by year: read one month with number_of_months (up to 120) to get a run of months in a single call, or ask get_consolidation with basis YTD for a year to date.
list_accountsaccounts.read- Lists one company's chart of accounts: code, name, class, type, status and standard tags, narrowed by status, system account type or code. Use the code with get_trial_balance or list_transactions to narrow to one account, and this list to answer what an account is rather than what it holds.
get_trial_balancetrial_balance.read- Reads one company's ledger account by account for a month, or the months ending at it: debit, credit, movement, balance and average for each account, in the currency and scenario asked for. This is the ledger itself; use get_statement for the reported sections, and get_statement with detail=true for the accounts behind one section. `period` answers the reporting month when omitted, `scenario` answers Actual. A company answers its own books by default; consolidated=true answers a company with companies under it the consolidated figures of its branch, and changes nothing for a group.
get_statementstatements.read- Reads one organisation's reported statement: a consolidated organisation_id gives group figures, while an approved subsidiary's organisation_id gives that entity's figures. For group and subsidiary revenue, discover all approved entities with list_organisations, then call this tool separately for the group and each subsidiary using statement=profit-loss. `statement`: profit-loss or balance-sheet answers the sections with their movement and balance; add detail=true and a `section` for the accounts inside it; cash-flow answers its lines for the month, or the year to date with is_ytd. Only cash-flow takes is_ytd, and only the other two take number_of_months, scenario, detail and section - a parameter the chosen statement does not take is refused. A company answers its own books by default; consolidated=true answers a company with companies under it the consolidated figures of its branch, and changes nothing for a group.
list_transactionstransactions.read- Lists one company's journal lines for a month: the lines the trial balance is built from, narrowed to one journal, one account code or one document. Use it to explain a movement or trace it to its journal rather than to total a month; totals belong to get_trial_balance. `period` answers the reporting month when omitted.
get_exchange_rateexchange_rates.read- Reads the stored rate for one currency pair and month, with its type (average or closing) and its source. Use it to explain how a translated figure was arrived at. `from` and `to` are required three-letter codes; a pair with no stored rate answers not_found.
get_kpi_valuekpis.read- Reads one KPI of one company for a month: this month, the year to date, last month, the change from last month, the target and the variance. `metric` is a name from list_kpis. Use it for a ratio the reports define rather than for a ledger figure, which is get_trial_balance. A company answers its own books by default; consolidated=true answers a company with companies under it the consolidated figures of its branch, and changes nothing for a group.
list_invoicesinvoices.read- Lists one company's invoices for a month: totals, tax, discounts, amount due and paid, and the posted status. This is the document view; use list_transactions for the ledger lines an invoice produced, and get_trial_balance for the receivable balance it sits in.
list_billsbills.read- Lists one company's bills for a month: totals, tax, discounts, amount due and paid, and the posted status. This is the document view; use list_transactions for the ledger lines a bill produced, and get_trial_balance for the payable balance it sits in.
list_operation_datasetsoperation_data.read- Lists the operational datasets one company holds - the non-ledger feeds it loads, such as headcount or units. A name here is what get_operation_data takes as `dataset`. It reads no figures.
get_operation_dataoperation_data.read- Reads one operational dataset of one company for a month: the rows as they were loaded, for one scenario, optionally narrowed to one value of the first dimension. Use it for the non-ledger feed behind a cost or volume, not for a balance - those are in get_trial_balance. `period` is required and is `YYYY-MM`, as list_operation_datasets and the reports state it.
get_consolidationconsolidation.read- Reads one group-level figure for a month, chosen by `dataset`: cta is the currency translation reserve report, nci the non-controlling interest report, journal-vouchers the consolidation journals, adjustments the adjusting entries, intercompany the intercompany analysis above a materiality threshold. subsidiary_id filters these consolidation reports, not revenue statements; use get_statement with each approved subsidiary's organisation_id for entity revenue or profit and loss. Parameters are per dataset: cta takes period, scenario, basis, flag, subsidiary_id; nci and journal-vouchers take period, scenario, basis, subsidiary_id; adjustments takes period, scenario; intercompany takes period, scenario, flag, materiality - one it does not take is refused. Defaults: period is the reporting month, scenario Actual, basis YTD, flag local, materiality 0.5.
list_intercompany_transactionsintercompany.read- Lists the intercompany postings of a group for a month: the elimination entries that take one company's balance against another's, each naming the two companies, the amount, the line count and the accounts it touches. Use it to explain why a consolidated figure differs from the subsidiaries added up - revenue lower than the parts, a loan that nets out - rather than to total a month. A subsidiary holds none of these; ask for the group's own id. `period` answers the reporting month when omitted.
The write tools
Seven tools, offered only on the Premium edition and only to Zapier's MCP client, and only to a person who may
administer the company they name. Each import answers the same path the endpoint answers - so what it stores,
what it refuses and what it records are the endpoint's own - and every one of them takes
dry_run to check a payload without writing it.
import_accountsaccounts.write- Imports a company's chart of accounts. Sends records to the same contract as POST /api/v1/organisations/{organisation}/accounts: code, name, system account type and status. A chart carries no month, so there is no period and no amount. mode merge updates the codes you send and leaves the rest; replace_all retires the codes you did not send. The answer is the request's receipt - read it back with its id, and use trigger_consolidation when the group's figures must move.
import_trial_balancetrial_balance.write- Imports one company's trial balance for one month, to the same contract as POST /api/v1/organisations/{organisation}/trial-balances. The month is YYYY-MM or YYYY-MM-DD; scenario Actual writes the ledger and Budget or Forecast write the plan where the group accepts plan input. A trial balance month is sent whole, so mode is always replace_period and merge or replace_all are refused. switch_source states that this source takes the month over from another one. The receipt names the request id and its recalculation state; the month is rebuilt overnight unless trigger_consolidation asks for the group run.
import_invoicesinvoices.write- Imports sales invoices for one month, to the same contract as POST /api/v1/organisations/{organisation}/invoices. Each record is one document, identified by external_id, with its party, date, amounts and lines. mode replace_period (the default) replaces the month for your source reference. The receipt names the request id and what was created, updated or rejected.
import_billsbills.write- Imports supplier bills for one month, to the same contract as POST /api/v1/organisations/{organisation}/bills. Each record is one document, identified by external_id, with its party, date, amounts and lines. mode replace_period (the default) replaces the month for your source reference. The receipt names the request id and what was created, updated or rejected.
import_journal_linestransactions.write- Imports journal lines for one month, to the same contract as POST /api/v1/organisations/{organisation}/transactions. Each line is identified by journal_external_id and line_external_id and carries its date, account code, side, amount and currency. A journal that does not balance within the payload is refused before anything is written. mode replace_period (the default) replaces the month for your source reference. The receipt names the request id and what was created, updated, suppressed or rejected.
import_operation_dataoperation_data.write- Imports operational figures for one month, to the same contract as POST /api/v1/organisations/{organisation}/operation-data. Each record carries its period, its dimension values, an optional account code and the figure. The dataset a figure belongs to is declared by the feed, so use list_operation_datasets to see what the company reports. mode replace_period (the default) replaces the month for your source reference.
trigger_consolidationconsolidation.trigger- Asks for the group to be consolidated in the next overnight run, as POST /api/v1/organisations/{organisation}/consolidation-requests does. An import stores its month and answers; the figures are rebuilt by that run, so call this after importing when the group's consolidated figures must move. It is safe to repeat: while a request is pending the same one answers with deduplicated true, and nothing else is created. The answer names the request to read back.