Payware MCP Server

Payware is an MCP integration. Payware A2A payments API for merchants, ISVs and payment institutions.

Packages and local setup

The published npm package is @payware/mcp-server, version 1.4.0. Its declared MCP transport is stdio.

The package declares PAYWARE_PARTNER_TYPE: Partner role: merchant, isv or payment_institution; PAYWARE_PARTNER_ID (required): Partner ID from the payware dashboard; PAYWARE_SANDBOX_PRIVATE_KEY_PATH (required): Path to the RSA private key for the sandbox; PAYWARE_PRODUCTION_PRIVATE_KEY_PATH: Path to the RSA private key for production; PAYWARE_OAUTH_CLIENT_ID: OAuth2 client ID (ISV partners only); PAYWARE_OAUTH_CLIENT_SECRET: OAuth2 client secret (ISV partners only); PAYWARE_MCP_TOOLSETS: Comma-separated toolsets to load, e.g. products,placements. Unset loads every tool. Toolsets: auth, transactions, products, placements, deep_links, data, logs, poi, shops, onboarding, utils.

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 1.4.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related payments & commerce MCP servers for tools that cover the same kind of work.