Name: iDoklad
Author: honzsik

iDoklad MCP

Unofficial iDoklad invoicing: read and create invoices, proformas, credit notes and contacts.

Grade A Local · stdio API key 20 tools v0.4.0 · 9 Nov 2026 MIT

No reviews yet by honzsiknpm 422 Runs on your machine, nothing hosted

96/100

trust score

422

downloads a day

local

runs on your machine

tools declared

What it does

Unofficial iDoklad invoicing: read and create invoices, proformas, credit notes and contacts.

Quickstart

# 1 — add it to Claude Code
claude mcp add --scope user --env 'IDOKLAD_CLIENT_ID=${IDOKLAD_CLIENT_ID}' --env 'IDOKLAD_CLIENT_SECRET=${IDOKLAD_CLIENT_SECRET}' --env 'IDOKLAD_APPLICATION_ID=${IDOKLAD_APPLICATION_ID}' --transport stdio idoklad-mcp '--' npx -y idoklad-mcp

# 2 — ask your agent for something these tools do
#   get_codebook, search_api_docs, idoklad_api_request and 17 more

It needs IDOKLAD_CLIENT_ID, IDOKLAD_CLIENT_SECRET, IDOKLAD_APPLICATION_ID: this reads them from your environment, so export them first.

iDoklad costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.

Publishernot claimed

honzsik1 server

1 category

All 1 server

Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.

Installation

Where are you running it?

Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts iDoklad as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.

Claude Codedeclared by this listing

This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. Claude Code reads IDOKLAD_CLIENT_ID (Client ID from iDoklad → Settings → API), IDOKLAD_CLIENT_SECRET (Client Secret from iDoklad → Settings → API), IDOKLAD_APPLICATION_ID (Client Id of a ClientCredentials app on developer.idoklad.cz) from your environment each time it starts the server, so the value stays out of its config: export them in your shell profile (macOS, Linux), or run setx IDOKLAD_CLIENT_ID …, setx IDOKLAD_CLIENT_SECRET …, setx IDOKLAD_APPLICATION_ID … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.

claude mcp add --scope user --env 'IDOKLAD_CLIENT_ID=${IDOKLAD_CLIENT_ID}' --env 'IDOKLAD_CLIENT_SECRET=${IDOKLAD_CLIENT_SECRET}' --env 'IDOKLAD_APPLICATION_ID=${IDOKLAD_APPLICATION_ID}' --transport stdio idoklad-mcp '--' npx -y idoklad-mcp

Reconnect, or start a new session, and the tools appear in the model’s tool list.

Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.

What it asks of you

It reaches a system of yours, so it needs your own credential rather than the publisher’s: IDOKLAD_CLIENT_ID — Client ID from iDoklad → Settings → API; IDOKLAD_CLIENT_SECRET — Client Secret from iDoklad → Settings → API; IDOKLAD_APPLICATION_ID — Client Id of a ClientCredentials app on developer.idoklad.cz. You set them in your own client’s config, on your machine — this marketplace never holds it.

What it writes

One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.

What you approve

20 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.

Tool surface

What the model actually sees. Descriptions are diffed on every release — see version history.

Only tools that write or reach the network

Read from its source code. A server that builds its tool list when it starts can list more tools than this.

Get an iDoklad codebook (číselník) or company setting list: currencies, countries, VAT rates (current only), VAT codes,

Parameter	Type	Required	Notes
codebook	string	yes	—

