Bankstatemently provides an MCP server that lets AI agents parse bank statements into structured transactions, account metadata, and balances — no custom integration required.
Connect Claude Desktop, Cursor, VS Code, or any custom agent through the Model Context Protocol. Upload a PDF, get structured JSON back.
claude_desktop_config.json
{
"mcpServers": {
"bankstatemently": {
"url": "https://api.bankstatemently.com/mcp",
"headers": {
"X-API-Key": "bsk_live_..."
}
}
}
}You
"Analyze my expenses from this bank statement"
Agent
Calls parse_statement with the PDF
→ 47 transactions extracted → DBS Bank, SGD, Jan 2025 → Confidence: 97%
Agent
"Your top spending categories in January: Transport ($234), Food ($412), Subscriptions ($89). Total outflow: $2,847 across 47 transactions."
The Model Context Protocol (MCP) is an open standard that lets AI assistants connect to external tools and data sources. Instead of copy-pasting bank statement data or writing custom integrations, your agent calls Bankstatemently's tools directly — parse a PDF, get transactions back, all in one step.
Bankstatemently supports 55+ bank statement formats across 24+ countries, with dual-engine extraction (rule-based + vision LLM) for maximum accuracy.
Add to your claude_desktop_config.json:
{
"mcpServers": {
"bankstatemently": {
"url": "https://api.bankstatemently.com/mcp",
"headers": {
"X-API-Key": "bsk_live_..."
}
}
}
}Add to .cursor/mcp.json in your project root:
{
"mcpServers": {
"bankstatemently": {
"url": "https://api.bankstatemently.com/mcp",
"headers": {
"X-API-Key": "bsk_live_..."
}
}
}
}Add to .vscode/mcp.json in your project root:
{
"servers": {
"bankstatemently": {
"type": "http",
"url": "https://api.bankstatemently.com/mcp",
"headers": {
"X-API-Key": "bsk_live_..."
}
}
}
}Send JSON-RPC messages via POST https://api.bankstatemently.com/mcp with your API key in the X-API-Key header. The server implements the MCP Streamable HTTP transport (stateless mode).
All MCP requests require an API key. Generate one from your Developer Dashboard. The key is passed via the X-API-Key header in your MCP client configuration.
Pricing: 1 credit = 1 page of bank statement processed. Credits are shared across MCP and REST API usage. Check your balance anytime with the get_credits tool.
| Tool | Purpose | Type |
|---|---|---|
| parse_statement | Parse bank statement PDF | write |
| get_statement | Retrieve parsed results | read |
| list_statements | Browse parsed statements | read |
| get_credits | Check credit balance | read |
| Error | Cause | Resolution |
|---|---|---|
| Authentication required | Missing or invalid API key | Add X-API-Key header with a valid key |
| Key revoked / expired | API key has been revoked or expired | Generate a new key in the developer dashboard |
| Page limit exceeded | PDF exceeds your plan's page limit | Split into smaller PDFs or upgrade plan |
| Insufficient credits | Not enough credits for page count | Purchase credits or upgrade plan |
| Invalid PDF | File is not a valid PDF | Ensure file starts with %PDF- header |
| Wrong password | PDF is encrypted and password is missing or incorrect | Pass the correct password parameter |
| Document not found | No document with that ID exists | Check the document ID from parse_statement or list_statements |
| Rate limit exceeded | Too many requests (30 req/min for MCP) | Wait and retry after the reset window |
| Processing timeout | Processing exceeded 90 seconds | Use get_statement to poll for results |
MCP is an open standard by Anthropic that lets AI assistants connect to external tools and data sources. Think of it as a universal plug for AI — one protocol, many tools. Any MCP-compatible client can discover and use Bankstatemently's bank statement parsing tools automatically.
Same as the REST API — 1 credit per page of bank statement processed. Check your balance anytime with the get_credits tool. Credits are shared across MCP and REST API usage.
Claude Desktop, Cursor, VS Code (GitHub Copilot), Windsurf, and any custom agent built with the MCP SDK. The ecosystem is growing rapidly as more tools adopt the standard.
Yes. They share the same API key and credit balance. Use whichever fits your workflow — the REST API for programmatic integrations, MCP for AI agent workflows.
JSON (default), CSV, XLSX, QuickBooks (QBO), and Xero. Specify the format via the output_format parameter on parse_statement or get_statement.
Yes. Each request is independent — no session management needed. Your API key provides identity and authorization on every call.