ZATCA e-invoices

Live

Create and validate Saudi VAT invoices from a conversation.

Build a VAT-correct invoice (seller, buyer, line items, 15% standard rate) and validate totals and required fields. Returns UBL-style XML and a Phase-1 TLV QR. Phase 2 clearance (CSID, signing, reporting) is not included.

Start free Tool reference

Server URL

streamable http

https://toolcargo.com/mcp/zatca

Claude Code

terminal

claude mcp add --transport http --scope user toolcargo-zatca https://toolcargo.com/mcp/zatca \
  --header "Authorization: Bearer YOUR_API_KEY"

Create a key in your dashboard. Other clients: setup guides.

What it helps you do

VAT totals computed consistently
Required-field validation
UBL-style XML and Phase-1 QR

Built for: Small Saudi businesses and freelancers who invoice from their assistant.

Example requests

Draft an invoice

“Create a ZATCA invoice 2026-104 dated 2026-09-28: seller Halawa Studio VAT 300000000000003 in Riyadh, buyer Acme, one line Design work × 1 at 1000 SAR.”

Validated totals (subtotal 1000, VAT 150, total 1150) plus XML and a TLV QR.

Check totals

“Validate this invoice JSON before I send it.”

A list of field problems, or computed SAR totals if it is consistent.

Step-by-step workflows: pre-launch check · fixing link previews

Tools

Tool	What it does	Access
`validate_invoice` Validate a Saudi VAT invoice	Check seller VAT number, required fields, line quantities and that VAT is 0% or 15%. Returns issues and computed totals. Does not submit to ZATCA.	Read-only
`create_invoice` Create a Saudi VAT invoice	Same checks as validate_invoice, then return UBL-style XML and a Phase-1 TLV QR payload. Does not clear or sign with ZATCA.	Writes a document (not a third-party API)

Requirements

• A ToolCargo account with Site Audit activated (free).
• Seller 15-digit VAT number (starts and ends with 3).

Limitations

• Does not submit invoices to ZATCA Phase 2 clearance or sign with a CSID.
• The QR is a Phase-1 TLV payload, not a clearance stamp.
• VAT rate is 0 or 15% only.

Supported clients

“Tested” means we connected that client to this endpoint and ran a tool call ourselves. “Documented” means the client supports this setup per its own docs, but we have not tested it yet.

Claude Code	API key header	Tested	Remote HTTP server with an Authorization header. Tested 2026-09-11 (v2.1.268).
Claude (claude.ai)	OAuth sign-in	Tested	Custom connector with OAuth sign-in; tested on claude.ai web 2026-09-11. Desktop and mobile use the same account connectors but were not tested separately.
Cursor	API key header	Documented, not yet tested	mcp.json with url and headers.
VS Code (Copilot agent mode)	API key header	Documented, not yet tested	.vscode/mcp.json with type http and headers.
ChatGPT (developer mode)	OAuth sign-in	Documented, not yet tested	Requires OAuth; API keys cannot be entered.
MCP Inspector	API key header	Tested	CLI mode, tested 2026-09-11. Useful for calling tools directly.

Pricing

Free

For trying the connector on your own sites.

50 calls/month · 25 links per check

Pro

$12/mo

For freelancers and agencies auditing client sites every week.

2,000 calls/month · 100 links per check

Proposed test price. See the pricing page for checkout status.

Full pricing and billing details