fiscai-yuki-api-connector
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
Powered by FISCALCI Accounting & Tax (Askin Alci)
Author: Askin Alci
Belgium. Made for Belgian accountants and bookkeepers: it follows the Belgian chart of accounts (MAR) and Belgian VAT. Outside Belgium, check the local rules yourself.
Nederlandse samenvatting. Bedoeld voor Belgische boekhouders/accountants; gebaseerd op Belgische boekhoud- en btw-regels (MAR, Belgisch btw-stelsel). Gebruik buiten België: verifieer zelf de lokale regels. Zie README.nl.md voor de volledige Nederlandse uitleg.
Contents
What it does · How it works · Example output · Install in Grok Bot · Other MCP clients · Configuration · Security and safety · Tools · Limitations · FAQ · License
Agents. Ready-made agent definitions for Grok Bot, Claude, GitHub Copilot, Cursor, OpenAI Agents SDK and open models; see also AGENTS.md.
Command line and hooks. CLI reference (yuki-api-connector doctor | tools | call | export | dashboard | serve) and Hooks (off by default, no secrets).
Postman. Collection for the read calls (file-based, complementary to the official Yuki Postman documentation; not an official Yuki or Visma product).
Project health. Troubleshooting and FAQ · Privacy and data flow · Errors, logging, timeouts and limits · Roadmap · Code of conduct · Security
Related MCP server: aruba-fatturazione-elettronica-mcp
What it does
FISCAi Yuki API Connector is first and foremost a plugin for Grok Bot. It is a local MCP server (stdio), bundled with a Grok Bot-ready skill, that lets Grok Bot read your Yuki administrations: balances, ledger entries, open debtor and creditor items, VAT returns, contacts and archive metadata. On top of the raw data it adds deterministic analyses and drafts, always with the Yuki method used as the source.
70 tools, all read-only unless you switch on the optional booking workflow.
Analyses: ageing of open items (not yet due, 0-30, 31-60, 61-90, over 90 days), DSO/DPO, top relations, period comparison, margin and cost structure, liquidity ratios, outliers in the ledger.
Dashboard as an MCP app widget and as a static HTML export to a folder you choose.
Draft reminder emails (text, HTML, optional
.eml) for open items. The plugin contains no mail or network-send code and never sends anything.Guidance on positive and negative balances, and matching proposals for negative open items (proposals only).
Made for Grok Bot, usable from other MCP clients (Cursor, Claude, Copilot, Windsurf ...).
Your own key, your own computer: no central server, no shared cache, no data to third parties.
How it works

flowchart LR
A[AI assistant<br/>Cursor] -- MCP over stdio --> B
subgraph LOCAL[Your computer]
B[FISCAi Yuki API Connector<br/>70 tools] --> C[Safety layer<br/>allow-list, daily limit,<br/>cache, scrubbing]
C --> D[SOAP client<br/>read-only]
B -.-> E[Booking workflow<br/>OFF by default]
E -.-> D
B --> F[(Local files<br/>cache, counter, audit)]
B --> G[Exports<br/>dashboard, draft mail]
end
D --> H[Yuki web services<br/>your own key]Example output

