Business PDF Field Extractor MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your Apify API token from console.apify.com/account/integrations. The server lists its tool without a token; a call needs one. |
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_business_pdf_fieldsA | Read invoices, purchase orders, and contracts from PDF addresses and return fixed fields: numbers, dates, parties, totals, line items, and a totals check, or contract parties, dates, term, renewal, notice days, governing law, and clauses found. Scans go through OCR. Rule based with no AI, so a value with no known label stays null. Pay per event on Apify: 0.01 USD per document, 0.015 USD per scanned page. |
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 1 tool
There is only one tool, so there is no possibility of tool selection confusion. Its purpose (extracting fixed fields from business PDFs) is stated clearly and covers both invoice/PO and contract extraction paths.
The single name extract_business_pdf_fields follows a clear verb_noun snake_case convention that matches the domain. There are no competing conventions to introduce inconsistency.
A single tool is thin relative to the stated scope, which spans invoices, purchase orders, and contracts with two distinct output schemas. It is defensible as a wrapper around one extraction actor, but a second tool (e.g. contract vs. invoice extraction, or batch input) would sharpen the surface.
The tool covers the full read-only extraction lifecycle, including OCR, line items, totals validation, and contract clauses, which is complete for a pay-per-document extractor. Minor gaps exist: no batch/multi-document input, no schema or field-selection option, and null results for unlabeled values leave no verification path beyond the totals check.