Extract invoices from Claude with the Temlavo MCP server
Connect Temlavo to Claude or another MCP client and ask in plain language: extract this invoice, does it need review, how many pages are left.
On this page
Temlavo now has a remote MCP server. Add it to Claude, or any client that supports MCP, and ask about invoices in plain language. It uses your existing Temlavo account, plan and usage, and the same checks as the API.
What you can ask
- “Extract this invoice and tell me if it needs review.” Your assistant submits the invoice from a link and reads the result when it’s ready.
- “Why does it need review?” It reads the checks that failed, such as a total that doesn’t match its subtotal and tax.
- “Show me the line items.” Long results arrive page by page.
- “How many pages have I used this month?”
Behind those questions are three tools: submit_invoice, get_invoice_result and get_usage.
Connect it
In claude.ai, open Settings → Connectors, add a custom connector with the server URL from the MCP page, and sign in with your Temlavo account. Clients that can send a header, such as Claude Code, connect to the same URL with an API key instead. The exact steps are on the MCP docs page.
Try it with a sample invoice
Once connected, ask:
Extract https://temlavo.com/fixtures/v1/bad-total-us.pdf and tell me if it needs review.It’s a synthetic invoice whose printed total doesn’t match its subtotal and tax, so the result should come back as needs_review with the total check failing. It uses one page of your allowance.
Good to know
- Invoices come from links: a direct HTTPS link to the file. For uploads, redirects or email attachments, use the API, SDK or n8n.
- Processing happens in the background, so the assistant reads the result once it’s completed, needs review or failed.
- Retrying is safe: the same submission returns the existing document instead of processing the invoice again.
completedmeans no blocking check failed. It doesn’t mean the invoice was verified or approved for payment.
When to use it
MCP suits looking at invoices by hand: checking one before you approve it, asking why an invoice needs review, or seeing how many pages you have left. For automated pipelines, use the API and SDK or the n8n template where your code decides what happens with each outcome.
Try the API in the playground
Compare sample invoices with their extracted fields, checks and full API responses. No account needed.
More from the blog
How to validate extracted invoice totals: rounding, tolerances and tax
The rules I use to check that extracted invoice amounts add up: lines, subtotal, tax rounding, total tax, total and amount due, with code to copy.
36 held-out real invoices: what we measured, and what we didn't
We measured Temlavo on 36 held-out 2020 US TV-station invoices from FCC filings: the method, the numbers with their uncertainty, and what they do not show.
Why I built Temlavo
Temlavo extracts invoice data and tells your code which invoices not to trust. Here is why I built it that way, and what it deliberately does not do.