ISO 20022 AI MCP Server
Your AI assistant just learned the entire ISO 20022 specification.
Stop hunting through schemas. Stop second-guessing field names. Stop waiting for the one person on your team who's done this before. Just ask.
The specification that runs global finance — and the problem it creates
ISO 20022 is the international standard for financial messaging. Payments between banks. Securities settlements. Trade finance instructions. Foreign exchange confirmations. If money moves between financial institutions anywhere in the world, there is a very good chance an ISO 20022 message is involved.
The standard is also, by any fair measure, enormous.
The full repository holds over 2,500 message definitions organized across more than 40 business areas. Each message is built from hundreds of components, data types, and code sets, each with their own field-level rules, cardinality constraints, and usage notes. Three major versions are in active deployment simultaneously. SWIFT, SEPA, CBPR+, FedNow, and T2 all use ISO 20022 — with their own profiles, extensions, and local rules layered on top.
The official documentation runs to thousands of pages. The XSD schema files are dense, deeply nested, and cross-referenced. There is no single place to look something up. Every integration requires hunting through multiple documents, checking multiple versions, and ideally consulting someone who has done it before.
This is why ISO 20022 projects are expensive and slow — and why seemingly small mistakes (wrong code value, missing mandatory field, wrong message version) only surface at testing time, or worse, at settlement.
What MCP changes — and why it matters
Your AI assistant is powerful. It can read code, write code, explain concepts, and synthesize information. But until now, when you asked it about ISO 20022, it was answering from memory — from whatever happened to be in its training data. That training data has a cutoff date. It may be incomplete. For a domain as specialized and version-sensitive as ISO 20022, “from memory” is often not good enough.
The Model Context Protocol (MCP) is an open standard that solves this. It gives AI assistants a live connection to external data sources — tools they can call during a conversation to look things up, not just recall them.
Think of the difference this way: before MCP, your AI assistant was a brilliant colleague who had read a lot about ISO 20022 a while ago and was doing their best to remember. With MCP, that same colleague has the complete specification open on their desk and can look up anything — precisely, immediately, without guessing.
The ISO 20022 AI MCP Server is that connection. Configure it once in your AI client, and every conversation becomes a live query session against the full, current specification. Your AI doesn’t guess field names. It looks them up. It doesn’t approximate code set values. It reads the authoritative list. It doesn’t estimate what changed between versions. It shows you the diff.
One configuration. Every question answered from the live spec.
What you can do
Ask anything about the spec
“What fields are mandatory in a pain.001.001.09 CustomerCreditTransferInitiation?”
“What’s the difference between a pain.001 and a pacs.008, and when should I use each?”
“What are the valid ServiceLevel code values for a SEPA credit transfer?”
Your AI queries the live specification and returns precise, structured answers — field definitions, cardinality rules, usage notes, and cross-references — not a best guess from training data.
Generate working code
“Write a C# class for a pacs.008 FIToFICustomerCreditTransfer with all required fields.”
“Generate a valid XML sample for a pain.002 CustomerPaymentStatusReport.”
“Create a TypeScript interface for the CreditorAgent component.”
The AI reads the structure from the live spec before writing a single line. The result isn’t close — it’s correct. No manual schema-checking required.
Navigate version migrations
“What changed between pain.001.001.03 and pain.001.001.09?”
“We’re migrating from MT103 to pacs.008. What’s the field mapping?”
“Which fields in our current implementation won’t be valid in the new version?”
Version migration is one of the most error-prone tasks in ISO 20022 development. The MCP server tracks every version difference so your AI can walk you through migrations accurately, completely, and without omissions.
Cross-reference and validate
“What’s the equivalent of SWIFT MT103 field 32A in ISO 20022?”
“Does my pacs.009 message conform to the CBPR+ usage guidelines?”
“How does ISO 20022 model this concept compared to FIX protocol?”
Cross-reference between ISO 20022, SWIFT MT, FIX, and SEPA. Validate your messages against the spec before they reach your testing environment — or your counterpart’s rejection queue.
Works with the tools you already use
No new interface to learn. No separate application to open. The MCP server plugs directly into the AI client you’re already working in.
Claude Code (CLI & VS Code)
The fastest path. Add the server with a single command and every Claude Code session — in your terminal, in VS Code, anywhere — gains live spec access. Native SSE connection, no bridge required.
Claude Desktop
Full conversational access. Configure once and every Claude Desktop chat becomes a live spec session. Uses mcp-remote as a lightweight bridge between Claude Desktop and the server.
Cursor
The AI coding editor gets authoritative spec knowledge. Add a five-line config to mcp.json and Cursor knows the full ISO 20022 standard alongside your codebase. Native SSE — no bridge needed.
VS Code + GitHub Copilot
Wire it into VS Code’s MCP configuration and GitHub Copilot Chat gains precise spec access during code review, generation, and refactoring. One workspace config, immediate results.
Built for everyone who touches ISO 20022
Developers
Generate correct message implementations in any language. Understand exactly which fields to populate and why. Get code that compiles, conforms, and handles edge cases — without leaving your editor to hunt through schemas.
The hours you used to spend cross-referencing spec documents become seconds.
Architects & analysts
Map message flows across your payment infrastructure. Trace migration paths from MT to MX. Understand message interactions, component dependencies, and version compatibility — instantly, with full citation back to the specification.
Spec questions that used to require a specialist now have immediate, authoritative answers.
Banks & fintechs
ISO 20022 expertise is scarce and expensive. The institutional knowledge that lives in the heads of your most senior engineers — the field mappings, the gotchas, the version quirks — now lives in a server that any member of your team can query.
Onboard faster. Build faster. Make fewer expensive mistakes.
See it in action
See real examples of what developers and analysts have asked — and exactly what the MCP server and AI delivered in response. Code generation, message validation, migration analysis, cross-standard mapping.
Browse use cases →Start in five minutes
The Free tier requires no credit card. Connect your AI client, ask your first question, and see the difference for yourself. Upgrade to Pro when you need schema validation, migration guidance, and cross-standard references.