pbsq-sk

This MCP server wraps the PayBySquare generator library to create, decode, and validate PayBySquare QR codes. It exposes a set of tools that let you generate QR codes from payment data, save them to files, decode QR codes back to data, and perform comprehensive compliance checks. Core capabilities include: generating a PNG QR code via generatePayBySquare (or saving to a file with generatePayBySquareToFile), decoding a PNG with decodePayBySquare, and validating data against banking standards with isCompliant, checkCompliance, checkQRCompliance, and verifyRoundTrip. The server is designed to integrate with MCP clients like Claude Desktop, enabling automated generation and verification workflows for payment QR codes. Use it to produce QR codes from structured input such as IBAN, beneficiaryName, amount, currency, and optional fields, then verify and audit the results with the built-in compliance tooling.

Prerequisites:

• Node.js >= 18.0.0
• npm (comes with Node.js)

Installation steps:

1. Create a project directory and initialize it (optional): mkdir pbsq-mcp-server && cd pbsq-mcp-server npm init -y

2. Install the PayBySquare-related library (the MCP server uses this under the hood): npm install paybysquare-generator

3. Add a simple server entry point (example: server.js) that initializes and exposes the MCP server logic. A minimal example might look like:

   // server.js const { createServer } = require('http'); // Import and initialize MCP server logic here, depending on your MCP framework // This is a placeholder to illustrate where the MCP server would be started const port = process.env.PORT || 3000; const server = createServer((req, res) => { res.statusCode = 200; res.end('pbsq-sk MCP server placeholder'); }); server.listen(port, () => { console.log(pbsq-sk MCP server listening on port ${port}); });

4. Run the server: node path/to/server.js

5. Optional: configure environment variables (see additional notes) and integrate with your MCP client workflow.

Notes and tips:

• The MCP server uses Node.js >= 18 with ESM module support; ensure your runtime matches.
• The PayBySquare generator supports generation, decoding, and validation of PayBySquare data. The library emphasizes that beneficiaryName is required for generation, and the modern API can return file paths for generated QR codes (instead of base64 data) to improve token/LLM context usage.
• If you enable the outputDirectory option (or set OUTPUT_DIRECTORY), generated QR codes will be saved to disk and the filePath will be returned by generator helpers that you wire into your MCP server.
• For international payments, consider marking BIC (swift) as RECOMMENDED in your validation logic to catch common issues before sending data to banks.
• If you run into issues with input data validation, check the detailed compliance reports produced by checkCompliance or verifyRoundTrip to diagnose round-trip fidelity.
• Ensure environment variables and file system permissions allow writing to the configured output directory.
• When upgrading, review breaking changes noted in the library’s changelog to adjust how you consume file-based QR codes versus in-memory buffers.