Spree Commerce: open-source B2B and marketplace ecommerce
Open-source B2B and marketplace ecommerce; new stores include an MCP server for AI agents.
作者提供的说明(英文原文)
payware A2A payments API for merchants, ISVs and payment institutions
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
PAYWARE_PARTNER_TYPE, PAYWARE_PARTNER_ID, PAYWARE_SANDBOX_PRIVATE_KEY_PATH, PAYWARE_PRODUCTION_PRIVATE_KEY_PATH, PAYWARE_OAUTH_CLIENT_ID, PAYWARE_OAUTH_CLIENT_SECRET, PAYWARE_MCP_TOOLSETS标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"payware": {
"command": "npx",
"args": [
"-y",
"@payware/mcp-server"
],
"env": {
"PAYWARE_PARTNER_TYPE": "your-value",
"PAYWARE_PARTNER_ID": "your-value",
"PAYWARE_SANDBOX_PRIVATE_KEY_PATH": "your-value",
"PAYWARE_PRODUCTION_PRIVATE_KEY_PATH": "your-value",
"PAYWARE_OAUTH_CLIENT_ID": "your-value",
"PAYWARE_OAUTH_CLIENT_SECRET": "your-value",
"PAYWARE_MCP_TOOLSETS": "your-value"
}
}
}
}在终端中运行这条命令
claude mcp add payware --env PAYWARE_PARTNER_TYPE=your-value --env PAYWARE_PARTNER_ID=your-value --env PAYWARE_SANDBOX_PRIVATE_KEY_PATH=your-value --env PAYWARE_PRODUCTION_PRIVATE_KEY_PATH=your-value --env PAYWARE_OAUTH_CLIENT_ID=your-value --env PAYWARE_OAUTH_CLIENT_SECRET=your-value --env PAYWARE_MCP_TOOLSETS=your-value -- npx -y @payware/mcp-server运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"payware": {
"command": "npx",
"args": [
"-y",
"@payware/mcp-server"
],
"env": {
"PAYWARE_PARTNER_TYPE": "your-value",
"PAYWARE_PARTNER_ID": "your-value",
"PAYWARE_SANDBOX_PRIVATE_KEY_PATH": "your-value",
"PAYWARE_PRODUCTION_PRIVATE_KEY_PATH": "your-value",
"PAYWARE_OAUTH_CLIENT_ID": "your-value",
"PAYWARE_OAUTH_CLIENT_SECRET": "your-value",
"PAYWARE_MCP_TOOLSETS": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"payware": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@payware/mcp-server"
],
"env": {
"PAYWARE_PARTNER_TYPE": "your-value",
"PAYWARE_PARTNER_ID": "your-value",
"PAYWARE_SANDBOX_PRIVATE_KEY_PATH": "your-value",
"PAYWARE_PRODUCTION_PRIVATE_KEY_PATH": "your-value",
"PAYWARE_OAUTH_CLIENT_ID": "your-value",
"PAYWARE_OAUTH_CLIENT_SECRET": "your-value",
"PAYWARE_MCP_TOOLSETS": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
PAYWARE_PARTNER_TYPE envPAYWARE_PRODUCTION_PRIVATE_KEY_PATH envPAYWARE_OAUTH_CLIENT_ID envPAYWARE_MCP_TOOLSETS env这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日
注册名称已通过 GitHub 账户 payware 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:PAYWARE_PARTNER_ID, PAYWARE_SANDBOX_PRIVATE_KEY_PATH, PAYWARE_OAUTH_CLIENT_SECRET
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(2.1.0)于昨天进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
同一分类中有:Spree Commerce: open-source B2B and marketplace ecommerce, Stripe MCP, MCP Cn Commerce
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Open-source B2B and marketplace ecommerce; new stores include an MCP server for AI agents.
MCP server integrating with Stripe - tools for customers, products, payments, and more.
8 read-only MCP platform entries; support is operation-specific; merchant live acceptance pending
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Official MCP (Model Context Protocol) server for payware payment API integration. This server enables AI assistants to interact with payware APIs, automating integration workflows for all partner types.
Releases are published to npm as @payware/mcp-server and to the official MCP Registry as io.github.payware/mcp-server. MIT licensed, see LICENSE.
contentSha256 header)ERR_INVALID_CONTENT_HASH, ERR_MISSING_CONTENT_HASHFor merchants, and for ISVs acting for them. Changes need the merchant's PRM plan; reading works on every plan.
pl ID, so every payment it starts is attributed to it. Includes the QR code, barcode and short link of each placementFrom npm (recommended):
npm install -g @payware/mcp-server
From source:
git clone https://github.com/payware/mcp-server.git
cd mcp-server npm install
Copy the example environment file and configure your credentials:
cp .env.example .env
Edit .env file:
# Partner ID from payware dashboard
PAYWARE_PARTNER_ID=your_partner_id_here
PAYWARE_SANDBOX_PRIVATE_KEY_PATH=keys/sandbox-your-private-key.pem PAYWARE_PRODUCTION_PRIVATE_KEY_PATH=keys/production-your-private-key.pem
PAYWARE_SANDBOX_URL=https://sandbox.payware.eu/api
⚠️ Security Note: Never commit the .env file to version control. It contains sensitive credentials.
Every tool definition goes into the assistant's context on every turn, and a merchant has over 70 of them. To offer only the groups you use, set PAYWARE_MCP_TOOLSETS to a comma-separated list:
PAYWARE_MCP_TOOLSETS=products,placements
Toolsets: auth, transactions, products, placements, data, logs, poi, shops, onboarding, utils. Unset, or all, loads every tool. An unknown name is ignored with a warning in the server log. A tool outside the chosen toolsets is neither listed nor callable; this narrows what the assistant is offered and does not change what your partner account may do. An ISV that obtains OAuth2 tokens through this server includes auth.
npm start
Tool: payware_authentication_generate_rsa_keys
Tool: payware_authentication_create_jwt_token
Parameters:
Tool: payware_authentication_setup_sandbox_auth
Parameters:
Tool: payware_operations_create_transaction
Parameters:
Tool: payware_operations_get_transaction_status
Parameters:
The payware MCP server transforms flat parameter inputs into the proper nested JSON structure required by the payware API:
{
// ROOT LEVEL - Transaction metadata "shop": "SHOP001", // Optional: Shop code "account": "GB29NWBK60161331926810", // Optional: Account identifier "friendlyName": "Your Shop Name", // Optional: Account holder name "callbackUrl": "https://callback.url", // Optional: HTTPS callback URL "passbackParams": "{\"orderId\":\"12345\"}", // Optional: Callback parameters
// TRANSACTION DATA - Required transaction information "trData": { "amount": "25.50", // String/Number: Amount (can be "0.00" for flexible amounts) "currency": "EUR", // REQUIRED: ISO 3-character currency code "reasonL1": "Payment for services", // REQUIRED: Transaction description (max 100 chars) "reasonL2": "Order #12345" // Optional: Additional description (max 100 chars) },
// TRANSACTION OPTIONS - Transaction behavior settings "trOptions": { "type": "QR", // PLAIN, QR, or BARCODE (default: PLAIN) "timeToLive": 300 // Seconds: 60-600 (default: 120) },
// QR OPTIONS - Only included when type=QR "qrOptions": { "qrFormat": "PNG", // PNG, SVG, JPG, GIF, BMP (default: SVG) "qrBorder": 4, // Border modules: 1-10 (default: 4) "qrErrorCorrection": "QUARTILE", // LOW, MEDIUM, QUARTILE, HIGH (default: QUARTILE) "qrScale": 16, // Pixel size: 1-100 (default: 16, irrelevant for SVG) "qrVersion": 10 // QR version: 1-40 (default: 10, auto if not specified) },
// BARCODE OPTIONS - Only included when type=BARCODE "barOptions": { "barFormat": "SVG", // PNG, SVG, JPG (default: SVG) "barModuleWidth": 2, // Module width: 1-10 (default: 2) "barBarHeight": 100, // Height: 15-1000 (default: 100) "barFontSize": 12, // Font size: 0-24 (default: 12) "barHumanReadableLocation": "NONE" // NONE, BOTTOM, TOP (default: NONE) } }
When using MCP tools, parameters are automatically mapped to the correct API structure:
| MCP Tool Parameter | API Location | Description |
|---|---|---|
partnerId, privateKey | Authentication | Used for JWT signing, not sent in request |
account, friendlyName, shop, callbackUrl, passbackParams | Root Level | Transaction metadata |
amount, currency, reasonL1, reasonL2 | trData object | Core transaction data |
type, timeToLive | trOptions object | Transaction behavior |
qrFormat, qrBorder, etc. | qrOptions object | QR code settings (when type=QR) |
barFormat, barModuleWidth, etc. | barOptions object | Barcode settings (when type=BARCODE) |
payware_generate_code_exampleAdvanced multi-language code generation with framework support
Supports 60+ operations across all partner types:
payware_generate_documentationComprehensive documentation generator
Generates complete API documentation with working code examples for any partner type and programming language combination.
payware_authentication_generate_rsa_keysGenerate RSA key pair for API authentication.
Parameters:
keySize (optional): RSA key size in bits (default: 2048)payware_authentication_create_jwt_tokenCreate JWT token for API authentication.
Parameters:
partnerId (required): Partner ID from paywareprivateKey (required): RSA private key in PEM formatpayware_authentication_validate_jwtValidate JWT token format and signature.
Parameters:
token (required): JWT token to validatepartnerId (required): Partner ID for validationpayware_authentication_test_jwtTest JWT token with payware API.
Parameters:
token (required): JWT token to testpartnerId (required): Partner IDpayware_authentication_setup_sandbox_authSetup sa
只显示了开头部分;其余内容请在仓库中阅读