pdfvera MCP server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PDFVERA_API_KEY | Yes | Your pdfvera API key, created in your pdfvera account (e.g. pv_YOUR_KEY). Required to call the pdfvera API. |
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": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| convert_invoiceA | Convert a German PDF invoice into an e-invoice: XRechnung 3.0 (UBL and CII), a ZUGFeRD PDF (EN 16931) and a check report, checked against the KoSIT rules. Files are written next to the PDF. If mandatory data is missing, nothing is written and the result lists the missing fields with a German label, help text and example: ask the user for them (or use the offered escape value when it fits), then call again with the same PDF and |
| convert_bank_statementA | Convert a Brazilian bank statement PDF (extrato bancário) into OFX for an accounting system, CSV and Excel. The entries are summed and checked against the balances printed in the statement; files are only written when the balance reconciles. Password-protected PDFs need |
| get_usageA | Show the user's pdfvera plan and how many documents of the monthly quota are used. |
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 3 tools
Each tool targets a distinct operation and document domain: German invoice conversion, Brazilian bank statement conversion, and account usage reporting. convert_invoice and convert_bank_statement cannot be confused because the descriptions specify different input types and outputs.
All names use snake_case with a verb-first pattern (convert_invoice, convert_bank_statement, get_usage). The two conversion tools share the convert_ prefix, and get_usage is a clear retrieval verb.
Three tools are well-scoped for a service focused on two specific PDF conversion workflows plus quota reporting. Each tool has a clear, non-redundant role, and no extra tools are needed for the described functionality.
The surface covers both advertised conversion workflows, including missing-data handling, corrections, password handling, reconciliation, and quota checking. No obvious lifecycle step is missing for these stated purposes.