Skip to main content
Læs siden på dansk The Uniconta connector gives your AI access to your accounts in Uniconta: debtors with their invoices, orders, entries and open items, creditors and debt, the chart of accounts with balances, ledger entries, VAT codes, inventory transactions and inventory, without exports or spreadsheets. It can also work in the daily journal: create, edit and delete journal lines and post exactly the lines you point out, always behind clear guardrails. You connect with a dedicated Server-Login User (username and password) and a Company ID via a form in the portal, not with a login redirect. Your AI never sees the login itself.
Read + guardrailed write. Managed MCP for Uniconta, EU-hosted. 21 tools only read. The 4 write tools only work in the daily journal and change nothing in Uniconta without an explicit confirmation (confirm: true). Without it, you only get a preview. Posting only happens for the lines you have seen and confirmed. Nothing else in Uniconta can be changed. An administrator can set the individual user to Read only. See Actions & guardrails.

Access

Read + guardrailed write in the daily journal. Read only can be chosen per user

Authentication

Server-Login User + Company ID

Hosting

Hosted in the EU · Frankfurt
  • Price: 299 DKK/month excl. VAT. No lock-in, cancel at any time. The price covers 1 user and 1 company (agreement). Each extra user and each extra agreement costs 149.50 DKK/month excl. VAT. See Pricing. Uniconta is also included in the Consile Studio membership and the free edition.
  • Users: whoever buys Uniconta automatically gets the included access. If more colleagues need Uniconta in their AI, an administrator gives them access under Team in the portal (next to Uniconta on the person’s page) and chooses their access level at the same time (see Access level per user). An extra user is billed pro rata from the day access is given. A colleague without access can still see the tools in their AI, but every lookup is refused with a message to ask an administrator for access. One access covers all your Uniconta agreements. If you have the Consile Studio membership, an administrator instead gives one membership licence per person, and it also covers Uniconta. The access level is still chosen per person. See Team.
  • Multiple companies: one connection covers one company (one Company ID). If you have several companies, an administrator adds them directly on the connector’s page in the portal: the Connections card → Add agreement. Each extra agreement gets its own address, for example https://mcp.consile.ai/uniconta-2/mcp, and is connected with Connect and its own Company ID. Add each address as its own connector in your AI. See Connect Uniconta.
  • Endpoint: https://mcp.consile.ai/uniconta/mcp (your own named connector in Claude).

​
Prerequisites

1

Subscription

The connector must be bought in the portal. See Buy a connector.
2

Your AI connected

See Connect Claude or Connect ChatGPT.
3

Uniconta connected

Create a dedicated Server-Login User in Uniconta and enter the username, password and Company ID in the portal. See Connect Uniconta.

​
What can it do? (tools)

You do not need to know the tool names. You ask in natural language, and your AI picks the right one itself. The connector provides 25 tools: 21 only read, and 4 write in the daily journal. A user who is on Read only only gets the 21 (see Access level per user). If you bought Uniconta before October 7, 2026, an administrator must first activate the six daily journal tools (see Activating the daily journal). Here they are grouped by what they answer: Companies Debtors Creditors Finance / general ledger Inventory Advanced Daily journal (reading)

​
Writing in the daily journal (4 guardrailed tools)

These four tools are the only ones that change anything in Uniconta, and they only work in the daily journal. Customers, suppliers, items, invoices and posted entries cannot be changed. A call without confirm: true never changes anything, but shows exactly which change would be sent. Normally your AI shows you the preview and only calls again with confirm: true once you have said yes. The tools are called uniconta__<tool> (for example uniconta__get_account_balance) when your AI calls them. You only need to ask the question in natural language.
Questions about the newest item cannot be answered yet. Uniconta stores no creation date on items, and the tool list_recently_added_items is not available yet: it only answers with a message saying so. If you want to see the items that most recently had an inventory movement, ask for items sorted by latest movement (list_inventory_items with sortBy: last_movement).

Building on top yourself? See the API reference

Full reference with all 25 tools, arguments, filters, paging, guardrail fields and return values.

​
How the guardrail works

The guardrails are built into the Uniconta tools:
  1. All four write tools are dry-run by default. A call without confirm: true never changes anything in Uniconta. You get a structured preview of exactly the change (method, path and content) that would be sent, with a summary of the number of lines and totals.
  2. The change is only carried out with confirm: true. In accounting there is no write without consequences, so there are no exceptions. Posting also requires a check value from the preview and therefore always takes two calls.
  3. Posting has an extra guardrail. post_journal_lines only posts the line ids you specify, at most 50 at a time and never the whole journal. The preview shows each line, the totals and how many other unposted lines in the journal are not included. If a line’s date, account, contra account, amount, VAT, text, voucher, invoice or due date has changed between preview and confirmation, the posting is refused, and nothing is posted. Posting cannot be undone.
  4. The result is checked. After the posting, the connector reads the journal again and reports which lines were posted, which, if any, are still unposted, and how many lines are left in the journal.
  5. Only unposted lines can be changed. Posted entries can neither be edited nor deleted in Uniconta. Corrections are made with a new reversing entry.
  6. One journal at a time. Lines are always addressed by their line id within one daily journal. A blocked journal is refused.
  7. Edits keep the rest of the line. update_journal_lines only changes the fields you specify. The confirmation call applies your changes to the line as it looks at that time.
  8. Uniconta has the last word. If the server user lacks rights, or Uniconta does not know an account, Uniconta refuses the change. Your AI is shown Uniconta’s reason, so it can correct the proposal, and nothing is changed.
