PayFast MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Optional: Logging level (debug, info, warn, error). | info |
| PAYFAST_PASSPHRASE | Yes | The passphrase generated in your PayFast security settings. | |
| PAYFAST_ENVIRONMENT | Yes | The environment to use: 'sandbox' for testing or 'production' for live transactions. | sandbox |
| PAYFAST_MERCHANT_ID | Yes | Your PayFast Merchant ID, found in Settings > Integration. | |
| PAYFAST_MERCHANT_KEY | Yes | Your PayFast Merchant Key, found in Settings > Integration. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pingA | Test connectivity to the PayFast API and verify credentials are valid |
| transaction.fetchC | Fetch details of a specific PayFast transaction by payment ID |
| transaction.historyB | Get PayFast transaction history with optional date range and pagination |
| transaction.chargeA | Process a charge on a tokenized card. This creates a real payment. Requires confirmation. |
| subscription.fetchC | Fetch details of a PayFast subscription by its token |
| subscription.pauseB | Pause a PayFast subscription for a specified number of billing cycles. This stops charges temporarily. |
| subscription.unpauseA | Resume a previously paused PayFast subscription. Billing will resume on the next cycle. |
| subscription.cancelA | Permanently cancel a PayFast subscription. This cannot be undone. |
| subscription.updateC | Update a PayFast subscription's parameters (amount, cycles, frequency, or run date) |
| subscription.adhocC | Process an ad-hoc (one-time) charge on an existing PayFast subscription |
| creditcard.fetchC | Query credit card transaction details for a specific PayFast payment |
| refund.createC | Create a refund for a PayFast transaction. This will return money to the customer's original payment method. |
| refund.queryA | Query refund availability for a transaction BEFORE creating a refund. Returns available amounts, refund methods (credit card or bank payout), and required parameters. Use this first to check if a refund is possible. |
| refund.fetchA | Fetch refund transaction history and available balance for a payment that has ALREADY been refunded. Returns 404 if no refund exists yet — use refund.query first to check availability. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 14 tools
Each tool has a clearly distinct purpose with no ambiguity. For example, refund.query checks availability, refund.create initiates a refund, and refund.fetch retrieves refund details, all serving different steps in the refund workflow. Similarly, subscription tools like pause, unpause, cancel, and update target specific lifecycle actions without overlap.
All tool names follow a consistent verb_noun pattern with dot notation for subcategories (e.g., subscription.cancel, transaction.fetch). The naming is uniform across all 14 tools, using clear verbs like fetch, create, query, and cancel, making the set highly predictable and readable.
With 14 tools, the count is well-scoped for a payment processing server, covering core operations like transactions, refunds, subscriptions, and connectivity. Each tool earns its place by addressing specific needs in the domain, such as subscription lifecycle management and transaction handling, without being excessive or sparse.
The tool surface provides complete CRUD/lifecycle coverage for the PayFast domain. It includes connectivity testing (ping), transaction processing and history (charge, fetch, history), refund management (query, create, fetch), and full subscription operations (fetch, update, pause, unpause, cancel, adhoc), with no obvious gaps that would hinder agent workflows.