Ryft MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RYFT_BASE_URL | No | The Ryft API base URL. Defaults to https://sandbox-api.ryftpay.com/v1 | https://sandbox-api.ryftpay.com/v1 |
| RYFT_ACCOUNT_ID | No | Default Account header for account-scoped operations | |
| RYFT_SECRET_KEY | Yes | Your Ryft secret key. The server will exit immediately if this is missing. |
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 |
|---|---|
| customers.createC | Create a Ryft customer. |
| customers.getB | Get a Ryft customer by id. |
| customers.listC | List Ryft customers. |
| customers.updateC | Update a Ryft customer. |
| customers.deleteC | Delete a Ryft customer. |
| customers.listPaymentMethodsC | List stored payment methods for a Ryft customer. |
| paymentSessions.createD | Create a Ryft payment session. |
| paymentSessions.getC | Get a Ryft payment session by id. |
| paymentSessions.listD | List Ryft payment sessions. |
| paymentSessions.updateC | Update a Ryft payment session. |
| paymentSessions.refundC | Refund a Ryft payment session. |
| paymentSessions.captureD | Capture a manually captured Ryft payment session. |
| paymentSessions.voidC | Void a Ryft payment session. |
| paymentSessions.continuePaymentC | Continue a Ryft payment after a required action such as 3DS. |
| paymentSessions.listTransactionsC | List transactions for a payment session. |
| paymentSessions.getTransactionC | Get a payment session transaction by id. |
| subscriptions.createC | Create a Ryft subscription. |
| subscriptions.getC | Get a Ryft subscription by id. |
| subscriptions.listD | List Ryft subscriptions. |
| subscriptions.updateD | Update a Ryft subscription. |
| subscriptions.cancelC | Cancel a Ryft subscription using the correct lifecycle endpoint. |
| subscriptions.getPaymentSessionsC | List payment sessions for a Ryft subscription. |
| files.createC | Upload a file to Ryft. |
| files.getC | Get a file by id. |
| files.listC | List files. |
| accounts.createD | Create a Ryft account. |
| accounts.getC | Get a Ryft account by id. |
| accounts.updateC | Update a Ryft account by id. |
| accounts.verifyC | Request account verification for a Ryft account. |
| accounts.createAuthorizationLinkC | Create a Ryft account authorization link for a registered account email. |
| accountLinks.generateTemporaryC | Generate a temporary Ryft account link for a hosted sub-account. |
| paymentMethods.getC | Get a Ryft payment method by id. |
| paymentMethods.updateC | Update a Ryft payment method billing address. |
| paymentMethods.deleteC | Delete a Ryft payment method. |
| webhooks.createC | Create a Ryft webhook endpoint. |
| webhooks.listB | List Ryft webhook endpoints. |
| webhooks.getC | Get a Ryft webhook by id. |
| webhooks.updateC | Update a Ryft webhook endpoint. |
| webhooks.deleteC | Delete a Ryft webhook endpoint. |
| persons.createC | Create a Ryft person for a business account. |
| persons.listC | List Ryft persons for an account. |
| persons.getC | Get a Ryft person by id. |
| persons.updateD | Update a Ryft person. |
| persons.deleteC | Delete a Ryft person. |
| payoutMethods.createC | Create a Ryft payout method for an account. |
| payoutMethods.listC | List payout methods for a Ryft account. |
| payoutMethods.getC | Get a Ryft payout method by id. |
| payoutMethods.updateC | Update a Ryft payout method. |
| payoutMethods.deleteC | Delete a Ryft payout method. |
| payouts.createC | Create a Ryft payout for an account. |
| payouts.listC | List Ryft payouts for an account. |
| payouts.getC | Get a Ryft payout by id. |
| transfers.createD | Create a Ryft transfer. |
| transfers.listC | List Ryft transfers. |
| transfers.getB | Get a Ryft transfer by id. |
| platformFees.listC | List Ryft platform fees. |
| platformFees.getC | Get a Ryft platform fee by id. |
| platformFees.getRefundsC | List refunds for a Ryft platform fee. |
| events.listD | List Ryft events. |
| events.getC | Get a Ryft event by id. |
| disputes.listC | List Ryft disputes. |
| disputes.getC | Get a Ryft dispute by id. |
| disputes.acceptC | Accept a Ryft dispute. |
| disputes.challengeC | Challenge a Ryft dispute. |
| disputes.addEvidenceC | Add evidence to a Ryft dispute. |
| disputes.deleteEvidenceC | Delete evidence from a Ryft dispute. |
| balances.listC | List Ryft balances for a currency. |
| balanceTransactions.listC | List Ryft balance transactions. |
| ryft.healthA | Show the Ryft MCP server configuration state without revealing secrets. |
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 69 tools
Every tool has a clearly distinct purpose with no ambiguity. Tools are organized by resource type (accounts, customers, disputes, etc.) with specific CRUD operations, making it easy to distinguish between them. The naming convention clearly indicates both the resource and action, preventing misselection.
The naming follows a perfectly consistent pattern throughout: resource.action (e.g., accounts.create, customers.get, disputes.list). All tools use lowercase with dot notation separating resource and verb, creating a predictable and readable structure. There are no deviations in naming style.
With 69 tools, the count is excessive for most agent workflows and feels heavy for the payment processing domain. While the domain is comprehensive, this many tools creates cognitive load and may overwhelm agents. A more focused subset would be more appropriate for typical use cases.
The tool surface provides complete CRUD/lifecycle coverage across all major payment processing domains: accounts, customers, payments, disputes, subscriptions, transfers, and webhooks. Every resource type has create, get, update, and list operations where applicable, with no obvious gaps in functionality.