# payware MCP server

> Enables AI assistants to interact with payware APIs to automate A2A payments, manage products, and handle transaction workflows for merchants and ISVs.

- Repository: https://github.com/payware/mcp-server
- Page: https://hostedmcp.org/servers/payware/mcp-server
- Transport: stdio
- Stars: 0
- License: MIT
- Latest version: 2.3.0

## Install

### Claude Code

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

### Cursor (`~/.cursor/mcp.json`)

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

### VS Code (`.vscode/mcp.json`)

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

### VS Code CLI

```sh
code --add-mcp '{"name":"mcp-server","type":"stdio","command":"npx","args":["-y","@payware/mcp-server"],"env":{"PAYWARE_OAUTH_CLIENT_SECRET":"<YOUR_PAYWARE_OAUTH_CLIENT_SECRET>"}}'
```

### Claude Desktop (`claude_desktop_config.json`)

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

### Codex

```sh
codex mcp add mcp-server --env 'PAYWARE_OAUTH_CLIENT_SECRET=<YOUR_PAYWARE_OAUTH_CLIENT_SECRET>' -- npx -y @payware/mcp-server
```

### Codex config.toml (`~/.codex/config.toml`)

```toml
[mcp_servers.mcp-server]
command = "npx"
args = ["-y", "@payware/mcp-server"]

[mcp_servers.mcp-server.env]
PAYWARE_OAUTH_CLIENT_SECRET = "<YOUR_PAYWARE_OAUTH_CLIENT_SECRET>"
```

### Gemini CLI

```sh
gemini mcp add -s user -e 'PAYWARE_OAUTH_CLIENT_SECRET=<YOUR_PAYWARE_OAUTH_CLIENT_SECRET>' mcp-server npx -- -y @payware/mcp-server
```

### Gemini settings.json (`~/.gemini/settings.json`)

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

## Environment variables

| Name | Required | Secret | Description |
|---|---|---|---|
| `PAYWARE_OAUTH_CLIENT_SECRET` | no | yes | OAuth2 client secret (ISV partners only) |
| `PAYWARE_LINKS_BASE_URL` | no | no | Payer 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_TOOLSETS` | no | no | Comma-separated toolsets to load, e.g. products,placements. Unset loads every tool. Toolsets: auth, transactions, products, placements, data, logs, poi, shops, onboarding, utils, payer |
| `PAYWARE_OAUTH_CLIENT_ID` | no | no | OAuth2 client ID (ISV partners only) |
| `PAYWARE_PARTNER_ID` | no | no | Partner ID from the payware dashboard (not needed for the payer role) |
| `PAYWARE_PARTNER_TYPE` | no | no | Partner role: merchant, isv, payment_institution or payer (a buying agent, no keys needed) |
| `PAYWARE_PRODUCTION_PRIVATE_KEY_PATH` | no | no | Path to the RSA private key for production |
| `PAYWARE_SANDBOX_PRIVATE_KEY_PATH` | no | no | Path to the RSA private key for the sandbox (not needed for the payer role) |
| `PAYWARE_SANDBOX_URL` | no | no |  |

## FAQ

### Can I generate code examples for my integration?

Yes, the server can write complete, signed programs in Python, Node.js, PHP, Java, C#, or curl for real routes.

### How can I limit the tools available to the AI assistant?

You can use the PAYWARE_MCP_TOOLSETS environment variable to provide a comma-separated list of specific toolsets like products or placements.
