CapyParse MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CAPYPARSE_API_KEY | Yes | Your CapyParse API key. Get one at https://capyparse.com/dashboard/settings/api-keys |
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 |
|---|---|
| convert_bank_statementA | Convert a PDF bank statement with CapyParse. Pass a local file_path or a downloadable file_url. Costs 1 credit per page. Returns a conversion id — poll get_conversion until status is 'completed' (typically 1-3 minutes, wait ~30s between polls), then call get_conversion_result. |
| get_conversionC | Check a conversion's status (queued | processing | completed | failed). When completed, includes a per-account summary with verification status. |
| get_conversion_resultA | Fetch the converted transactions for a completed conversion. format: markdown (default, ready-to-read tables), json (signed amounts: deposits positive / withdrawals negative), csv, or jsonl. provenance: none | summary (default — page/line citations, verbatim source text, verification status per row) | full (adds per-field sources). |
| list_conversionsA | List the team's recent conversions (newest first), including ones started from the CapyParse dashboard. Use this to find a conversion id. |
| get_creditsA | Check remaining CapyParse credits (1 credit = 1 statement page). Call before converting large documents or after an insufficient-credits error. |
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 5 tools
Each tool serves a unique purpose: starting a conversion, checking status, retrieving results, checking credits, and listing conversions. There is no overlap or ambiguity in their functions.
All tools follow a consistent verb_noun pattern in snake_case, such as 'convert_bank_statement' and 'get_conversion', making the set predictable and easy to navigate.
With 5 tools, the server is well-scoped for its purpose of parsing bank statements. Each tool is essential for the workflow, and the count is neither too small nor too large.
The tool set covers the complete lifecycle: initiating a conversion, monitoring progress, retrieving results in multiple formats, managing credits, and reviewing past conversions. No obvious gaps exist for the stated domain.