parserbee-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PARSERBEE_API_KEY | Yes | Your ParserBee API key from Settings. It starts with `pk_`. | |
| PARSERBEE_BASE_URL | No | The base URL for the ParserBee API. Defaults to `https://app.parserbee.com`. | https://app.parserbee.com |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| extract_documentA | 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 |
| list_templatesA | List the Parser Templates in the ParserBee account (ID, name, description and fields). Use an ID with extract_document. |
| get_templateA | Get one Parser Template with all of its fields. |
| get_creditsA | Get the ParserBee page credit balance, plan and subscription status. |
| list_recent_extractionsA | List the last 10 extraction requests (status, file name, template, time). |
| get_extractionB | Get one extraction request, including the extracted data. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
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.