PayFast MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PAYFAST_PASSPHRASE | Yes | API passphrase | |
| PAYFAST_MERCHANT_ID | Yes | Merchant ID | |
| PAYFAST_MERCHANT_KEY | Yes | Merchant key |
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 |
|---|---|
| create_paymentC | Create a payment request |
| query_transactionC | Query transaction status |
| cancel_subscriptionC | Cancel a subscription |
| update_subscriptionC | Update a subscription |
| create_adhocC | Charge tokenized card (ad-hoc) |
| refund_paymentC | Refund a payment |
| get_balanceC | Get settlement balance |
| validate_signatureC | Validate a webhook signature |
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 8 tools
Each tool has a clearly distinct purpose targeting specific payment operations: subscription management (cancel, update), payment processing (create, refund, query), balance checking, ad-hoc charging, and webhook validation. No ambiguity exists between tools as they cover non-overlapping actions on different resources.
All tools follow a consistent verb_noun pattern with clear action verbs (cancel, create, get, query, refund, update, validate) paired with specific nouns (subscription, payment, balance, transaction, signature). The naming is uniform and predictable throughout the set.
With 8 tools, the server is well-scoped for a payment processing domain. Each tool earns its place by covering essential operations like payment lifecycle, subscription management, balance inquiries, and security validation without being overly sparse or bloated.
The toolset provides complete coverage for core payment workflows: payment creation, status querying, refunds, subscription management (cancel/update), balance checks, ad-hoc charges, and webhook validation. No obvious gaps exist for the inferred payment processing domain, supporting full agent interaction.