MCP connector

Your Fawtar account, inside your assistant

An official MCP server that connects your Fawtar account to an AI assistant. It reads your invoices, customers, receivables and VAT position, and issues an invoice when you ask. Sign in once through a consent screen — you choose the organization and whether it may write — and end the connection whenever you like.

What you can ask it

Each question maps to one tool. The assistant picks the tool; you read the answer against your real books.

“Who owes me money, and how overdue is it?”

Every unpaid issued invoice with its remaining balance and days overdue, plus totals.

fawtar_outstanding

“What is my VAT position for last quarter?”

Output VAT on sales, recoverable input VAT on expenses, and the net — the figures a VAT return is built from.

fawtar_vat_summary

“Issue a simplified invoice for SAR 3,000 of design work”

A sequential number, computed VAT, a ZATCA-compliant QR code, and a ledger posting.

fawtar_create_invoice

“Show me this customer’s invoices this year”

Reads any resource in the account — customers, products, expenses, journals, payroll — with filtering, sorting and paging.

fawtar_list

Connecting

Two ways in. The first is for assistants that add a connector from a URL; the second for clients configured from a file.

1. Sign in through the assistant (OAuth)

Give the assistant this address as a custom MCP connector and nothing else. It discovers the rest on its own, sends you to a Fawtar consent screen where you sign in, choose which organization it may reach and whether it may write, and receives its own token. No key is copied and no password is shared.

https://fawtar.app/api/mcp

Whether an assistant offers a field for a connector URL is its own decision, not ours. Where one exists, this is all it needs.

2. Paste an API key (config file)

Create a key under Integrations in your account — read access unless you want invoices issued — and paste this into your client’s MCP configuration.

{
  "mcpServers": {
    "fawtar": {
      "type": "http",
      "url": "https://fawtar.app/api/mcp",
      "headers": { "Authorization": "Bearer fwt_live_xxxxxxxx" }
    }
  }
}

The endpoint is https://fawtar.app/api/mcp over Streamable HTTP, protocol version 2025-06-18. Both paths need the Business plan, the same rule the REST API follows.

The tools

Deliberately few. One tool per resource would be about fifty near-identical names, and a model choosing between fifty picks wrong — so the resource is a parameter instead.

fawtar_list
List recordsread only
fawtar_get
Fetch one recordread only
fawtar_create
Create a recordwrite
fawtar_create_invoice
Issue an invoicewrite
fawtar_outstanding
What is owed to this businessread only
fawtar_vat_summary
VAT for a periodread only

What the assistant can and cannot do

The key decides the organization

Nothing in the protocol can name another organization. The assistant sees the data of the organization the key was created in, and nothing else.

A read key cannot write

Write tools reject a read-only key. If you want an assistant that reads and issues nothing, create a read key and that is the whole configuration.

Issuing an invoice is irreversible

An issued invoice is never edited or deleted; it is corrected with a credit note. The tool itself instructs the assistant to confirm the amounts with you first.

It never sees your password

You sign in on Fawtar's own page. The assistant only ever holds a separate token, revoked on its own without touching your login.

Questions

What do I need to connect?

A Fawtar account on the Business plan and a client that speaks MCP over Streamable HTTP. If the client accepts a custom connector URL, the address is all you need; if it is configured from a file, create an API key under Integrations.

Is the server officially listed?

Yes — published in the official Model Context Protocol registry as app.fawtar/fawtar, with domain ownership verified against fawtar.app.

Can the assistant delete my data?

No. The exposed tools read, create simple records, and issue an invoice. There is no delete tool, and none that edits an issued invoice.

Does this replace the REST API?

No. The REST API is for what you build; MCP is for what an assistant does on your behalf. Both use the same key and the same scopes.

Last verified: 2026-08-29.