Pain001 MCP server

<!-- SPDX-License-Identifier: Apache-2.0 OR MIT>

pain001-mcp

ISO 20022 pain.001 and pain.008 payment files for AI agents: generate, validate, convert MT101 and parse bank replies through 21 Model Context Protocol tools over the pain001 library.

Tool catalogue: every tool, its description and its arguments, generated

from the running server, is in docs/tools.md.

Contents

Getting started

• What is pain001-mcp? — the problem it solves
• Install — PyPI, virtualenv, Docker
• Quick start — register with Claude Desktop in 30 seconds
• Transports — stdio, streamable HTTP (2026-07-28 and 2025-11-25) and SSE from one command line

Library reference

• Tools — the 21 tools, one resource, one prompt
• Using the tools — call them in-process from Python
• The pain001 suite — core lib, MCP server, LSP server

Operational

• When not to use pain001-mcp — honest boundaries
• Development — gates, make targets
• Security — sandboxing posture
• Documentation — examples, guides
• Contributing — how to get changes in
• License — Apache-2.0

What is pain001-mcp?

The Model Context Protocol (MCP) is an open standard that lets AI agents discover and call external tools in a uniform way. pain001-mcp is the MCP server that turns the pain001 ISO 20022 payment library into 21 first-class agent tools — so an assistant can generate and validate pain.001 Customer Credit Transfer Initiation and pain.008 Customer Direct Debit Initiation messages (the standardised payment instructions behind SEPA and cross-border credit transfers) directly from a conversation.

Every tool is a thin, typed wrapper over the pain001 public API (validators, schema loaders, generatexmlstring, parsers, the version mapper, the ISO 20022 charset sanitiser), so all interfaces behave identically to the CLI, REST API, and in-tree MCP server. Tools return JSON-serialisable data; on a validation error they return an {"error": ...} payload rather than raising.

Shortened. The full README is on GitHub.