Illustration with made-up [Voorbeeld] data, rendered from the real function output. It is not a Yuki screen and contains no client data.
Install in Grok Bot (recommended)
This repository is a Grok Bot plugin: it contains the plugin manifest (plugin.json, .cursor-plugin/plugin.json), the MCP server definition (mcp.json), and a skill (skills/fiscai-yuki-api-connector/SKILL.md) that tells Grok Bot when and how to use the tools.
Requirements: Python 3.10 or higher and a Yuki API key (portal key or domain key).
Get the code and install the two free dependencies:
git clone <repository-url> fiscai-yuki-api-connector cd fiscai-yuki-api-connector python3 -m venv .venv .venv/bin/pip install -r requirements.txt # httpx and cryptographyAdd the folder to Grok Bot as a plugin (from the repository or from the local folder) and fill in the variables it asks for. At minimum:
YUKI_ACCESS_KEY. Enter the key in Grok Bot's own settings; never put it in a file or in the chat. The exact menu names depend on your Grok Bot version.Ask Grok Bot: "Run
yuki_status". It makes no Yuki call and confirms the setup. Then try: "Give me the ageing of the debtors of [Voorbeeld] as of 30/11/2026."
Grok Bot keeps writing to Yuki off: the optional booking workflow stays disabled unless you set YUKI_WRITE_ENABLED=ja yourself.
Quickstart (command line)
After the install steps above (about five minutes if Python 3.10+ is present; not timed):
export YUKI_ACCESS_KEY=... # your own key; never commit it (or: yuki-api-connector config init)
yuki-api-connector doctor # checks Python, packages and variables; prints no secrets
yuki-api-connector tools --names-only
yuki-api-connector call yuki_administraties --json
yuki-api-connector dashboard --administratie "[Voorbeeld] BV" --jaar 2026 --dry-run # drop --dry-run for a real callWithout installing the package use python3 server/run_connector.py .... Full reference: docs/CLI.md.
Automation and reminders. Meeting preparation and recurring obligations (yuki-api-connector workflows plan | run | list): overviews you define, draft reminder e-mails, never sent by default; read-only for Yuki.
Manuals and dossier transfer. Complete manual (EN) · Volledige handleiding (NL) (printable PDF and DOCX in docs/manuals/) · Dossier transfer per fiscal year (yuki-api-connector transfer export).
Other MCP clients (Cursor, Claude, Copilot, Windsurf ...)
The server speaks the standard MCP protocol over stdio, so other MCP clients can use it too. Setup differs per client. Example for Cursor (~/.cursor/mcp.json or .cursor/mcp.json in a project): use the absolute path of your checkout and let the client read the key from your environment; never paste a key into a file:
{
"mcpServers": {
"fiscai-yuki-api-connector": {
"command": "/absolute/path/to/fiscai-yuki-api-connector/.venv/bin/python",
"args": ["/absolute/path/to/fiscai-yuki-api-connector/server/run_server.py"],
"env": {
"YUKI_ACCESS_KEY": "${env:YUKI_ACCESS_KEY}",
"YUKI_ACCESS_LEVEL": "portaal"
}
}
}
}The same command, arguments and environment variables apply in Claude, Copilot, Windsurf and other clients; use that client's own syntax for MCP servers. The bundled skill is written for Grok Bot; other clients simply use the tool descriptions.
Compatibility and guides
Client or platform | Role | Guide | Verified |
Grok Bot | recommended: plugin + skill | primary target | |
Cursor | MCP client | config format checked in official docs | |
Claude Desktop | MCP client | config format checked in official docs | |
Claude Code | MCP client | config format checked in official docs | |
GitHub Copilot (VS Code) | MCP client | config format checked in official docs | |
Windsurf | MCP client | verify current client docs | |
Any MCP client | stdio | standard MCP | |
Hermes Agent (Nous Research) | agent with native MCP | checked in official docs | |
OpenClaw | agent gateway with MCP registry | checked in official docs | |
AgentMail | companion server for mail drafts | checked in official docs |
Configs were checked against each project's official documentation on 2026-11-20 and not tested live in every client. All examples are in examples/ and use placeholders for keys.
For business owners. Read your own Yuki administration and build a dashboard: docs/business-owners. Read-only, with yuki_dashboard_kpis.
For accountants (portal key). Portfolio overview across files: docs/accountants-portal, with yuki_portfolio_kpis.
More integrations. Visualisation and data apps (Power BI, Qlik Sense, Domo, Looker Studio, Tableau, Lovable, Metabase, Superset, Grafana, Streamlit, Dash, Hex, Snowflake) on one export schema (yuki_export_dataset: CSV, JSON, xlsx, Parquet) · Document generation · Data collection · Automation · 40 useful apps. Optional console command after pip install .: fiscai-yuki-api-connector.
Configuration
All settings are environment variables. YUKI_ACCESS_KEY is the only required one.
Variable | Meaning | Default |
| Your Yuki access key (secret; alias | required |
|
|
|
| Optional strong secret for the local encrypted session cache. Without it a key is created once in the data folder (mode 0600). | automatic |
| Daily call limit per domain. Yuki: 1,000 calls per domain per day are free. |
|
| Needed only above 1,000: your explicit confirmation (costs may follow). | empty |
| Domain label used to count calls that name no domain. | key-dependent |
| Folder for cache, counter and audit log. |
|
|
|
|
|
| off |
| Lifetime of a confirmation token in minutes (1 to 60). |
|
| Maximum bookings per day (1 to 100). |
|
| Your own branding of dashboard and guide. | neutral |
| Text under the closing line of draft emails. |
|
Per-domain keys: YUKI_ACCESS_KEY_<DOMAIN> plus the domein parameter per call.
Daily call limit. Yuki includes 1,000 calls per domain per day for free. The plugin blocks hard at 900 per domain per day by default (YUKI_DAILY_LIMIT). Above 1,000 it needs your explicit confirmation and warns that costs may follow.
Security and safety
Read-only by default. Without
YUKI_WRITE_ENABLED=jano tool can book, upload or change anything in Yuki. AllProcess*,Upload*,Update*andSet*methods are refused, also by prefix.Optional booking workflow, off by default. When you switch it on, only
Accounting.ProcessJournalis used, one journal entry per explicit confirmation: proposal first, a one-time token bound to the administration and the exact journal, a double-entry check, a daily maximum and an audit log. See docs/BOEKINGSWORKFLOW.md.Workflow documents are not booked as journal entries. Purchase and sales invoices waiting in Yuki's back office are finished with the Afhandelen button in Yuki. The plugin refuses to turn such a document into a journal entry (that would double the cost) and offers
yuki_afhandeling_controleto check afterwards, read-only, that the document left the workflow. To "book in Yuki" means: back-office status Afgehandeld.Secrets stay in the environment. Keys are never written to files, logs or tool output (output is scrubbed). Session cache and call counter are local, encrypted or mode 0600.
Exports only where you say. Dashboards, guides and drafts are written to a folder you choose.
Mandatory attribution. The text Powered by FISCALCI Accounting & Tax (Askin Alci) is checked at start-up and in every export, as required by
NOTICE.
Please report vulnerabilities privately, see SECURITY.md.
Tools
Group | Tools | Examples |
Status and limits | 1 |
|
Administrations and domains | 5 |
|
Balances and general ledger | 11 |
|
Open items | 3 |
|
Analyses | 7 |
|
Dashboard, drafts and guidance | 6 |
|
Key figures and export (read-only) | 4 |
|
VAT, projects and master data | 7 |
|
Contacts | 2 |
|
Archive (metadata only) | 18 |
|
Backoffice and optional booking workflow (writes OFF by default) | 6 |
|
The complete list with descriptions is in docs/TOOLS.md. The Yuki methods that are allowed or deliberately excluded are in docs/INVENTARIS-LEESMETHODES.md. Tool names and tool descriptions are in Dutch.
Limitations
Built for Belgium (MAR, Belgian VAT). Elsewhere, verify the local rules yourself;
yuki_rgs_schemais a Dutch reference that is normally not used in Belgium.Archive tools return metadata only, never the files themselves.
The Yuki API has no documented method to set an existing workflow document to Afgehandeld; that step stays with a person in Yuki.
The optional booking workflow was tested with mocks and synthetic data only. Test it first in a test administration and let your accountant check the first entries.
You need a Yuki API key; free call quota per domain per day applies.
Not approved or endorsed by Yuki or Visma. Yuki is a trademark of its owner.
FAQ
Is this only for Grok Bot? It is built as a Grok Bot plugin and that is the recommended route. Because it is a standard MCP stdio server it also works in other MCP clients; see the section above.
Does it send data anywhere? Only to the Yuki web services you already use, from your own computer with your own key. There is no server of ours in between.
Can it change my bookkeeping? Not unless you set YUKI_WRITE_ENABLED=ja, and then only one confirmed journal entry at a time. Workflow documents are always excluded.
Does it send emails? No. It builds a draft that you review and send yourself.
Why do I see a daily limit? To protect your Yuki quota. Raise or lower it with YUKI_DAILY_LIMIT; check yuki_status first for big tasks.
Can I use it outside Belgium? The read tools work with any Yuki administration, but the analyses and booking proposals assume the Belgian MAR and VAT. Check local rules.
Can I run the tests? Yes: .venv/bin/python -m pytest -p no:cacheprovider -q tests. They use mocks only and make no Yuki calls.
License
Apache-2.0, see LICENSE. The attribution in NOTICE must be kept. Contributions: see CONTRIBUTING.md.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Read-only access to Dutch accounting: Exact Online, Moneybird and SnelStart.
Read Yuki administrations, open invoices, ledger balances, contacts and documents.
Read-only NuMetric.work accounting & ERP data: statements, KPIs, reports, invoices, documents.
Read-only access to your Fidexa books: transactions, totals, mileage and tax report.
Related MCP Servers
- AlicenseAqualityCmaintenanceRead-only access to Wise (TransferWise) personal API for profiles, balances, exchange rates, transfers, and recipients.11125 npmMIT
- FlicenseCqualityCmaintenanceExposes read-only Aruba Fatturazione Elettronica API operations for managing electronic invoices, notifications, and providing fiscal document helpers.702-
- AlicenseNot gradedqualityCmaintenanceProvides read-only access to Xledger accounting data via GraphQL API for querying invoices, balances, projects, timesheets, and more.2MIT
- AlicenseAqualityBmaintenanceEnables interaction with the Bokio accounting API for managing journal entries, invoices, customers, items, and more, with read-only mode by default for safety.3785 npm3MIT