idpay-mcp
# idpay-mcp
MCP server for IDPay payment gateway (Iran). Supports payment creation, verification, inquiry, transaction listing, and payment links. Uses X-API-KEY header with optional X-SANDBOX mode.
## Tools (8)
| Tool | Description |
|------|-------------|
| `create_payment` | Create a payment |
| `verify_payment` | Verify a payment |
| `get_payment` | Get payment details |
| `list_transactions` | List transactions |
| `create_link` | Create a payment link |
| `get_link` | Get payment link details |
| `list_links` | List all payment links |
| `delete_link` | Delete a payment link |
## Quick Start
```json
{
"mcpServers": {
"idpay": {
"command": "npx",
"args": ["-y", "@theyahia/idpay-mcp"],
"env": {
"IDPAY_API_KEY": "<YOUR_API_KEY>",
"IDPAY_SANDBOX": "0"
}
}
}
}
```
## Environment Variables
| Variable | Required | Description |
|----------|----------|-------------|
| `IDPAY_API_KEY` | Yes | API key from IDPay dashboard |
| `IDPAY_SANDBOX` | No | Set to "1" for sandbox mode |
## Demo Prompts
- "Create a payment for 50000 IRR with order ID ORD-001"
- "Verify payment abc123 for order ORD-001"
- "List my recent transactions"
- "Create a payment link for 100000 IRR"
- "Delete payment link lnk_abc123"
## License
MIT
TDQS
Scored across 8 tools
Each tool clearly targets a distinct resource: payment links (list/create/get/delete) and payments (create/verify/get), with transactions listed separately. There is no ambiguity as the purpose of each tool is unique.
All tool names follow a consistent verb_noun pattern (e.g., list_links, create_payment, verify_payment). The verbs and nouns are predictable and consistently use snake_case.
With 8 tools, the server is well-scoped for a payment processing domain, covering both payments and payment links without unnecessary redundancy. The number is appropriate and neither too sparse nor overwhelming.
The tool set covers the core lifecycle for payments (create, verify, get) and payment links (create, list, get, delete). The only notable missing operation is an update for payment links, but this is a minor gap and does not severely hinder the primary workflows.