An MCP server for iCount — Israeli cloud
accounting/invoicing software. Lets any MCP-compatible AI agent (Claude Code, Claude Desktop, Cursor,
Windsurf, n8n, etc.) create and manage iCount documents (invoices, receipts, orders, offers...) and
clients directly from a conversation.
Runs as a local server — no hosting, no OAuth flow, just a static API token.
MCP server for the iCount (Israeli accounting/invoicing) API — documents and clients, over stdio
2026-11-16
ดาว
—
เครื่องมือ
—
อัปไทม์
—
stdio
Unofficial, community-built integration. Not affiliated with or endorsed by iCount. You are
responsible for the documents and data this creates in your own iCount account.
Keep your MCP client's tool-approval prompts on for this server. It acts on real financial
records, and icount_cancel_document / icount_delete_client are irreversible. See
SECURITY.md.
Requirements
Node.js 18+
An iCount account with an API Token (not your login user/pass — see below)
Getting your API token
Log in to your iCount account.
Go to אזור אישי → הגדרות → API (Personal area → Settings → API).
Create a new API Token.
Copy it — you'll need it below. It looks like API3E8-XXXXXXXX-XXXXXXXX-XXXXXXXXXXXXXXXX.
This is iCount API v3, which authenticates with a single static Bearer token — unlike the legacy
create_doc.php API, which used cid/user/pass. Only the token works with this server.
Install
Nothing to clone or install — npx fetches and runs it on demand. Just add it to your MCP client
config with your token:
That file is .mcp.json in your project (Claude Code), claude_desktop_config.json (Claude Desktop),
~/.cursor/mcp.json (Cursor), or the equivalent for your client. On Windows, some clients need
"command": "npx.cmd".
Claude Code
claude mcp add icount --env ICOUNT_API_TOKEN=API3E8-... -- npx -y icount-mcp
Pin a version
npx -y icount-mcp always runs the latest published version. To pin:
npm test # offline: no iCount account or network needed
The token can come from either the env block or a .env file — the env block wins when both are
set. A .env is looked for next to the package and in the working directory; with npx you'll want
the env block.
Configuration
Variable
Required
Default
What it does
ICOUNT_API_TOKEN
yes
—
Your iCount API v3 token
ICOUNT_TIMEOUT_MS
no
30000
Per-request timeout, clamped to 1s–300s
Verify it's working
Ask your agent to "test the icount connection" — it should call icount_test_connection and get back
basic account/API info.
Tools
Documents
Tool
What it does
icount_test_connection
Verify the token works
read
icount_create_document
Create an invoice, receipt, order, offer, etc.
write
icount_search_documents
Search documents by type, status, client, date range (needs ≥1 filter)
read
icount_get_document
Fetch full details of one document
read
icount_cancel_document
Cancel a document (iCount has no hard delete)
⚠️ irreversible
icount_close_document
Mark a document closed/paid
write
icount_convert_document
Convert a document to another type (e.g. offer → order)
write
icount_get_document_url
Get a printable/viewable PDF URL
read
Clients
Tool
What it does
icount_create_client
Create a client record directly (no document)
write
icount_update_client
Update an existing client's fields
write
icount_get_client
Fetch a client's details
read
icount_list_clients
List clients (bounded — returns { total, returned, clients })
read
icount_delete_client
Really delete a client — no cancel-only restriction here
⚠️ irreversible
icount_get_client_open_docs
One client's outstanding/unpaid documents (needs a client id/email/name)
read
Every tool carries MCP tool annotations
(readOnlyHint / destructiveHint / idempotentHint / openWorldHint), so a well-behaved client
knows which calls are safe to run without asking and which need your confirmation.
⚠️ Important: real tax documents need a payment breakdown
invoice, invrec, receipt, and refund are real fiscal documents. Creating them without a
payment object will fail with an opaque "יצירת המסמך נכשלה" ("document creation failed") error —
even though the client record may already have been created as a side effect before validation failed.
payment.method is one of cash, creditcard, cheque, banktransfer. For testing purposes, prefer
order or offer doctypes instead — they're non-tax documents with no payment requirement, and (like
all iCount documents) can't be hard-deleted, only cancelled.
Search quirks
iCount's doc/search has two behaviours worth knowing about, both verified against a live account:
At least one filter is required. An unfiltered search is rejected; pass a doctype, client,
docnum, or date range. This server catches that locally, without a wasted round trip.
A very broad date range can be refused with too_many_results. Narrow the range or add
filters — maxResults does not raise iCount's server-side limit.
A search that legitimately matches nothing returns { "docs": [], "matched": 0 }. iCount itself
reports that case as a failure; this server normalises it to an empty result so your agent doesn't
conclude something broke.
Development notes / how this was verified
iCount's public documentation (apiv3.icount.co.il/docs/iCount/) is a JS-rendered Postman page that
isn't easy to scrape. The endpoint map used here (/api/v3.php/<module>/<method>) was cross-checked
against the open-source n8n-nodes-icount node (MIT
licensed) and then empirically verified against a live iCount account: every tool in this server was
exercised end-to-end (including a full create → update → delete client lifecycle, and a real receipt
creation + cancellation) before being shipped.
Security
Short version: this is a local stdio server that talks only to a hardcoded https://api.icount.co.il,
never logs your token, redacts it from error messages, times out every request, and keeps stdout
reserved for JSON-RPC. It adds no confirmation step of its own — the model can call every tool, so
leave your client's approval prompts on. Full threat model in SECURITY.md.
doc/update_doc_income_type, doc/list (superseded here by the more flexible doc/search)
Expenses, suppliers, inventory, CRM, and time-tracking modules (separate iCount API areas entirely)
Contributing
PRs welcome — see CONTRIBUTING.md for setup, how to verify a change against a
live account without wrecking it, and what CI enforces. main is protected: fork, branch, and open
a PR. Please also read the Code of Conduct.