Searches documents
By period, supplier, type and amount range, page by page.
Connector for Claude and ChatGPT
Connect InvoiceHub once and ask in plain language: how much a supplier invoiced, which client still owes you, which contract is expiring, which documents are duplicates, what was deleted. The assistant sees only your company's documents and cannot change anything.
Server URLhttps://web.invoicehub.work/mcp
By period, supplier, type and amount range, page by page.
Every extracted field: number, dates, amounts and VAT, issuer, recipient, IBAN and the description of services.
Likely duplicate documents, and suppliers stored under different names.
Which documents were deleted as duplicates, and what changed on the issuers.
Which locations have uploaded their monthly cash register report and which are still missing.
Issued and uploaded invoices, notes, proformas and offers, what each client still owes and which payment is overdue.
Contracts, annexes and powers of attorney: search that also covers their text, end and notice dates, and what is missing. Confidential documents stay hidden.
Read-only through MCP. The connector cannot upload, issue, change or delete documents. A separate REST API with explicit permissions lets another system issue invoices.
API guide: issue an invoice, generate a PDF and queue email delivery
All clients use the same address. In Administration → API keys, an administrator creates a named key for the connector with legacy:access. The key is shown only once — save it in a password manager. REST API invoice-issuing permissions do not grant MCP access.
https://web.invoicehub.work/mcp. Leave the OAuth Client ID and Secret fields empty.https://web.invoicehub.work/mcp and OAuth authentication.Send the key as a bearer token:
claude mcp add --transport http invoicehub https://web.invoicehub.work/mcp \
--header "Authorization: Bearer $INVOICEHUB_API_KEY"
Cursor, VS Code and the MCP SDKs take the same configuration:
{
"mcpServers": {
"invoicehub": {
"type": "http",
"url": "https://web.invoicehub.work/mcp",
"headers": { "Authorization": "Bearer sk-…" }
}
}
}
Menu names in Claude and ChatGPT change, and connector availability depends on your plan and workspace policies.
legacy:access, the company's OAuth tokens are also invalidated. Other active API keys remain valid. Creating an additional key does not stop existing connections.MCP access covers the whole company. Personal invoice and sales visibility restrictions in the browser do not apply to legacy:access. Confidential company documents remain hidden. Grant this permission only to people with full access to the company's accounting records.
In practice
The assistant picks the tool and the filters on its own, then summarizes, compares and calculates on what it finds.
What is the total of our BILLA invoices for May?
I called search_invoices for BILLA and 1–31 May. I found 6 invoices totaling €64.82 including VAT. The largest is dated 26 May for €15.49. These are invoice amounts, not confirmed payments.
| Tool | Parameters | Result |
|---|---|---|
search_invoices |
date_from, date_to (ISO date), type, issuer, amount_min, amount_max, page (default 1), per_page (default 20, maximum 100) |
Document list and pagination with page, per_page, total, total_pages |
get_invoice |
invoice_id |
One company document, or a message that it was not found |
duplicate_invoices |
no parameters | Groups of likely duplicates with each document's rows and the one recommended to keep (keep_id) — the suggestions from the “Duplicate documents” page |
issuer_names |
no parameters | The counterparty directory — suppliers and clients — with each one's role (supplier, client or both), its spellings and document count (purchases and sales), and the supplier groups recorded under different names that are offered for merging — from the “Suppliers” page |
invoice_audit_log |
limit (default 50, maximum 200) |
The history of deleted duplicates: the kept document, the deleted documents as they were saved, and the objects removed from storage — the “History” table on the “Duplicate documents” page |
issuer_audit_log |
limit (default 50, maximum 200) |
The history of merges, renames, removals and restores: the standard, the changed documents with before and after values, the added and removed rules, and whether the record can still be restored — the “History” table on the “Issuers — standard names” page |
cash_register_reports |
month (YYYY-MM, default: the month that has just ended) |
Each location with an uploaded or missing report. Each report has total_amount (the VAT-inclusive total of the device report), vat_amount (the VAT inside it at the standard rate, or “0.00” when the company is not fully registered for VAT) and currency (EUR), its files (name, type, size), when and by whom it was uploaded, and the Google Drive delivery – the month from the “Cash register reports” page. Amounts are null for reports uploaded before they were recorded. The images themselves are not returned. |
search_sales_documents |
date_from, date_to (ISO issue date), kind, status (draft, issued or cancelled), client (name, UIC or VAT number), number, page (default 1), per_page (default 20, maximum 100) |
The sales documents — invoices, notes, proformas, offers, protocols and receipts, issued in the app or uploaded — with each one's open amount, totals of the issued invoices and notes (credit notes subtract) and pagination — the list from the “Sales” page |
get_sales_document |
document_id |
One sales document with its lines, the client's address, its remarks, the linked documents, the notes against it and the open amount, or a message that it was not found |
sales_report |
report (documents, offers or receipts, default documents), date_from, date_to (default: 1 January to today), client, unpaid_only (documents only), page, per_page (default 20, maximum 100) |
The report from the “Sales reports” page: the period's issued and cancelled documents with their amounts (credit notes negative) and what is unpaid, totals for the whole period and owed — how much is owed today, how much is overdue and the five clients who owe the most |
search_company_documents |
query (up to 200 characters, also searches the text), doc_type, status (active by default, expired, terminated, archived or all), page (default 1), per_page (default 20, maximum 50) |
The company documents with their type, title, counterparty, dates, renewal, notice period, value, versions and reminders, the text excerpts that match the search, and pagination — from the “Company documents” page. Confidential documents are not shown. |
get_company_document |
document_id |
One company document with its versions and reminders, without its access rights, or a message that it was not found |
get_company_document_text |
document_id, version (default: the latest), page_from (default 1), page_limit (default 10, maximum 20) |
The text of a run of pages of the version and next_page_from for the next run. Each read is recorded in the document's history. |
company_document_checks |
no parameters | The checks from the “Company documents” page and the home page: end and notice dates within 30 days, a missing signed copy or counterparty, an annex without a contract, invoices above the contract value and counterparties without a required contract — with key, due and document_id |
Each received document is returned with its number, type, issuer (name, UIC, VAT number), recipient, amount excluding and including tax, currency, original currency and amounts, issue date, payment method, description of services, IBAN and the date it entered the system.
Each sales document is returned with its kind, status, origin (issued in the app or uploaded), ten-digit number, dates, client (name, UIC, VAT number), amounts excluding VAT, VAT and total in euro, original currency and amounts, payment method and open amount. The PDF file and the uploaded image are not returned.
No. MCP tools only read. Reading a company document's text is recorded in its history. Another system can issue invoices through the separate REST API with a key carrying the required permissions, not through this connector.
All documents of the company whose key you used — and none from any other company, even if asked. The company comes from the token, not from the conversation. Company documents marked confidential are not shown to the assistant.
Each key and each connection serves one company. To connect another company, use that company's API key.
Only the results of the tools it calls during the conversation, which the assistant's provider processes under its own terms. InvoiceHub does not receive the conversation — it sees only the tool requests.
Remove the connector in your assistant's settings. In Administration → API keys, revoke or rotate the key used. Revoking, rotating or removing legacy:access invalidates the company's OAuth tokens but does not stop other active bearer keys.
Clients discover the server through /.well-known/oauth-protected-resource and /.well-known/oauth-authorization-server, register themselves at /register, get a code at /authorize and a token at /token. PKCE S256 is required; authorization codes are stored as hashes, are valid for five minutes and can be used only once. A token is revoked at /oauth2/revoke.
Sign in, generate a key under “Administration” and ask your first question.
Sign in