Safely connect AI agents to MyFatoorah payments, invoices, payment methods, and refunds.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent β or use 1-click editor setup below.
We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag β we're steadily working through the catalog.
π‘ Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
An LLM-friendly Model Context Protocol server for the MyFatoorah API. It lets Claude, VS Code, Cursor, and other MCP hosts discover payment methods, create payment links, verify payments, inspect invoices, and manage refunds through focused tools.
This is an independent community project, not an official MyFatoorah product. Test in the sandbox before using a live account.
For step-by-step host setup, Inspector testing, agent prompts, payment verification, refunds, and troubleshooting, see the usage guide.
Set MYFATOORAH_API_TOKEN in the MCP host's environment. The server does not automatically load .env; the VS Code debug configuration does.
| Variable | Required | Default | Description |
|---|---|---|---|
MYFATOORAH_API_TOKEN | Yes, when calling the API | β | Bearer token. Never expose it to an agent prompt. |
MYFATOORAH_ENVIRONMENT | No | test | test, kuwait, uae, saudi_arabia, qatar, or egypt |
MYFATOORAH_BASE_URL | No | Environment URL | HTTPS override for a supported MyFatoorah deployment or test proxy |
MYFATOORAH_TIMEOUT_MS | No | 30000 | Request timeout from 1 to 300000 ms |
Kuwait also covers the shared Bahrain, Jordan, and Oman API origin. Multi-country accounts use a separate token for each country.
Use an absolute path in host configurations. Replace /absolute/path/to/myfatoorah-mcp and the token placeholder locally.
Add this server to Claude Desktop's MCP configuration:
Restart Claude Desktop after saving the configuration.
Project-scoped configuration can use .mcp.json (keep it uncommitted if it contains a token):
The included .vscode/mcp.json launches the built server and securely prompts for a token. Build once, open the MCP servers view, then start myfatoorah. The token is not stored in the repository.
Use the same command, args, and env values as the Claude Desktop example. MCP protocol messages use stdin/stdout; server diagnostics must use stderr.
After publishing to npm, hosts can instead launch it with npx -y myfatoorah-mcp.
| Tool | Effect | Purpose |
|---|---|---|
myfatoorah_get_payment_methods | Read-only | Lists enabled methods and their ApiName values |
myfatoorah_create_payment | Creates data | Creates a hosted checkout or invoice link with POST /v3/payments |
myfatoorah_get_payment | Read-only | Gets authoritative payment details by PaymentId |
myfatoorah_get_invoice | Read-only | Gets an invoice by InvoiceId or external identifier |
myfatoorah_create_refund | Destructive | Creates a full or partial refund; requires confirm: true |
myfatoorah_get_refund | Read-only | Gets refund details by RefundId |
myfatoorah_api_request | Varies | Restricted escape hatch for relative /v2/ or /v3/ paths; mutations require confirmation |
The server also exposes:
myfatoorah://configuration: environment, base URL, timeout, and whether a token is configuredβnever the token itself.create-payment-safely: a reusable guided payment-link workflow.Successful tools return a concise text summary plus machine-readable structuredContent containing the MyFatoorah response.
myfatoorah://configuration and confirm test versus live.myfatoorah_get_payment_methods and use its ApiName.myfatoorah_create_payment and give the customer its PaymentURL.myfatoorah_get_payment with the returned PaymentId. A redirect is not proof of payment; require invoice status PAID and transaction status SUCCESS.Refunds move money in live mode. Obtain explicit user approval for the exact PaymentId and amount before passing confirm: true.
npm run inspect starts the official MCP Inspector against the compiled stdio server. VS Code also includes build/test tasks and a debug configuration.
Tests mock every MyFatoorah request; they do not make network calls or require a token.
/v2/ and /v3/ to prevent credential exfiltration.The focused tools use MyFatoorah's documented v3 routes as of August 2026:
GET /v3/payment-methodsPOST /v3/paymentsGET /v3/payments/{paymentId}GET /v3/invoices/{invoiceId}GET /v3/invoices/externalIdentifier/{externalIdentifier}POST /v3/refundsGET /v3/refunds/{refundId}References:
MIT
No reviews yet β be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/myfatoorah-mcp)<a href="https://allmcps.com/mcp/myfatoorah-mcp"><img src="https://allmcps.com/api/badge/myfatoorah-mcp?style=directory" alt="MyFatoorah MCP on AllMCPs" /></a>