Skip to main content
Glama
README.md
# paytabs-mcp

MCP server for PayTabs payment gateway (MENA region). Supports payment pages, transactions, refunds, voids, tokenization, and payment method discovery.

## Tools (8)

| Tool | Description |
|---|---|
| `create_payment_page` | Create a hosted payment page |
| `query_transaction` | Query transaction details |
| `refund_transaction` | Refund a completed transaction |
| `create_token` | Tokenize a card for recurring payments |
| `charge_token` | Charge a saved card token |
| `list_transactions` | List transactions by date range |
| `void_transaction` | Void a pending transaction |
| `get_payment_methods` | Get available payment methods |

## Quick Start

```json
{
  "mcpServers": {
    "paytabs": {
      "command": "npx",
      "args": ["-y", "@theyahia/paytabs-mcp"],
      "env": {
        "PAYTABS_PROFILE_ID": "<YOUR_PROFILE_ID>",
        "PAYTABS_SERVER_KEY": "<YOUR_SERVER_KEY>"
      }
    }
  }
}
```

## Environment Variables

| Variable | Required | Description |
|---|---|---|
| `PAYTABS_PROFILE_ID` | Yes | Merchant profile ID |
| `PAYTABS_SERVER_KEY` | Yes | Server key from PayTabs dashboard |

## Demo Prompts

- "Create a payment page for 500 SAR for electronics order"
- "Check status of transaction TST2026040112345"
- "Refund 200 SAR from transaction TST2026040112345"
- "Void pending transaction TST2026040198765"
- "What payment methods are available for AED?"

## License

MIT

TDQS

A3.6/5.0

Scored across 8 tools

Disambiguation5/5

Each tool targets a distinct action: creating payment pages, querying, refunding, voiding, tokenization, charging tokens, listing, and fetching methods. No overlap exists.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (create_, query_, refund_, void_, list_, get_, charge_). The naming convention is uniform and predictable.

Tool Count5/5

With 8 tools, the set is well-scoped for a payment processing server, covering core payment operations without being bloated or sparse.

Completeness4/5

The surface covers the main payment lifecycle: creation, querying, refund, void, tokenization, and charging tokens. A minor gap is the lack of a capture/settlement operation, but most workflows are supported.

Maintenance

ActivityInactive
ResponsivenessSyncing