Skip to main content
Glama
payme-mcp

payme-mcp

by theYahia

🗄 Repositorio archivado

El desarrollo se ha trasladado a theYahia/WWmcp — un monorepositorio de servidores MCP para APIs no occidentales: CEI, MENA, África, LATAM, Sudeste Asiático. Núcleo común @theyahia/mcp-core, CI unificado, pipeline de lanzamiento unificado.

La versión actual de lo que estaba aquí: servers/payme/

El paquete en npm sigue siendo el mismo — @theyahia/payme-mcp, se instala y funciona como antes. Aquí ya no se actualiza nada. Las tareas y pull requests — en WWmcp.

Archivado: el desarrollo se trasladó a theYahia/WWmcp, un monorepositorio de servidores MCP para APIs no occidentales. La versión actual de este paquete ahora se encuentra en servers/payme/. El paquete npm @theyahia/payme-mcp no ha cambiado. Por favor, abre issues y pull requests allí.

payme-mcp

Servidor MCP para el sistema de pagos Payme (Uzbekistán). Utiliza el protocolo JSON-RPC 2.0. Admite transacciones, extractos, enlaces de pago y consultas de saldo.

Related MCP server: paymongo-mcp

Herramientas (8)

Herramienta

Descripción

create_transaction

Crear una nueva transacción de Payme

perform_transaction

Confirmar/realizar una transacción

cancel_transaction

Cancelar una transacción con motivo

check_transaction

Comprobar el estado de la transacción

get_statement

Obtener transacciones para un rango de tiempo

check_perform_transaction

Validar antes de crear

create_payment_link

Generar un enlace de pago

get_merchant_balance

Obtener el saldo del comerciante

Inicio rápido

{
  "mcpServers": {
    "payme": {
      "command": "npx",
      "args": ["-y", "@theyahia/payme-mcp"],
      "env": {
        "PAYME_MERCHANT_ID": "<YOUR_MERCHANT_ID>",
        "PAYME_KEY": "<YOUR_KEY>"
      }
    }
  }
}

Variables de entorno

Variable

Requerida

Descripción

PAYME_MERCHANT_ID

Sí

ID de comerciante del panel de Paycom

PAYME_KEY

Sí

Clave API del panel de Paycom

Ejemplos de demostración

  • "Crear una transacción de 50000 UZS para el pedido #789"

  • "Comprobar el estado de la transacción txn_abc123"

  • "Cancelar la transacción txn_abc123 con el código de motivo 3"

  • "Obtener todas las transacciones del 1 de marzo al 31 de marzo"

  • "Generar un enlace de pago de 100000 UZS"

Licencia

MIT

Available Tools

8 tools
cancel_transactionC

Cancel a transaction with a reason code.

Inputs: reason (required), transaction_id (required).

check_perform_transactionC

Validate if a transaction can be performed.

Inputs: amount (required), account (required).

check_transactionC

Check transaction status.

Inputs: transaction_id (required).

create_transactionC

Create a new Payme transaction (JSON-RPC).

Inputs: amount (required), account (required).

get_merchant_balanceB

Get merchant account balance.

Inputs: no named parameters.

get_statementC

Get transaction statement for a time period.

Inputs: to_timestamp (required), from_timestamp (required).

perform_transactionC

Perform (confirm) a created transaction.

Inputs: transaction_id (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    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.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      D
      maintenance
      MCP server for VNPay payment gateway (Vietnam). Supports payment URL generation, transaction queries, refunds, tokenized payments, and IPN verification with HMAC-SHA512 signing.
      8
      10 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      MCP server for PayMongo payment gateway (Philippines). Supports payment intents, sources, payments, refunds, and checkout sessions via Basic Auth.
      24
      22 npm
      2
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      MCP server for JazzCash mobile wallet and payments (Pakistan). Supports wallet payments, mobile account payments, vouchers, refunds, and balance inquiries.
      5
      15 npm
      1
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      MCP server for Bank of Georgia iPay payment gateway, enabling payment orders, refunds, recurring payments, and pre-authorization via OAuth 2.0 + JWT.
      8
      16 npm
      MIT