Schema | Centrapay MCP Server

Centrapay MCP Server

Describes the environment variables required to run the server.

Name	Required	Description	Default
`CENTRAPAY_API_KEY`	Yes	API key for Centrapay authentication

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.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`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.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/CedricConday/centrapay-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server