Skip to content
MCP server

payware

Create and test payware A2A payments, POIs and products from an AI assistant

Runs locallyStatus and history
Pricing
Open source
Platforms
CLI, API
Runs
Locally
Version
2.3.0
Listing updated
3 days ago

About payware

payware is an open-source MCP server for finance and payments. It runs locally on your machine and is started by your AI client.

This is payware's official server for merchants, ISVs and payment institutions. Each partner role loads the tools it needs, and a PAYWARE_MCP_TOOLSETS setting can limit loading to groups such as products or placements; the groups are auth, transactions, products, placements, data, logs, poi, shops, onboarding and utils.

The tools cover RSA key and JWT generation for sandbox setup, creating plain, QR and barcode transactions, checking status and history, and simulating callbacks. Point-of-interaction tools set or cancel a price on a POI, fetch its QR code and list a merchant's POIs. Campaign and placement tools need the merchant's PRM plan for changes.

Version 2.2 added partial product and schedule updates through update_product and update_schedule, an execution lock for payment institutions, deferred merchant legs, and payware_generate_code_example, which writes signed example programs for real routes. It runs over stdio from npm and needs a partner ID and a sandbox RSA private key.

Install

Run in a terminal

claude mcp add mcp-server --env PAYWARE_OAUTH_CLIENT_SECRET='<PAYWARE_OAUTH_CLIENT_SECRET>' -- npx -y @payware/mcp-server

Add to claude_desktop_config.json

{
  "mcpServers": {
    "mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@payware/mcp-server"
      ],
      "env": {
        "PAYWARE_OAUTH_CLIENT_SECRET": "<PAYWARE_OAUTH_CLIENT_SECRET>"
      }
    }
  }
}

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@payware/mcp-server"
      ],
      "env": {
        "PAYWARE_OAUTH_CLIENT_SECRET": "<PAYWARE_OAUTH_CLIENT_SECRET>"
      }
    }
  }
}

Add to .vscode/mcp.json

{
  "servers": {
    "mcp-server": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@payware/mcp-server"
      ],
      "env": {
        "PAYWARE_OAUTH_CLIENT_SECRET": "<PAYWARE_OAUTH_CLIENT_SECRET>"
      }
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@payware/mcp-server"
      ],
      "env": {
        "PAYWARE_OAUTH_CLIENT_SECRET": "<PAYWARE_OAUTH_CLIENT_SECRET>"
      }
    }
  }
}

Add to your client's MCP settings (most use this shape)

{
  "mcpServers": {
    "mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@payware/mcp-server"
      ],
      "env": {
        "PAYWARE_OAUTH_CLIENT_SECRET": "<PAYWARE_OAUTH_CLIENT_SECRET>"
      }
    }
  }
}

Configuration

  • PAYWARE_PARTNER_TYPEPartner role: merchant, isv, payment_institution or payer (a buying agent, no keys needed)
  • PAYWARE_PARTNER_IDPartner ID from the payware dashboard (not needed for the payer role)
  • PAYWARE_SANDBOX_PRIVATE_KEY_PATHPath to the RSA private key for the sandbox (not needed for the payer role)
  • PAYWARE_PRODUCTION_PRIVATE_KEY_PATHPath to the RSA private key for production
  • PAYWARE_OAUTH_CLIENT_IDOAuth2 client ID (ISV partners only)
  • PAYWARE_OAUTH_CLIENT_SECRETOAuth2 client secret (ISV partners only)
  • PAYWARE_LINKS_BASE_URLPayer role only: the base URL of the public link host, e.g. http://localhost:8080 for a local payware server. Defaults to https://go-sandbox.payware.eu (sandbox) or https://go.payware.eu (production)
  • PAYWARE_MCP_TOOLSETSComma-separated toolsets to load, e.g. products,placements. Unset loads every tool. Toolsets: auth, transactions, products, placements, data, logs, poi, shops, onboarding, utils, payer

Tools this server provides (4)

Taken from the project documentation; the running server may differ.

payware_generate_code_example
Writes complete, signed example programs for real payware routes.
payware_products_get_product_image
Returns a product image, including for an ISV acting for a merchant.
update_product
Sends only the product fields you give, keeping stored values.
update_schedule
Sends only the schedule fields you give, keeping stored values.

What it does

Role-based setup
Works for merchants, ISVs with OAuth2, and payment institutions.
Transaction tools
Create PLAIN, QR and BARCODE transactions and check their status.
POI price control
Set, cancel and read prices on points of interaction and fetch QR codes.
Toolset filtering
Load only chosen groups such as products or placements.
Callback simulation
Test merchant and institution callback scenarios.
Signed code examples
Generate complete example programs for real API routes.

Good for

  • Prototype a payware integration in the sandbox
  • Generate JWT-authenticated example code
  • Update a product price schedule from chat
  • Test payment callbacks before go-live
  • Manage POI prices for a shop

Pricing

Open source

Server is MIT licensed; payware plans are separate, with a 0.5% plus VAT transaction fee listed

Prices change. Check payware.eu before you buy.

payware FAQ

How do I install it?

Install the npm package @payware/mcp-server; it runs over stdio.

What credentials are required?

A partner ID and a path to the sandbox RSA private key; a production key and OAuth2 credentials for ISVs are optional.

What licence is it under?

MIT.

Can I limit which tools load?

Yes, set PAYWARE_MCP_TOOLSETS to a comma-separated list of toolsets.

Is payware free?

Yes. payware is open source, so you can use and self-host it for free.

How do I add payware to Claude Code?

Run this command in your terminal: claude mcp add mcp-server --env PAYWARE_OAUTH_CLIENT_SECRET='<PAYWARE_OAUTH_CLIENT_SECRET>' -- npx -y @payware/mcp-server

What are the best alternatives to payware?

The closest alternatives to payware are REA, Codebase Memory, GitHub, Serena MCP: the IDE for your agent and XERJ.

Alternatives to payware

  1. REA

    MCP server

    CLI and MCP server that lets coding agents reverse engineer apps and binaries

    Runs locally
    • Open source
    • 464K GitHub stars
    • Developer tools
  2. Codebase Memory

    MCP server

    Local MCP server that builds a code knowledge graph for AI coding agents

    Runs locally
    • Open source
    • 48.7K GitHub stars
    • Knowledge and memory
  3. GitHub

    MCP server

    Official MCP server connecting AI assistants to GitHub repos, issues and workflows

    Not checked yet
    • Remote
    • Open source
    • 34.5K GitHub stars
    • Developer tools
  4. MCP toolkit giving coding agents symbol-level code retrieval and editing

    Runs locally
    • Open source
    • 31.5K GitHub stars
    • Developer tools
  5. XERJ

    MCP server

    Local search engine for AI agents with cited answers over your code and docs

    Runs locally
    • Open source
    • 19.2K GitHub stars
    • Knowledge and memory
  6. Ouroboros

    MCP server

    Spec-first layer that pins requirements and verifies results of AI coding agent work

    Runs locally
    • Open source
    • 6.4K GitHub stars
    • Developer tools