Centrapay MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CENTRAPAY_API_KEY | Yes | API key for Centrapay authentication |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_payment_requestB | Create a Centrapay payment request under a merchant config. Returns a payment URL and request id. |
| get_payment_statusA | Get the current status of a Centrapay payment request by id. |
| void_payment_requestB | Void (cancel) an active Centrapay payment request. |
| list_payment_requestsA | List payment requests matching an externalRef for a merchant account (Centrapay has no flat list-all). |
| pay_payment_requestA | Settle a payment request in the sandbox. Requires an assetType and asset reference — used to test webhook/settlement flows. |
| create_refundA | Refund a paid payment request. amount is in MINOR units (cents): 2500 = $25.00, must not exceed the original. Requires an idempotencyKey — a refund moves money irreversibly, so a retry without one would double-refund. |
| list_merchantsB | List merchants visible to the API key. |
| get_merchantA | Get details for a Centrapay merchant by id. |
| create_merchantB | Create a merchant under an account. |
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 9 tools
Each tool targets a distinct resource (merchant or payment request) and action (create, get, list, pay, void, refund). No overlap between merchant and payment operations, and payment operations are clearly differentiated by action.
All tools follow a consistent verb_noun pattern with underscores (e.g., create_merchant, get_payment_status, void_payment_request). No mixing of styles or ambiguous names.
9 tools is well-scoped for a payment/merchant server covering core CRUD and lifecycle operations. Not excessive nor insufficient for the domain.
The tool set covers merchant management (create, get, list) and full payment lifecycle (create, status, list, pay, void, refund). No obvious gaps for the intended use case.