A Model Context Protocol server for ParserBee. It lets an AI assistant extract structured data from invoices, receipts, purchase orders, bank statements and other documents, using your Parser Templates.
Ask your assistant things like:
"Extract the invoice in ~/Downloads/inv-2041.pdf with my Invoice template."
"Read every receipt in this folder and give me a table of merchant, date and total."
"How many ParserBee page credits do I have left?"
Tool | What it does |
| Extract data from a local file ( |
| List the Parser Templates in your account, with their fields |
| One Parser Template with all of its fields |
| Page credit balance, plan and subscription status |
| The last 10 extraction requests |
| One extraction request, with its extracted data |
Related MCP server: document-to-json-mcp
Create a free account at app.parserbee.com. New accounts get 25 free pages, no credit card.
Create a Parser Template: upload one sample document and the AI builds the fields for you, or pick a ready-made one from the template library.
Copy your API key from Settings in the dashboard. It starts with pk_.
You need Node.js 18 or later.
Open Settings > Developer > Edit Config and add:
{
"mcpServers": {
"parserbee": {
"command": "npx",
"args": ["-y", "parserbee-mcp"],
"env": { "PARSERBEE_API_KEY": "pk_your_api_key" }
}
}
}Restart Claude Desktop.
claude mcp add parserbee --scope user -e PARSERBEE_API_KEY=pk_your_api_key -- npx -y parserbee-mcp--scope user makes ParserBee available in every folder. Without it, Claude Code adds the server only to the folder you run the command in. Start a new Claude Code session afterwards, then check it with claude mcp list.
Add the same mcpServers block to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project).
Add to .vscode/mcp.json:
{
"servers": {
"parserbee": {
"command": "npx",
"args": ["-y", "parserbee-mcp"],
"env": { "PARSERBEE_API_KEY": "pk_your_api_key" }
}
}
}git clone https://github.com/ParserBee/parserbee-mcp.git
cd parserbee-mcp
npm install
PARSERBEE_API_KEY=pk_your_api_key node dist/index.jsPoint your client at node /path/to/parserbee-mcp/dist/index.js.
Environment variable | Required | Use |
| Yes | Your API key from Settings |
| No | Defaults to |
extract_document returns the API response. The extracted fields are in data, shaped like your Parser Template:
{
"success": true,
"request_id": "req_abc123",
"data": {
"invoice_number": "INV-2026-001",
"vendor_name": "Acme Corp",
"total_amount": 1500
},
"credits_remaining": 449,
"usage": { "pages_processed": 1, "credits_charged": 1 }
}Files can be PDF, PNG, JPG, WebP or HEIC, up to 50 MB. Scans and phone photos work. API errors (an invalid key, no page credits left, an unknown template) come back as tool errors with the ParserBee error code, so the assistant can tell you what to fix.
The sample-invoices repository has 18 free test invoices with the correct value of every field, so you can check the results.
parserbee-python and parserbee-node: client libraries
parserbee-n8n: n8n workflows
parserbee-postman: Postman collection and OpenAPI file
Free browser tools: invoice parser, bank statement converter, receipt scanner
Comparing tools? See our test of invoice OCR software.
npm install
npm test
npm run buildMIT
Extract structured data from an invoice, receipt, purchase order, bank statement or other document with a ParserBee Parser Template. Give either file_path (a PDF or image on this computer) or file_url (a public link). Returns the extracted fields in data. Costs 1 ParserBee page credit per page. Use list_templates to find the template_id.
Inputs: template_id (required), file_url, file_path.
Get the ParserBee page credit balance, plan and subscription status.
Inputs: no named parameters.
Get one extraction request, including the extracted data.
Inputs: request_id (required).
Get one Parser Template with all of its fields.
Inputs: template_id (required).
List the last 10 extraction requests (status, file name, template, time).
Inputs: no named parameters.
List the Parser Templates in the ParserBee account (ID, name, description and fields). Use an ID with extract_document.
Inputs: no named parameters.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Scored across 6 tools
Each tool targets a distinct resource and action: listing/getting templates, extracting a document, checking credits, and listing/getting extraction records. The only potentially confusable pair (extract_document vs get_extraction) is clearly separated by the descriptions, which distinguish initiating an extraction from retrieving an existing request.
All six tools follow a consistent snake_case verb_noun pattern (list_templates, get_template, extract_document, get_credits, list_recent_extractions, get_extraction). Verbs map predictably to actions (list/get/extract).
Six tools is well within the ideal 3-15 range and each earns its place: template discovery, extraction, credit check, and extraction history/retrieval. Nothing feels redundant or missing at the count level.
The core workflow (find template, extract document, check credits, review past extractions) is fully covered. Minor gaps exist—templates are read-only (no create/update/delete), extraction history is capped at the last 10 with no pagination, and there is no retry/cancel for failed extractions—but agents can work around these via the ParserBee UI.
Extract, search and tag any document: invoices, receipts, contracts, templates. OAuth or API key.
Upload invoices for OCR; read, export and correct extracted invoices in Parseo.
Extract structured data from invoices, receipts, PDFs, scans, photos and emails. Create an inbox for a document type, define the fields and tables to extract (or propose a schema from a sample document), upload a document and get typed JSON back, review past documents, and add an optional Python post-processing step that is tested on a real document before it is enabled. 17 tools. Sign in with OAuth by pasting your Airparser API key (Account page of the Airparser app); the client only sees that account's inboxes and documents.
PDF tools + invoice extraction, bank statement parsing, GST reconciliation & GSTIN validation.
