open-payments-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPEN_PAYMENTS_KEY_ID | Yes | Key identifier for the private key. | |
| OPEN_PAYMENTS_SESSION_FILE | No | Path to session file for persistence (optional). | |
| OPEN_PAYMENTS_CALLBACK_PORT | No | Callback port for grants (optional). | |
| OPEN_PAYMENTS_CLIENT_ADDRESS | Yes | The client address URL for Open Payments. | |
| OPEN_PAYMENTS_MAX_DEBIT_AMOUNT | No | Maximum debit amount in smallest units (optional). | |
| OPEN_PAYMENTS_PRIVATE_KEY_PATH | Yes | Absolute path to the private key file. |
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 |
|---|---|
| get_wallet_addressA | Resolve an Open Payments wallet address and return sanitized wallet details. |
| request_grantB | Request an Open Payments grant. Outgoing payment grants are made interactive and return an approval URL. |
| continue_grantB | Continue an interactive Open Payments grant after the user approves it. |
| create_incoming_paymentA | Create an incoming payment using a finalized incoming-payment grant session. |
| get_incoming_paymentC | Read incoming payment details using a finalized incoming-payment read grant. |
| create_quoteC | Create a quote using a finalized quote grant session. |
| get_quoteB | Read quote details using a finalized quote read grant. |
| create_outgoing_paymentB | Create an outgoing payment using a finalized outgoing-payment grant session. |
| get_outgoing_paymentA | Read outgoing payment details using a finalized outgoing-payment read grant. |
| execute_peer_to_peer_paymentB | Orchestrate a full peer-to-peer payment flow: incoming payment, quote, interactive outgoing grant, and outgoing payment (blocks until approval). |
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 10 tools
Most tools map clearly to distinct resources and actions (e.g., create_incoming_payment vs. create_outgoing_payment, get_quote vs. get_outgoing_payment). The composite tool execute_peer_to_peer_payment could be confused with the individual step tools, but its description clearly frames it as an orchestration workflow.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., get_wallet_address, create_incoming_payment, request_grant). The verbs and resource names are uniform and predictable.
With 10 tools, the server is well-scoped for the Open Payments domain. It covers the essential resources (wallet address, grants, incoming payments, quotes, outgoing payments) and includes a high-level workflow tool without becoming bloated.
The tool set provides create and read coverage for all major resources and handles the grant lifecycle. However, there are no list operations (e.g., list incoming payments) or cancellation/update capabilities, which constitutes a minor gap for a full payment workflow.