bankstatementparser-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_supported_formatsA | List every bank statement format identifier this server can parse. |
| detect_formatA | Detect which bank statement format an inline payload is. |
| parse_statementA | Parse an inline statement payload into transaction rows and a summary. |
| validate_statementA | Dry-run parse an inline statement to check it parses cleanly. |
| summarize_statementA | Summarize an inline statement's balances and totals only. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| analyze_statement | Guided prompt for reading and reconciling a bank statement. Args: filename: The statement filename being analysed. Returns: A prompt string instructing the model how to proceed. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| formats_resource | Describe each supported statement format and its file extensions. Returns: A human-readable catalogue of the supported formats. |
TDQS
Scored across 5 tools
Each tool has a distinct purpose: discovering formats, detecting format, parsing full statements, validating without returning rows, and summarizing balances. The overlap between parse_statement and the other parse-derived tools is explicitly disambiguated in their descriptions.
All tool names follow a consistent verb_noun pattern in snake_case: list_supported_formats, detect_format, parse_statement, validate_statement, summarize_statement. No mixed conventions or vague verbs.
Five tools is well-scoped for a bank statement parser server. Each tool covers a distinct stage or mode of use with no redundant extras.
The surface covers format discovery, format detection, validation, full parsing, and summary extraction—everything needed to work with bank statements. There are no obvious dead ends or missing lifecycle operations.