In practice your AI normally shows you the plan first and only sends confirm: true once you have said yes. It is the call with confirm: true that actually changes something in Uniconta.
Read the whole confirmation model, which applies across all write connectors, under Actions & guardrails.

​
Activating the daily journal

The six daily journal tools were released on October 7, 2026: list_journals, list_journal_lines and the four write tools. New tools are never added to your AI unless you choose to add them.
  • Bought before October 7, 2026: the six tools are switched off for the organization until an administrator activates them. Until then, your AI has the other 19 read tools. The Uniconta page in the portal says 6 new tools since you bought Uniconta. An administrator clicks Activate all 6 or switches them on one by one, for example only the two that read.
  • Bought on October 7, 2026 or later: all 25 tools are switched on from day one.
An administrator can also switch any tool off for the whole organization. See Tools and new tools.

​
Access level per user

An administrator can choose the access level for each user in the portal under Team: click the user’s name, and for Uniconta choose between None, Read only (21), Full access (25) and Custom, where you choose exactly the tools the user gets (see Custom access). The numbers count the tools the organization has switched on.
  • Both levels cost the same.
  • The level applies to the user’s access to all your Uniconta agreements.
  • If a user is on Read only, Consile blocks all write operations on the server for that user: the write tools do not show in the user’s AI, and a call to them is refused without anything being changed.
  • If a user has not been given a level, Full access applies. The level only gives the tools the organization has switched on. If the daily journal is not activated yet, a user with Full access gets the 19 tools you already had.
  • If an open conversation has already fetched the tool list, the write tools can still be there until the user starts a new conversation. Calls to them are refused.
  • Only administrators can change the level. If you choose a level for a user who does not have access to Uniconta yet, the user gets access at the same time. If it is an extra user, you confirm the purchase first.
Uniconta also decides for itself. If the server user only has read access in Uniconta, Uniconta refuses all writes, whatever the level in Consile. If your AI should be able to create and post journal lines, the server user needs write access to the daily journal and the right to post. See Connect Uniconta.

​
Try asking

“What is the balance on account 1010 right now?”
“Show the chart of accounts with balances for the revenue and expense accounts.”
“Which debtors have the largest open items right now?”
“Show unpaid invoices for customer 1024.”
“How much do we owe our suppliers in total?”
“Show the ledger entries on account 1010 for May.”
“How many units did we sell of item group X this year?”
“Show the contribution margin per item group across the whole item register.”
“Create a journal line in the daily journal: 1,250 DKK office supplies on account 3617 with contra account 5820, dated today.” (you get a preview and must confirm)
“Show the unposted lines in the daily journal, and post the ones I approve.” (posting always requires a preview and your confirmation)
Mention the account number or the debtor account in the question if you know it. That gives a precise answer right away. Several tools can also be narrowed by date range.

​
Limitations

  • Only writes in the daily journal: the read tools, including query and aggregate, can only read and cannot change anything. The only changes the connector can make are the four daily journal tools above, and they always require your confirmation. Customers, suppliers, items, invoices and posted entries cannot be changed.
  • Writing requires rights in Uniconta: the server user needs write access to the daily journal and the right to post. With a pure read role, all read tools work, but Uniconta refuses every write, and nothing is changed.
  • Requires a Server-Login User: a regular user or a “Workapp user” does not work. A dedicated user must be created with User type = Server user. See Connect Uniconta.
  • Check the connection after setup: ask your AI a simple question, for example about the balance on an account. If the username, password or Company ID is wrong, you get an error instead of an answer: a message that Uniconta refused the login and that a reconnect is needed (reconnect required), or the general error “Tool invocation failed.” An administrator then disconnects and reconnects with correct values, or asks your AI for a new connection link in the connector that belongs to the agreement (for example uniconta-2). If you ask “Which Uniconta company are you connected to?”, and your AI finds no company, the login works, but the Company ID is wrong. See If a lookup fails. If you set an expiry on the server user in Uniconta, the connection stops working when it expires.
  • Results are limited in size: each lookup returns up to 50 rows by default (max. 1,000). A broad lookup without narrowing in a large entries table can take a long time or fail. So narrow it down with a search, account or date range, or use aggregate for totals per group.
  • User-defined fields: the company’s own fields only exist on the …ClientUser variants (for example InvItemClientUser). On the base entity, a filter on a user-defined field is ignored without an error message.
  • Missing rights give an error, not an empty answer: if the server user or the company lacks rights to, for example, an entries table, Uniconta refuses the lookup. Your AI gets the general error “Tool invocation failed.” instead of “0 rows”. Give the server user read access to the parts of the accounts you want to ask about.
Is something not working as expected? See Troubleshooting.