MCP server `@watenga/mcp`

A Model Context Protocol server: your AI assistant (Claude, Cursor, VS Code and other MCP clients) works with your Watenga account through the API, with your own key.

Your key stays on your machine

The server runs locally over stdio and reads the key from the environment. The key is sent only to the Watenga API and never appears in what the assistant sees. Test keys work by default; a live key needs WATENGA_MCP_ALLOW_LIVE=1. A refund needs your confirmation: the tool refuses without confirm: true.

Install

Claude Code:

bash

claude mcp add watenga --env WATENGA_API_KEY=sk_test_... -- npx -y @watenga/mcp

Claude Desktop (claude_desktop_config.json), Cursor (.cursor/mcp.json) or VS Code (.vscode/mcp.json, where the top-level key is servers):

json

{
  "mcpServers": {
    "watenga": {
      "command": "npx",
      "args": ["-y", "@watenga/mcp"],
      "env": { "WATENGA_API_KEY": "sk_test_..." }
    }
  }
}

Node 20 or later. Until the package is on npm, run node packages/watenga-mcp/bin/watenga-mcp.js from a checkout of the Watenga repository instead of npx -y @watenga/mcp. Optional: WATENGA_API_URL.

Tools and the scopes they need

With a secret key every tool is available. With a restricted key the server reads the key's own scopes (GET /v1/account/api-key) and lists and runs only the tools they allow; a refused tool sends nothing to the API, which enforces the same scopes.

Tool	What it does	A restricted key needs
`list_payment_links`	Payment links, newest first	payment_links read
`create_payment_link`	A new link, with a saved design or its own appearance	payment_links write
`list_transactions`	Payments and refunds	transactions read
`get_transaction`	One payment	transactions read
`refund_transaction`	A full or partial refund, after you confirm	refunds write (and the app’s Refunds switch on)
`list_invoices`	Invoices by status	invoices read
`get_checkout_design`	Your Checkout Studio design, saved designs, product defaults	a secret key
`validate_checkout_design`	Checks an appearance (schema and readable contrast); saves nothing	a secret key
`propose_checkout_design`	Saves an appearance as a new “(proposed)” design for you to review in Checkout Studio; never changes the draft or the live checkout	a secret key
`list_webhook_deliveries`	An API app’s deliveries	a secret key
`send_test_webhook`	A test event to an app’s endpoint	a secret key
`search_api_reference`	Finds endpoints in the OpenAPI reference	nothing

Resources: watenga://api-reference/merchant (the OpenAPI document) and watenga://checkout/appearance (what a checkout appearance holds). The server asks for API version 2026-10-29, whatever version your app is pinned to; errors name the field at fault and the request id.

MCP server @watenga/mcp

Install

Tools and the scopes they need

MCP server `@watenga/mcp`