Remote MCP for payments
zahls.ch exposes the REST API as MCP tools. Connect Cursor, Claude or agent frameworks — create payment links, trigger invoices, check status. No custom backend in between.
Connected in minutes
One endpoint and two headers. Get your API key and instance name in the dashboard under API and integrations.
- Endpoint
- https://www.zahls.ch/mcp
- Headers
- X-API-KEY, X-Instance
Example (Cursor / MCP JSON)
{
"mcpServers": {
"zahls-ch": {
"url": "https://www.zahls.ch/mcp",
"headers": {
"X-API-KEY": "DEIN_API_SCHLUESSEL",
"X-Instance": "deine-instanz"
}
}
}
}Replace the placeholders, reload the client — done.
What the tools can do
Payment links
Create, share and manage links — one-off or for subscriptions.
Invoices & donations
Create formal invoices and donation forms straight from the agent.
Status & refunds
Query transactions and initiate refunds.
Works with your client
Any client with remote MCP (HTTP) and custom request headers.
Cursor
Project or user MCP config — tools show up in the tool list.
Claude
Remote MCP clients with custom headers use the same endpoint.
OpenClaw
Open-source agent gateway: register zahls.ch as an MCP server.
Hermes
Hermes Agent with a native MCP client — tools as first-class capabilities.
Typical use cases
Create and send a payment link in a support chat
Generate an invoice or donation link for a campaign
Check payment status before the agent starts the next action
Create a subscription or prepare a refund
MCP + webhooks
MCP fits synchronous actions (create, query). For async events when a payment arrives, still set up webhooks — they complement each other.
Webhooks in helpUse it safely
- Use a dedicated API key for the MCP client — rotate if needed
- Never put keys in prompts or public repos
- Constrain critical actions (high amounts, refunds) in the prompt
Ready for your first MCP call?
Create an account, generate an API key, connect your client — no setup fees.