Install
$ agentstack add mcp-sebastienrousseau-camt053-mcp ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
camt053-mcp: An MCP Server for ISO 20022 Bank Statements
[![PyPI Version][pypi-badge]][07] [![Python Versions][python-versions-badge]][07] [![License][license-badge]][01] [![Tests][tests-badge]][tests-url] [![Quality][quality-badge]][quality-url] [![OpenSSF Scorecard][scorecard-badge]][scorecard-url] [![OpenSSF Best Practices][bestpractices-badge]][bestpractices-url] [![Documentation][docs-badge]][docs-url]
A [Model Context Protocol][mcp] server that exposes the [camt053][core] ISO 20022 Bank Statement library as tools for AI agents and assistants — discover message types and return reasons, inspect input schemas, validate records and financial identifiers, parse incoming statements, and generate validated reversing-entry XML, all from your favourite MCP client.
> Latest release: v0.0.14 — OAuth 2.1 resource-server auth (RFC 9728) > on the HTTP transport, Prometheus metrics, a tamper-evident audit chain, > and real-HTTP load benchmarks; 22 MCP tools over stdio or authenticated > streamable HTTP, all backed by the shared camt053.services layer, > for Python 3.10+. > [See what's new →][release-0014]
Contents
- [Overview](#overview)
- [The ISO 20022 MCP Suite](#the-iso-20022-mcp-suite)
- [Install](#install)
- [Quick Start](#quick-start)
- [Tools](#tools)
- [Prompts](#prompts)
- [Resources](#resources)
- [Using the tools](#using-the-tools)
- [The camt053 suite](#the-camt053-suite)
- [When not to use camt053-mcp](#when-not-to-use-camt053-mcp)
- [Development](#development)
- [Security](#security)
- [Documentation](#documentation)
- [License](#license)
- [Contributing](#contributing)
- [Acknowledgements](#acknowledgements)
Overview
The [Model Context Protocol][mcp] (MCP) is an open standard that lets AI agents and assistants discover and call external tools in a uniform way. camt053-mcp is an MCP server that turns the [camt053][core] library into a set of first-class agent tools, so an assistant can read and reverse ISO 20022 camt.05x cash-management messages — the standardised bank-to-customer account reports, statements, and debit/credit notifications — directly from a conversation.
The headline capability is the one-shot reversing-entry workflow: read an incoming camt.053 statement, find the entries carrying a return reason code (e.g. AC04 Closed Account), and emit a validated reversing entry.
Every tool is a thin, typed wrapper over camt053.services — the single shared facade also used by the CLI and REST API — so all interfaces behave identically. Tools return JSON-serialisable data; on an error they return an {"error": ...} payload rather than raising.
- Website:
- Source code:
- Bug reports:
This package is part of the camt053 suite — a set of independently installable packages that share the camt053.services layer:
- [
camt053][core] — the core library (CLI + REST API) camt053-mcp— this package, the Model Context Protocol server- [
camt053-lsp][lsp] — the Language Server Protocol server for editors
flowchart LR
A["MCP client(Claude Desktop, IDE, agent)"] -->|stdio| B["camt053-mcp"]
B -->|delegates to| C["camt053.services"]
C -->|parse + reverse + validate| D["ISO 20022 camt.053 XML"]
The ISO 20022 MCP Suite
camt053-mcp is the bank-statement flagship of four coordinated, vendor-neutral MCP servers that together cover the ISO 20022 bank-statement workflow — statement depth, whole-catalogue routing, reconciliation, and multi-format ingestion. Dependency ranges are kept aligned across the suite, so the servers co-install cleanly in a single Python environment: start with one, add the rest as your workflow grows.
| Server | Scope | Surface | Install | Use it when | |------|------|------|------|------| | [camt053-mcp](#install) | ISO 20022 camt.053/camt.052 bank statements: parse, validate, filter, reverse; MT940/MT942 migration; CBPR+ readiness; journal export | 22 MCP tools · 4 prompts · 3 resources | pip install camt053-mcp | You work with bank-to-customer statements end to end — this package, the suite's flagship | | iso20022-mcp | Unified gateway: search / describe / validate / generate / parse meta-tools routed across the pain · pacs · camt · acmt families | 7 meta-tools | pip install "iso20022-mcp[all]" | You want one entry point to every message family | | reconcile-mcp | Matches expected pain.001 payments against observed camt.053 entries — exact, partial, one-to-many, many-to-one, every match scored and explained | 7 MCP tools | pip install reconcile-mcp | You need explainable statement/payment reconciliation |
In one line each: camt053-mcp is the bank-statement flagship (deepest camt.05x surface, stdio + authenticated streamable HTTP); iso20022-mcp is the generic message toolkit (a handful of verbs over the whole catalogue); reconcile-mcp is the reconciliation workflow (did the money we expected actually arrive?); and bankstatementparser-mcp is the ingestion layer (many formats in, one transaction shape out).
The suite also includes per-family servers — pain001-mcp (credit transfer initiation), pacs008-mcp (FI-to-FI credit transfers), and acmt001-mcp (account management) — reachable through the iso20022-mcp gateway.
Install
camt053-mcp runs on macOS, Linux, and Windows and requires Python 3.10+ and pip. It pulls in the core camt053 library and the MCP SDK automatically.
python -m pip install camt053-mcp
Using an isolated virtual environment (recommended)
python -m venv venv
source venv/bin/activate # macOS/Linux
venv\Scripts\activate # Windows
python -m pip install -U camt053-mcp
Quick Start
For the 10-minute install → MCP client config → first conversation tutorial, see [docs/quickstart.md](docs/quickstart.md).
Launch the server over stdio (the FastMCP default transport):
camt053-mcp
Register it with any MCP client (e.g. Claude Desktop) by adding it to the client's configuration:
{
"mcpServers": {
"camt053": { "command": "camt053-mcp" }
}
}
The agent can then call the tools below to parse incoming statements and generate validated reversing entries on demand.
For a shared, multi-tenant deployment, the server can also serve streamable HTTP with mandatory bearer-token auth and optional per-request Camt053-Account tenant scoping:
CAMT053_MCP_TOKEN= camt053-mcp --transport=http --bind=0.0.0.0:8080
See [Multi-tenant HTTP deployment](docs/quickstart.md#6-multi-tenant-http-deployment) and the [deployment cookbook](docs/deployment-cookbook.md).
Tools
All tools delegate to the shared camt053.services layer, so they behave identically to the CLI and REST API.
list_message_types— List the 3 supported camt.05x message typeslist_return_reasons— List the ISO external return reason codesget_required_fields— Required input fields for a message typeget_input_schema— Full input JSON Schema for a message typevalidate_records— Validate flat records against a message typevalidate_identifier— Validate an IBAN, BIC, or LEIvalidate_statement— Validate a statement against its XSD and detect its typeconvert_mt940_to_camt053— MT940 → camt.053 migration: convert legacy SWIFT MT940 statement text into a camt.053 structureconvert_mt942— MT942 → camt.052 migration: convert legacy SWIFT MT942 interim transaction report text into a camt.052 structurecheck_cbpr_readiness— Flag CBPR+ Nov 2026 cliff issues in a statementget_cbpr_cutover_date— Return the official CBPR+ cutover date (2026-11-16)cite_rulebook— Quote a curated SEPA / CBPR+ / HVPS+ rulebook clauselist_rulebook_clauses— List the available rulebook citations (optionally filtered)export_journal— Export statement entries as XeroBankTransactionsor QBOJournalEntrypayloadslist_export_journal_targets— List the accounting-platform targetsexport_journalsupportsclassify_entry— Classify a statement entry via MCP Sampling (uses the client's LLM)list_classify_entry_categories— List the default categoriesclassify_entryusesget_tenant_context— Report the multi-tenant scope of the call (theCamt053-Accountheader on the HTTP transport;Noneover stdio)parse_statement— Parse an incoming camt.05x statement into datalist_entries— List every entry across all statements (paginated)filter_entries— Return entries carrying a return reason code (paginated)generate_reversal— Generate a validated reversing-entry XML document
Pagination
list_entries and filter_entries accept optional offset (default 0) and limit (default None) parameters. When limit is omitted they return the full list, exactly as before. When limit is given they return a paginated envelope instead:
{"total": 42, "offset": 10, "limit": 5, "entries": [/* ... */]}
A negative offset or limit returns an {"error": ...} payload, consistent with the rest of the server's error convention.
Prompts
| Prompt | Purpose | |--------|---------| | reversal_preview | Guide an agent through a safe, confirm-before-generate reversal workflow | | reconcile_against_pain001 | Match booked statement entries to the originating pain.001 batch on EndToEndId, surface exceptions | | find_duplicate_entries | Flag exact + suspected duplicates on a statement with confidence and next-action hints | | match_to_invoice_set | Match incoming credits to an AR invoice ledger (exact + remittance + partial / multi-invoice tiers) |
reversal_preview takes an optional reason_code (default "AC04") and returns a four-step message template: parse the statement, preview the matching entries with filter_entries, confirm with the operator, then call generate_reversal. The other three prompts take no parameters and return a two-message user-prompt + assistant-walkthrough template the agent can replay verbatim.
Resources
Resources give an agent read-only reference context it can load without calling a tool. Each resource returns a JSON payload.
| Resource URI | Contents | |--------------|----------| | camt053://return-reasons | The ISO external return-reason catalog — a list of {"code", "name"} | | camt053://message-types | The supported camt.05x message types — a list of {"message_type", "name"} | | camt053://session/{session_id}/bank/{bic} | Templated per-(session, bank) context: parsed BIC country/kind, recommended SEPA / CBPR+ / HVPS+ rulebook clauses, Nov 2026 cutover date |
Both back onto the shared camt053.services layer, so they stay in sync with the equivalent list_return_reasons / list_message_types tools. On an error they return a serialised {"error": ...} payload.
Using the tools
You can invoke the tools in-process — without a transport — straight through the FastMCP instance. This mirrors what an agent receives over stdio. The runnable version of this snippet lives in [examples/mcp_tools.py](examples/mcp_tools.py).
import asyncio
from camt053_mcp.server import server
# A complete camt.053 statement with one entry returned AC04 (Closed Account).
statement_xml = """
STMT-MSG-00012026-06-15T08:00:00
STMT-00012026-06-15T08:00:00
GB29NWBK60161331926819EUR
CLBD
10000.00CRDT
2026-06-15
NTRY-0001
1500.00CRDT
BOOK
AC04
"""
async def main() -> None:
async def call(name, args):
result = await server.call_tool(name, args)
content = result[0] if isinstance(result, tuple) else result
return content[0].text if content else ""
# Validate an identifier.
print(await call("validate_identifier",
{"kind": "bic", "value": "NWBKGB2LXXX"}))
# -> {"kind": "bic", "value": "NWBKGB2LXXX", "valid": true}
# Page through the matching entries (paginated envelope).
print(await call("filter_entries",
{"xml": statement_xml, "reason_code": "AC04",
"offset": 0, "limit": 5}))
# -> {"total": 1, "offset": 0, "limit": 5, "entries": [...]}
# Generate a validated reversing-entry document for the AC04 entries.
xml = await call("generate_reversal",
{"xml": statement_xml, "reason_code": "AC04"})
print(xml[:46]) # -> ...
asyncio.run(main())
Run it directly:
python examples/mcp_tools.py
The camt053 suite
camt053-mcp is part of a set of independently installable packages built around the [camt053][core] library — pick whichever ones your stack needs:
| Package | Role | | :--- | :--- | | camt053 | Core library + CLI + FastAPI REST API | | camt053-mcp | Model Context Protocol server (this package) | | camt053-lsp | Language Server Protocol server (for editors) | | camt053-writer-xlsx | Excel .xlsx writer for parsed statements | | camt053-loader-mt940 | SWIFT MT940 → camt.053 loader |
Every tool here is a thin typed wrapper over camt053.services — the same facade the CLI, REST API, and LSP use — so all four interfaces behave identically.
When not to use camt053-mcp
- You have no MCP client. This server only makes sense paired
with an MCP-aware host (Claude Desktop, the IDE plugins, an agent framework). For scripted / CI use, the camt053 CLI and REST API cover the same ground without the stdio protocol overhead.
- You need to run as a long-lived daemon without an MCP client.
The server does run persistently over the streamable HTTP transport (--transport=http), but every consumer must still speak MCP JSON-RPC. For plain REST semantics, use the camt053 FastAPI service.
- You need streaming responses. Tool calls return whole values,
not streams. Large statements are paginated through the existing list_entries(xml, offset, limit) envelope, not chunked over multiple responses.
- You need per-user OAuth flows brokered for you. The HTTP
transport authenticates callers (OAuth 2.1 resource server with RFC 9728 metadata, or a static bearer token in dev mode) and scopes requests via the Camt053-Account tenant header, but it does not run an authorization server: bring your own IdP.
- **You need to generate pain.001 outbound payment files.** Out of
scope; use pain001-mcp.
Development
camt053-mcp uses Poetry and mise.
git clone https://github.com/sebastienrousseau/camt053-mcp.git && cd camt053-mcp
mise install
poetry install
poetry shell
A Makefile orchestrates the quality gates (kept in lockstep with CI):
make check # all gates (REQUIRED before commit)
make test # pytest
make lint # ruff + black
make type-check # mypy --strict
Security
camt053-mcp is a thin wrapper — every tool delegates to camt053.services, where the defence-in-depth (defusedxml + xml_guard byte cap + DOCTYPE / ENTITY pre-flight) lives. Tools catch (ValueError, Camt053Error) and return an {"error": ...} envelope per the suite convention; they never propagate raw exceptions to the MCP client. Reporting practice, supported versions, and the full supply-chain posture are documented in [SECURITY.md](SECURITY.md). Vulnerabilities go via GitHub
…
Source & license
This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: sebastienrousseau
- Source: sebastienrousseau/camt053-mcp
- License: Apache-2.0
- Homepage: https://camt053.com
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.