agentbank-merchant-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGENTBANK_API_URL | No | Local dev only: URL to point at a local API (default: https://mcp.curless.ai) | |
| AGENTBANK_MERCHANT_ID | Yes | Your Curless merchant id, e.g. 888888 | |
| AGENTBANK_MERCHANT_TOKEN | Yes | Your Curless API key (issued by Curless at onboarding) |
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_ordersA | List this merchant's orders (what agents have paid you), newest first. Filter by status / protocol / currency / date. |
| get_summaryA | This merchant's order roll-up: count + gross by currency + breakdowns by protocol/status. Same status/protocol/currency/date filters as list_orders. |
| get_balanceB | This merchant's live Curless wallet balance, per currency. |
| get_orderA | One order's full detail — line items + the card it was paid with. Pass the order id from list_orders. |
| list_refund_requestsA | Buyers' refund requests on your orders. Default lists status=requested (the queue awaiting your decision); pass status to filter, or status=all for the full history. |
| approve_refundA | Approve a refund request → forwarded to Curless; the order refunds once Curless confirms. Pass the refund request id (rfr_…). |
| reject_refundA | Reject a refund request (optional note). Pass the refund request id (rfr_…). |
| refund_orderA | Directly refund one of your orders (no buyer request needed). Pass the order id (ord_…); optional partial |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Merchant card |
TDQS
Scored across 8 tools
Each tool has a distinct purpose: balance, single order, refund requests, approving/rejecting refunds, direct refunds, listing orders, and summary. No overlap; even the two refund actions are clearly separated by whether a buyer request exists.
All tools follow a consistent verb_noun pattern in snake_case: get_balance, get_order, list_refund_requests, approve_refund, reject_refund, refund_order, list_orders, get_summary. The verbs (get, list, approve, reject, refund) are predictably used.
With 8 tools, the server strikes an ideal balance: comprehensive enough to cover the merchant payment workflow (balance, orders, refunds, summary) without unnecessary bloat or missing essentials.
Core operations are covered: viewing balance, listing and getting orders, handling refunds (both direct and via requests), and a summary. Minor gap: no explicit order cancellation or update, but refunds effectively void orders. Still, a cancel_order tool could be missing.