Parzo ships a native MCP (Model Context Protocol) server. Once installed, your AI agent can extract invoice data without writing a single line of integration code — just point it at a PDF and ask.Documentation Index
Fetch the complete documentation index at: https://docs.parzo.dev/llms.txt
Use this file to discover all available pages before exploring further.
Installation
Install the MCP server globally via npm:Configuration
Claude Code
Add Parzo to your Claude Code MCP config file:inv_your_key_here with your Parzo API key. Get one free →
Cursor
Add the following to your Cursor MCP settings:Available tools
extract_invoice
Extracts structured data from an invoice PDF file.
| Parameter | Type | Description |
|---|---|---|
file_path | string | Absolute path to the PDF file on your local machine |
api_key | string | Your Parzo API key (optional if set via env) |
extract_invoice, poll for the result, and return the full JSON — vendor, buyer, line items, financials, and validation flags.
get_job
Retrieves the status and result of an existing extraction job.
| Parameter | Type | Description |
|---|---|---|
job_id | string | The job ID returned by a previous extraction |
api_key | string | Your Parzo API key (optional if set via env) |
Example workflow
Once Parzo is connected, you can use natural language to process invoices:extract_invoice for each file and synthesize the results.
Verify the connection
After adding the config, restart your client and run:extract_invoice and get_job listed.
Troubleshooting
“Missing X-API-Key header” — Make sure your API key is set correctly in theenv block of your config file.
“File not found” — Use the absolute path to the PDF. On Windows with WSL, use /mnt/c/Users/... format.
Server not showing up — Restart your MCP client after editing the config file.
The MCP server is open source and published on npm as
parzo-mcp.
Found a bug? Open an issue on GitHub.