Tegro.money MCP server

A Model Context Protocol server for Tegro.money — connect an AI assistant (Claude, Cursor, …) to your payment shop so it can build payment links, create invoices, and read order & balance status in plain language.

Accepts payments in RUB / USD / EUR and crypto (USDT TRC‑20 / ERC‑20 / TON, BTC…).

Safe by design. This server exposes only the collect-payment + read slice of the Tegro.money API. It never exposes payouts/withdrawals — money can only flow into your shop. You bring your own shop keys via environment variables; nothing is hardcoded and no secret ever leaves your machine.

Tools

Tool	What it does	Needs
tegro_create_payment_link	Build a ready-to-open payment URL (SCI form)	TEGRO_SECRET_KEY
tegro_create_order	Create an invoice via the REST API	TEGRO_API_KEY
tegro_get_order	Look up one order's status	TEGRO_API_KEY
tegro_list_orders	List the shop's orders	TEGRO_API_KEY
tegro_get_balance	Read the shop's balance	TEGRO_API_KEY
tegro_list_shops	List shops on the account	TEGRO_API_KEY

No payout/withdrawal tool exists — by design.

Your keys (from tegro.money/my/shop-settings/)

Env var	Tegro key	Used for
TEGRO_SHOP_ID	Shop ID (public)	everything (required)
TEGRO_SECRET_KEY	Secret KEY (MD5)	payment links
TEGRO_API_KEY	API KEY (HMAC‑SHA256)	the REST tools

You only need the keys for the tools you'll use.

Install

Claude Desktop

Add to claude_desktop_config.json:

{
  "mcpServers": {
    "tegro-money": {
      "command": "npx",
      "args": ["-y", "@tegroton/tegro-money-mcp"],
      "env": {
        "TEGRO_SHOP_ID": "your-shop-id",
        "TEGRO_SECRET_KEY": "your-secret-key",
        "TEGRO_API_KEY": "your-api-key"
      }
    }
  }
}

Cursor / Windsurf / other MCP clients

Same shape — command: npx, args: ["-y", "@tegroton/tegro-money-mcp"], and the env keys above. Then ask: "Create a 1500 RUB Tegro.money payment link for order #A‑42" or "What's my Tegro.money balance?"

How it works

• Payment links are signed locally with your Secret KEY (md5 over the sorted required fields + secret) — no network call; the customer pays on the opened Tegro page.
• REST calls are signed with your API KEY (HMAC‑SHA256 of the JSON body, sent as Authorization: Bearer …) with a strictly increasing nonce.

See the full Tegro.money API at https://tegro.money/docs/.

Security

• Keys are read from the environment, never embedded or logged.
• Read + collect-in only. No payouts. No webhook-trust surface.
• The server makes outbound HTTPS calls only to tegro.money (overridable via TEGRO_BASE_URL for staging).

Report issues privately — see SECURITY.md.

Develop

npm install
npm run build
TEGRO_SHOP_ID=… TEGRO_SECRET_KEY=… node dist/index.js   # stdio MCP server

MIT © TegroTON