Invoice4U MCP
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.
Invoice4U MCP by Agente
An unofficial, third-party Model Context Protocol server that gives any MCP-compatible agent safe, typed access to an Invoice4U account — searching documents and customers, and creating receipts linked to paid invoices.
Unofficial: this is a community integration, not affiliated with, endorsed by, or supported by Invoice4U. Invoice4U names are used nominatively to describe what the server connects to. No Invoice4U trademarks or logos are used without permission.
TypeScript / Node.js 24 LTS / MIT · stdio transport · local self-hosted — Agente never custodies your Invoice4U credentials.
Read-only by default: the single write tool (receipt creation) is not registered in
tools/listunlessINVOICE4U_ALLOW_WRITES=true.English README · Hebrew README.he.md
Quick start
{
"mcpServers": {
"invoice4u": {
"command": "npx",
"args": ["-y", "@agente-dev/invoice4u-mcp"],
"env": {
"INVOICE4U_API_TOKEN": "your-api-key",
"INVOICE4U_ENV": "qa",
"INVOICE4U_ALLOW_WRITES": "false"
}
}
}
}INVOICE4U_ENV must be explicitly qa or production — it never silently defaults to production. Start against QA; it is the safe documented starting configuration.
Related MCP server: invoice4u-mcp
Tools (v0.1 surface)
Tool | Mode | Purpose |
| read | Validate token, environment, organization access |
| read | Search documents: open/closed, dates, customer, type |
| read | Fetch by document ID, document number, or API identifier |
| read | Search/list customers |
| read | Complete customer details |
| read | Organization branches |
| read | Preflight a proposed receipt: documents, balances, allocations, totals — no writes |
| write | Create a receipt linked to one or more existing invoices (idempotent via mandatory |
Read tools declare readOnlyHint: true, idempotentHint: true. The write tool declares readOnlyHint: false, destructiveHint: false, idempotentHint: true — idempotency holds only because a stable apiIdentifier is mandatory and duplicate or uncertain outcomes resolve through identifier lookup. A timeout after submitting a write is never blindly retried: the server first queries by apiIdentifier and retries only when the lookup proves no document exists.
Money is expressed as decimal strings at the MCP boundary ("12500.00"), never JavaScript floats. Invoice4U responses that return HTTP 200 while carrying application errors in the Errors collection are normalized into a typed error model — never reported as success.
Configuration
Credentials live only in environment variables — the token is never accepted as a tool argument, never returned, never logged.
Variable | Values | Default |
| API key | required |
|
| required — no silent production default |
|
|
|
|
|
|
See .env.example. Only reviewed official Invoice4U hosts are contacted — there is no arbitrary base-URL escape hatch.
Safety model
Read-only by default — the write tool is omitted from
tools/listentirely unless writes are explicitly enabled.Idempotent writes — mandatory stable
apiIdentifier; resubmitting the same request cannot create a second receipt.Verified writes — every write re-fetches the receipt and referenced invoices, returning previous/new balances and statuses as structured output.
No blind retries on uncertain write outcomes; resolution goes through
apiIdentifierlookup.Secret hygiene — no tokens or customer PII in logs at normal levels; QA fixtures contain no real customer data.
No money movement — creating a receipt records money already received; the server cannot initiate payments or charge cards.
Status
Implemented — v0.1 surface. Eight tools (7 read + 1 gated write) are implemented and registered as described in the Tools table above. Coverage is tracked in coverage-manifest.json, with details in docs/.
QA status: read tools are verified against the Invoice4U API reference plus contract tests (120 unit + contract tests green). Live QA integration is BLOCKED pending credentials — there is no public Invoice4U sandbox, and exercising
apiqa.invoice4u.co.ilrequires a real QA org account + API token. The gated smoke test (tests/integration/qa.spec.ts) is skipped without a token; seedocs/qa-testing.md.npm package pending: publication awaits the trusted-publishing link for
@agente-dev/invoice4u-mcpon npmjs.com.
License
MIT — see LICENSE. © Agente Dev LTD. Not affiliated with Invoice4U.
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
Free hosted MCP for invoices, estimates, clients, items and PDFs. OAuth authorization required.
Managed MCP gateway with OAuth, per-agent permissions, shared accounts and activity logs.
wFirma.pl (Polish accounting) via MCP: invoices, contractors, payments, reports. Full read-write.
Secure remote MCP for supported accounting workflows in authorized Money S3 companies.
Related MCP Servers
AlicenseAqualityDmaintenanceEnables MCP-capable agents to read Fintaro invoices and transactions, and upload receipts, via a scoped API key with PII-safe projections.6Apache 2.0- AlicenseNot gradedqualityCmaintenanceEnables read-only querying of Invoice4U accounting data, including documents, customers, branches, tax rates, and Israeli invoice allocation statuses.MIT
- AlicenseBqualityCmaintenanceEnables MCP clients to read Fortnox invoices and customers, validate receipts, and optionally perform approved write operations with strict safety controls.3MIT
- AlicenseBqualityCmaintenanceEnables MCP clients to query and register invoices, suppliers, and payments through the Contasimple API v2, including optional write access for creating records, attaching files, and managing payments.1630 npmMIT