Menu
Getting started
Cookbooks
API reference
- Overview
- Companies
- Capabilities
- Measures
- Packages
- Unexplained
- Liquidity forecast
- Portfolio
- Customers
- Invoices
- Collections
- Articles
- Set-offs
- Suppliers
- Supplier invoices
- Supplier payment files
- Bank payments
- Expense claims
- Transactions
- Reconciliation
- Bank accounts
- POS sales
- Webshop orders
- Journal entries
- Voucher gap explanations
- Fiscal periods
- Accounts
- Accrual schedules
- Agreements and commitments
- Tax loss carry-forwards
- Fixed assets
- Documents
- Signing requests
- Company registers
- Capital events
- Owner tax
- Inbox items
- Dimensions
- Employees
- Salary runs
- Reports
- Budgets
- Imports
- Compliance check
- Deadlines
- Skatteverket
- Peppol
- Webhooks
- Operations
- Pending operations
- Health
- API key
- Service accounts
Connect with Claude
Talk to your bookkeeping. Connect Accounted to Claude (claude.ai, Claude Desktop, or Claude Code) and ask questions, categorise transactions, and prepare a momsdeklaration in plain language: every write still stages for your approval first.
Den här sidan på svenska: Anslut Claude.
Accounted ships an MCP server that exposes the full bookkeeping engine (150+ tools) to any MCP client. The endpoint is:
https://app.accounted.se/api/extensions/ext/mcp-server/mcp?tool_namespace=accounted
There are three ways to connect, depending on your client. All three reach the same tools and the same approval model: read tools answer immediately, write tools (categorise, mark paid, create voucher, year-end) stage a pending operation that you approve under To do › Routine (/pending) in the app, or in chat if you ticked Godkänn when you connected, before anything is booked.
Path A: claude.ai or Claude Desktop (one click)
The link opens claude.ai with the connector name and URL already filled in. You review the values and confirm; the link only prefills the dialog, it grants nothing on its own. No API key to manage.
You do not need an Accounted account yet. Adding the connector opens the Accounted sign-in straight away, and a new user creates the account right there (BankID or e-mail + 2FA).
Claude Team or Enterprise? There, only the organization's owners add connectors, and the link above does not work for other members. If an owner has already added Accounted: open Customize → Connectors in Claude, pick Accounted and click Connect. Every person signs in with their own Accounted account, so several people in the same company can be connected at once.
Everything except Approve pre-selected, every bookkeeping write still staged. The consent page pre-selects every permission except Godkänn (approve), so one click gives Claude read and write access while the final approval stays with you. Expand Behörigheter and choose Endast läs to connect read-only (list invoices, read reports, compute VAT): a reviewer can do that while you keep a write-enabled connection for daily work. Tick Godkänn only if Claude should approve its own proposals in chat. Whatever the scopes, write tools (create invoice, categorise, book vouchers, run year-end) only stage a pending operation that you approve before anything is booked, and the grant can be revoked under Agents › Connect an agent (/settings/api).
What happens after you click
The rest of the setup happens on Claude's side, in this order:
- The connector dialog. claude.ai opens Add custom connector with the name and URL filled in. Check the URL and continue: the dialog detects that the server requires a sign-in (Always required) and that Claude can register itself automatically. Keep those and click Add. Claude Desktop shows the same dialog under Settings → Connectors.
- The sign-in opens. claude.ai asks you to connect and opens the Accounted sign-in (BankID or e-mail + 2FA), followed by the consent page. It shows your company with every permission except Godkänn pre-selected. With several companies it lists all of them, the one active in the app first, and you choose Läsa och skriva, Bara läsa or Ingen åtkomst for each; expand Behörigheter and choose Endast läs for a read-only connection. Approve, and the connector shows as connected with the Accounted tools listed.
- Ask your first question. For example "Which company am I connected to?". From here every question runs against that company; writes stage at /pending until you confirm.
Signed in, but Claude still says it cannot reach the server? Ask again in the same chat first. If that does not help, open Settings → Connectors, remove the connector, and add it again from the link above, with authentication left on Always required.
Adding it by hand instead
In claude.ai (Settings → Connectors) or Claude Desktop (Settings → Connectors → Add custom connector), choose Add custom connector and paste:
https://app.accounted.se/api/extensions/ext/mcp-server/mcp?tool_namespace=accounted&client=claude-connector&auth=required
Keep all three parameters. tool_namespace=accounted selects the tool names this guide uses. auth=required makes the dialog detect the sign-in (Always required): without it the server accepts an anonymous handshake, the dialog suggests None, and a connector added with that default never opens the sign-in. If you do add the bare URL, choose Required when the server asks by hand. client=claude-connector is telemetry-only.
Path B: Claude Code (plugin)
Best in the terminal. The plugin installs the connection and eight workflow skills that follow the Swedish bookkeeping rhythm, plus two commands (/accounted:setup and /accounted:use).
/plugin marketplace add erp-mafia/accounted
/plugin install accounted@accounted
Then run /mcp and sign in with Accounted (the same OAuth consent screen as Path A). Start with /accounted:start.
| Command | What it does |
|---|---|
/accounted:setup | First run: connect (create the account if needed) and set up the company from the conversation |
/accounted:start | Connect, orient, and surface what needs attention |
/accounted:bookkeep | Clear unbooked bank transactions and receipts |
/accounted:check | Read-only health check with a prioritized fix list |
/accounted:month-close | Close the month against the product's checklist |
/accounted:vat | Prepare and reconcile the momsdeklaration |
/accounted:payroll | Monthly salary run and AGI underlag |
/accounted:year-end | Bokslut, readiness-gated |
/accounted:clients | Every company on the connection in one table, urgency first |
/accounted:use | Pin the current folder to one company |
Prefer plain MCP without the workflow commands? claude mcp add wires the same connection into Claude Code:
claude mcp add --transport http accounted \
"https://app.accounted.se/api/extensions/ext/mcp-server/mcp?tool_namespace=accounted&client=claude-code"
Cursor has no plugin format and does not read claude mcp add. Add the server to ~/.cursor/mcp.json (global) or .cursor/mcp.json (per project) instead:
{
"mcpServers": {
"accounted": {
"url": "https://app.accounted.se/api/extensions/ext/mcp-server/mcp?tool_namespace=accounted&client=cursor"
}
}
}
Path C: npx accounted-mcp with an API key (stdio bridge)
Best for Claude Desktop on a machine where you'd rather use a long-lived API key than the OAuth flow, or for scripting.
- Mint an API key in Accounted under Agents › Connect an agent (
/settings/api, the Developers group). Agnubok_sk_test_*key reads your real company but never writes: a write that supports a dry run is forced into one, and a write that cannot be simulated (for exampleaccounted_categorize_transaction) is refused, so it is safe while you evaluate; switch to a live key (gnubok_sk_*, notest_infix) when you want writes to commit. - Add the stdio bridge to your
claude_desktop_config.json:
Running Accounted yourself? Point the bridge at your own host with{ "mcpServers": { "accounted": { "command": "npx", "args": ["-y", "accounted-mcp"], "env": { "ACCOUNTED_API_KEY": "gnubok_sk_test_...", "ACCOUNTED_CLIENT": "claude-desktop" } } } }ACCOUNTED_URL. - Restart Claude Desktop. The bridge proxies stdio JSON-RPC to the hosted MCP endpoint over HTTPS; the key carries the scopes you granted it at mint time.
The key's scopes gate exactly which tools are callable: a key without write scopes can read reports and ledgers but cannot stage a booking.
The API-key value still begins with gnubok_sk_. That is a stable credential
format, not the MCP integration name. Existing gnubok-mcp configurations
continue to work without changes.
Several companies, one connection
The connection is issued to you, not to a company: one sign-in or one API key reaches every company you are a member of. accounted_list_companies lists them, with is_default marking the one used when a call names no company_id. Every tool result starts with company: { company_id, name, is_default }, so you always see whose books an answer came from.
Ask about all of them at once: accounted_client_overview returns one row per company (unbooked items, inbox, next deadline, last booked entry) and accounted_run_across_companies runs one read tool per company and summarises the results. Byrå teams pass scope: { companies: "team" } to cover every client the team works on. A write for several companies stages one pending operation per company under a shared batch_id; low- and medium-risk operations can be approved together, high-risk ones one by one.
In Claude Code, pin a folder to one company with /accounted:use <name or organisationsnummer>: it writes .accounted.json there, and every flow started from that folder targets that company. One folder per client is the byrå pattern; /accounted:clients shows the whole portfolio from anywhere.
A key can also be limited to some of your companies when you create it or connect, and a limited key never reaches the others, however the call is phrased. For each company you also choose Read and write or Read only: in a read-only company the agent can read everything but change nothing, whatever permissions the key has. To lock one connection to a single company, add ?company=<company id> to the endpoint URL (or set ACCOUNTED_COMPANY for the bridge): the company switch disappears entirely, every call runs for that company, and a call naming another company_id is refused.
Try these prompts
All three are read-only and safe to run against your real company (with a gnubok_sk_test_* key nothing can be booked at all). They exercise the read path end-to-end without booking anything.
- "Show my uncategorized bank transactions and suggest categories."
Claude calls
accounted_list_uncategorized_transactionsthenaccounted_suggest_categoriesand walks you through the proposals. Approving one stages anaccounted_categorize_transactionpending operation: nothing is booked until you confirm. - "Which invoices are overdue?"
Claude reads
accounted_get_ar_ledger(kundreskontra) throughaccounted_call_tool, since the ledger is outside the default tool list, and lists outstanding customer invoices with aging. - "Compute my VAT report for this quarter and tell me if I can close it."
Claude calls
accounted_get_vat_reportfor the momsdeklaration rutor, thenaccounted_vat_close_checkto scan for blockers (uncategorised rows, unapproved supplier invoices, missing receipts on expenses ≥ 4 000 kr: the tool's high-value heuristic; BFL requires underlag for every affärshändelse regardless of amount) and reportsready_to_close.
10-minute reviewer test
A quick end-to-end pass to confirm the connection works before you trust it with real data. Run the steps in order; each lists what you do and what you should see.
- Connect. Use Path A or Path B with the default permissions. (A read-only connection or a
gnubok_sk_test_*key covers steps 2 to 5 but cannot stage the write in step 6.) → Claude lists the Accounted tools (titles like List Uncategorized Transactions, VAT Declaration (Momsdeklaration)). - Confirm the company. Ask "Which company am I connected to?" → Claude names the company the key or consent was issued for.
- Run prompt 1 (uncategorized + suggest categories). → A list of uncategorised rows plus category suggestions; no booking happens.
- Run prompt 2 (overdue invoices). → At least one overdue customer invoice with aging.
- Run prompt 3 (VAT report + can I close). → Momsdeklaration rutor returned;
accounted_vat_close_checkreports a non-empty blocker list (uncategorised transactions, an unapproved leverantörsfaktura, and a high-value business expense without a receipt). - Stage a write. Ask Claude to categorise one transaction. → Claude stages a pending operation and tells you where it waits: the booking does not post until you approve at /pending (or in chat, on a connection with Godkänn ticked).
If every step matches, the connector is wired correctly and the approval model is enforced.
Support
Stuck connecting, or seeing an unexpected blocker? Use the in-app support form at /help: it routes straight to the product team with your company context attached. Include the client (claude.ai / Desktop / Code), the path you used (A, B, or C), and the tool name from any error message.