MCP server
https://mcp.voltpay.space/mcp| Tool | Does | Needs a key |
|---|---|---|
search |
Finds any operation, field, error code or guide, with tested Callback code. | No |
execute |
Runs up to five API calls in order, with your API Key. | Yes |
Before you connect
Section titled “Before you connect”- Create a test API Key (
gw_test_…) with no IP allowlist. Calls reach the API from the MCP server, not from your machine. - Put it in your environment:
export VOLTPAY_API_KEY="gw_test_…"
Connect
Section titled “Connect”claude mcp add --transport http voltpay https://mcp.voltpay.space/mcp --header "Authorization: Bearer $VOLTPAY_API_KEY"{ "mcpServers": { "voltpay": { "url": "https://mcp.voltpay.space/mcp", "headers": { "Authorization": "Bearer ${env:VOLTPAY_API_KEY}" } } }}{ "inputs": [{ "type": "promptString", "id": "voltpay-api-key", "description": "VoltPay API Key", "password": true }], "servers": { "voltpay": { "type": "http", "url": "https://mcp.voltpay.space/mcp", "headers": { "Authorization": "Bearer ${input:voltpay-api-key}" } } }}[mcp_servers.voltpay]url = "https://mcp.voltpay.space/mcp"bearer_token_env_var = "VOLTPAY_API_KEY"{ "mcpServers": { "voltpay": { "command": "npx", "args": ["-y", "mcp-remote", "https://mcp.voltpay.space/mcp", "--header", "Authorization:${VOLTPAY_AUTH}"], "env": { "VOLTPAY_AUTH": "Bearer gw_test_YOUR_KEY" } } }}A custom connector under Settings, Connectors also works, for search only: it sends no key.
gemini mcp add --transport http --header "Authorization: Bearer $VOLTPAY_API_KEY" voltpay https://mcp.voltpay.space/mcp{ "mcpServers": { "voltpay": { "serverUrl": "https://mcp.voltpay.space/mcp", "headers": { "Authorization": "Bearer gw_test_YOUR_KEY" } } }}{ "mcp": { "servers": { "voltpay": { "type": "remote", "url": "https://mcp.voltpay.space/mcp", "oauth": false, "headers": { "Authorization": "Bearer {env:VOLTPAY_API_KEY}" } } } }}Any other client works if it speaks Streamable HTTP and can send a header. Choose HTTP, not SSE. The server speaks MCP revision 2026-07-28 and still answers older clients.
What execute runs
Section titled “What execute runs”A plan of up to five calls. A later call can use an earlier answer, such as {0.id}, and fields trims what comes back.
{ "calls": [ { "method": "POST", "path": "/checkouts", "body": { "reference": "order-1234", "amount": "5.00" } }, { "method": "GET", "path": "/checkouts/{0.id}", "fields": ["id", "status", "url"] } ]}It reaches only the public API: Checkouts, Payments, Pairs and your balance.
Safety
Section titled “Safety”- Nothing here can move money. There is no refund, payout or transfer to call.
- Your API Key is never stored or logged. It goes only to
api.voltpay.space. - Use a
gw_test_key while you build. Agw_live_key opens real Checkouts, each with a Hold. - A repeated
POSTis safe. Each carries an Idempotency-Key made from the call. - Your own server calls the API directly, never through the MCP server. Read what the agent wrote before you ship it.
Prompts to try
Section titled “Prompts to try”- “Search VoltPay, then explain how to integrate it into this backend.”
- “Write the Callback handler: verify
Gateway-Signature, credit each Payment once, and test it with VoltPay’s signature vector.” - “With my test key, create a 5.00 Checkout, show me its link, then cancel it.”
When something does not work
Section titled “When something does not work”| You see | Do |
|---|---|
MCP_MISSING_API_KEY |
Add the Authorization header and restart the client. |
MCP_MALFORMED_API_KEY |
Check for a missing Bearer, or a variable that is not set. |
INVALID_API_KEY |
Check the key is not revoked and has no IP allowlist. |
MCP_INVALID_CALL |
Nothing was sent. Ask the agent to search first. |
| HTTP 403 on connecting | The client is a web page. Use a desktop or command-line client. |