payme-mcp
by theYahia
README.md
> ## 🗄 Репозиторий заархивирован
>
> Разработка переехала в **[theYahia/WWmcp](https://github.com/theYahia/WWmcp)** — монорепозиторий MCP-серверов для незападных API: СНГ, MENA, Африка, LATAM, Юго-Восточная Азия. Общее ядро `@theyahia/mcp-core`, единый CI, единый релизный конвейер.
>
> Актуальная версия того, что лежало здесь: [`servers/payme/`](https://github.com/theYahia/WWmcp/tree/main/servers/payme)
>
> Пакет в npm прежний — [`@theyahia/payme-mcp`](https://www.npmjs.com/package/@theyahia/payme-mcp), ставится и работает как раньше.
> Здесь больше ничего не обновляется. Задачи и pull request'ы — в WWmcp.
>
> **Archived — development moved to [theYahia/WWmcp](https://github.com/theYahia/WWmcp),** a monorepo of MCP servers for non-Western APIs.
> The current version of this package now lives at [`servers/payme/`](https://github.com/theYahia/WWmcp/tree/main/servers/payme).
> The npm package [`@theyahia/payme-mcp`](https://www.npmjs.com/package/@theyahia/payme-mcp) is unchanged.
> Please open issues and pull requests there.
# payme-mcp
MCP server for Payme payment system (Uzbekistan). Uses JSON-RPC 2.0 protocol. Supports transactions, statements, payment links, and balance queries.
## Tools (8)
| Tool | Description |
|------|-------------|
| `create_transaction` | Create a new Payme transaction |
| `perform_transaction` | Confirm/perform a transaction |
| `cancel_transaction` | Cancel a transaction with reason |
| `check_transaction` | Check transaction status |
| `get_statement` | Get transactions for a time range |
| `check_perform_transaction` | Validate before creating |
| `create_payment_link` | Generate a checkout link |
| `get_merchant_balance` | Get merchant balance |
## Quick Start
```json
{
"mcpServers": {
"payme": {
"command": "npx",
"args": ["-y", "@theyahia/payme-mcp"],
"env": {
"PAYME_MERCHANT_ID": "<YOUR_MERCHANT_ID>",
"PAYME_KEY": "<YOUR_KEY>"
}
}
}
}
```
## Environment Variables
| Variable | Required | Description |
|----------|----------|-------------|
| `PAYME_MERCHANT_ID` | Yes | Merchant ID from Paycom dashboard |
| `PAYME_KEY` | Yes | API key from Paycom dashboard |
## Demo Prompts
- "Create a transaction for 50000 UZS for order #789"
- "Check the status of transaction txn_abc123"
- "Cancel transaction txn_abc123 with reason code 3"
- "Get all transactions from March 1 to March 31"
- "Generate a payment link for 100000 UZS"
## License
MIT
TDQS
B3.2/5.0
Scored across 8 tools
Disambiguation4/5
Tools are mostly distinct in purpose, but 'check_perform_transaction' and 'check_transaction' could be confused if descriptions are not read carefully. Overall, each tool targets a specific action.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern in snake_case (e.g., cancel_transaction, create_payment_link). No mixing of conventions.
Tool Count5/5
8 tools cover the essential payment lifecycle (create, validate, perform, cancel, status, balance, statement, payment link) without being excessive or insufficient.
Completeness4/5
Core payment operations are covered, but missing refund or void capabilities. The surface is functional for basic workflows but has minor gaps.
Maintenance
ActivityMaintained
ResponsivenessNo issues