Search the iDoklad API v3 reference for endpoints not covered by other tools (bank statements, cash vouchers,

Parameter	Type	Required	Notes
query	string	yes	Keywords in English, e.g. 'bank statement list' or 'recurring invoice'.
limit	integer	no	—

Call any iDoklad API v3 endpoint directly (find it with search_api_docs first). Path is relative, e.g. 'BankStatements'.

Parameter	Type	Required	Notes
method	string	yes	—
path	string	yes	Endpoint path after /v3/, e.g. 'IssuedInvoices/123'.
query	object	no	—
body		no	JSON body for POST, PUT, PATCH.

Search contacts (kontakty: customers and suppliers) by company name, IČO, DIČ or email. Without filters, lists all contacts.

Parameter	Type	Required	Notes
name	string	no	Part of the company name.
ico	string	no	Company ID (IČO).
dic	string	no	VAT ID (DIČ).
email	string	no	Part of the email address.
page	integer	no	—
pageSize	integer	no	—

Get full detail of one contact by ID: address, IČO, DIČ, bank account, default due days.

Parameter	Type	Required	Notes
id	integer	yes	—

Search the price list (ceník) by item name or code. Use the prices when creating invoices.

Parameter	Type	Required	Notes
name	string	no	Part of the item name.
code	string	no	Part of the item code.
page	integer	no	—
pageSize	integer	no	—

Create a new contact (customer or supplier). Confirm the details with the user before creating.

Parameter	Type	Required	Notes
companyName	string	yes	—
ico	string	no	Company ID (IČO).
dic	string	no	VAT ID (DIČ), e.g. CZ12345678.
street	string	no	—
city	string	no	—
postalCode	string	no	—
country	string	no	Two-letter ISO country code. Default: the company's own country.
email	string	no	—
phone	string	no	—
firstname	string	no	—
surname	string	no	—
defaultDueDays	integer	no	Default invoice due period for this contact.
note	string	no	—

Download the PDF of an invoice, proforma, credit note or received invoice and save it to a local folder. Returns the file path.

Parameter	Type	Required	Notes
documentType	string	yes	—
id	integer	yes	Document ID.
language	string	no	PDF language. Default: the document's own language.
withPayments	boolean	no	Include the payment summary (not for received invoices).

Email an issued invoice, proforma or credit note through iDoklad, using the email template from iDoklad settings.

Parameter	Type	Required	Notes
documentType	string	yes	—
id	integer	yes	Document ID.
sendToPartner	boolean	no	Send to the email on the customer's contact.
otherRecipients	array	no	Extra recipients.
sendToSelf	boolean	no	Send a copy to your company email.
sendToAccountant	boolean	no	Send to the accountant set in iDoklad settings.
subject	string	no	Custom subject. Default: iDoklad template.
body	string	no	Custom body. Default: iDoklad template.
language	string	no	—

Record full payment of an issued invoice, proforma or received invoice (uhrazeno) on a given date.

Parameter	Type	Required	Notes
documentType	string	yes	—
id	integer	yes	Document ID.
dateOfPayment	string	no	Default: today.

Remove all payments from an issued invoice, proforma or received invoice, so it is unpaid again.

Parameter	Type	Required	Notes
documentType	string	yes	—
id	integer	yes	Document ID.

Create a credit note (opravný daňový doklad / dobropis) for an issued invoice. Without items it credits the whole invoice;

Parameter	Type	Required	Notes
invoiceId	integer	yes	ID of the issued invoice to credit.
reason	string	yes	Reason for the credit note (důvod opravy), shown on the document.
items	array	no	Items to credit. Default: all items of the invoice.
offset	boolean	no	Settle the credit note against the invoice (započtení).
dateOfIssue	string	no	Default: today.
description	string	no	—
note	string	no	—

Create the final issued invoice (vyúčtování zálohy) from a fully paid proforma invoice.

Parameter	Type	Required	Notes
proformaId	integer	yes	ID of the paid proforma invoice.

No parameter schema on file.

Free

$0 forever

Every tool, no call limit
No card, and mcprush charges nothing for it
Source published under MIT
Runs on your machine — nothing of it reaches our gateway
Nothing to cap, because mcprush bills nothing

Nothing here is billable: mcprush charges nothing to install iDoklad or to call it, at any volume.

ATrust score 96 / 100

Release 0.4.0 · scanned 9 Nov 2026

Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.

Threat score100

Client score96

Findings0 threat · 1 capability

Capabilitymoderate

Coveragesource

Verificationrepo

Surface digestd1dfd68081404818328b443fea86d246f31db6badfc3b203602a4c5c243470b7

Score vectorthreat 100 → client 96

Term	Level	What it prices	Points
capability-exposure	moderate	capability blast radius (moderate) — client exposure if the model is manipulated	−3
verification-discount	repo	publisher verification (public source) — no provenance, but the source is public and inspectable	−1
coverage-honesty	source	inspection depth (source) — how much of the target the scan could see	−0

score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.

What the scan could actually read

A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.

Tool surfaceread

Implementation sourceread

Package metadataread

Live transportnot available

Tools were statically extracted from the published source (20 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".

1 of the 20 recovered tools are registered only when ctx.readOnly is false (dist/tools/contacts.js:86) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes only the other 10.

5 of the 20 recovered tools are registered only when ctx.readOnly is false (dist/tools/documents.js:94) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes only the other 10.

4 of the 20 recovered tools are registered only when ctx.readOnly is false (dist/tools/invoices.js:27) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes only the other 10.

Capability — what it could do if the model were manipulated

Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.

10 tools are registered unconditionally · (1) 1 more only when ctx.readOnly is false (dist/tools/contacts.js:86) · (2) 5 more only when ctx.readOnly is false (dist/tools/documents.js:94) · (3) 4 more only when ctx.readOnly is false (dist/tools/invoices.js:27) — typically when a key or option is configured. All 20 are in the table below and were analysed; the conditional ones are marked.

Tool	Capability tags	Why the tag was assigned
get_codebook	no tags
search_api_docs	no tags
idoklad_api_request	no tags
list_contacts	no tags
get_contact	no tags
list_price_list_items	no tags
create_contact conditional (1)	no tags
get_document_pdf	untrusted-inputexternal-sink	untrusted-input: keyword "download"; external-sink: declares readOnlyHint: false, openWorldHint: true
send_document_email conditional (2)	state-write	state-write: declares destructiveHint: true
send_payment_reminder conditional (2)	state-write	state-write: declares destructiveHint: true
send_payment_confirmation conditional (2)	state-write	state-write: declares destructiveHint: true
mark_document_paid conditional (2)	no tags
mark_document_unpaid conditional (2)	state-write	state-write: declares destructiveHint: true
create_credit_note conditional (3)	no tags
create_invoice_from_proforma conditional (3)	no tags
create_issued_invoice conditional (3)	external-sink	external-sink: keyword "create_issue", handler sends an HTTP POST ( client.post(doc.path) at dist/tools/invoices.js:88
create_proforma_invoice conditional (3)	external-sink	external-sink: handler sends an HTTP POST ( client.post(doc.path) at dist/tools/invoices.js:88
get_business_stats	no tags
get_top_partners	no tags
get_contact_stats	no tags

Toxic-flow graph

The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.

flow-1

Untrusted input can drive an external action even though no sensitive source is exposed.

Supply chain and provenance

Integrityfirst-seen

Surface digestd1dfd68081404818

Scanned2026-11-09

This is the first scan of this surface here, so there is nothing yet to compare it against.

Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.