MCP

Use Temlavo from Claude.

Add Temlavo as an MCP connector and your assistant can extract an invoice from a link, tell you what needs review, and check your page usage. You need an existing Temlavo account; no code is required.

On this page

Connect Claude

Add to Claude

Listed in Claude's connector directory as Temlavo. Open the listing, select Connect, then sign in with your Temlavo account and approve access. You can disconnect it at any time; that does not delete your invoices or change your plan.

To add it as a custom connector instead, open Settings → Connectors in claude.ai, choose Add custom connector and paste the server URL below. Choose Use your own OAuth client, enter the client ID naCwU7C1qiVwdkmQ and leave the secret empty.

Server URL
https://api.temlavo.com/mcp

Other MCP clients

ChatGPT and other clients that sign in to MCP servers on their own need only the server URL above: add it in the client's connector settings, sign in with your Temlavo account and approve access. An app you approve can submit and read your invoices and see your page usage, and it receives your account's email address and name.

Clients that can send a custom header, such as Claude Code or your own server-side code, connect to the same server URL with an existing Temlavo API key as an Authorization: Bearer header. Keep the key in an environment variable or secret store, and never paste it into a chat.

What you can ask

Ask in plain language, such as “Extract this invoice and tell me if it needs review” or “How many pages have I used this month?”. Your assistant picks the matching tool:

  • submit_invoice sends one invoice from a direct HTTPS link and returns a document ID. It uses your page allowance.
  • get_invoice_result reads a document's result: a summary by default, or the full result, its fields, line items or checks.
  • get_usage reads used and remaining pages for the current billing period or an earlier one.

The tool calls behind those questions look like this:

Code example
get_usage {}
get_usage {"periods_ago":1}
get_invoice_result {"document_id":"doc_0123456789abcdef0123456789abcdef"}
get_invoice_result {"document_id":"doc_0123456789abcdef0123456789abcdef","view":"fields"}
get_invoice_result {"document_id":"doc_0123456789abcdef0123456789abcdef","view":"line_items","offset":0,"limit":25}
get_invoice_result {"document_id":"doc_0123456789abcdef0123456789abcdef","view":"checks","offset":0,"limit":25}

A submission names the file and a key the client keeps for retries:

Code example
{
  "file": {
    "download_url": "https://files.example/invoice.pdf?signature=REDACTED",
    "file_id": "stable-client-file-reference"
  },
  "idempotency_key": "generate-once-and-retain-for-retries"
}

Good to know

  • Results take a moment. A submission is processed in the background; the assistant reads the result once it is completed, needs review or failed. Completed means no blocking finding, not verified accuracy or payment approval.
  • Retries are safe. Retrying with the same key returns the existing document instead of processing the invoice again.
  • Files come from links. The link must be a direct HTTPS file URL of up to 8,192 characters. Redirects, private addresses and file attachments are not supported; use the REST upload flow for those.
  • Large results come in pages. Read the fields first, then line items and checks page by page (25 per page by default, up to 100). Responses are capped at 64 KiB of result data and 256 KiB in total.
  • Same account, same rules. MCP shares your plan, usage and retention rules with the API, SDK and n8n. OAuth sign-ins for MCP do not work with the REST API.
  • Protocol. Streamable HTTP with MCP 2026-07-28, plus compatibility for 2025-11-25 and 2025-06-18.