Tegro.money MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TEGRO_API_KEY | No | API KEY (HMAC‑SHA256) required for REST tools (create/get order, list orders, get balance) | |
| TEGRO_SHOP_ID | Yes | Shop ID (public) required for all tools | |
| TEGRO_BASE_URL | No | Base URL for Tegro.money API (optional, for staging) | |
| TEGRO_SECRET_KEY | No | Secret KEY (MD5) required for creating payment links |
Instructions
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.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| tegro_create_payment_linkA | Build a ready-to-open payment URL (SCI form) for a given amount and currency. Needs TEGRO_SECRET_KEY. No money moves until the customer pays on the page. |
| tegro_create_orderC | Create a payment order via the REST API and get back its details/URL. Needs TEGRO_API_KEY. Collects a payment into the shop. |
| tegro_get_orderA | Look up one order by your orderId or the Tegro paymentId. Needs TEGRO_API_KEY. |
| tegro_list_ordersC | List the shop's orders. Needs TEGRO_API_KEY. |
| tegro_get_balanceA | Read the shop's available balance. Needs TEGRO_API_KEY. |
| tegro_list_shopsA | List the shops on the account. Needs TEGRO_API_KEY. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: creating orders, generating payment links, checking balance, and querying orders/shops. No two tools overlap in functionality.
All tools follow a consistent 'tegro_verb_noun' snake_case pattern, using standard verbs like create, get, list. No mixing of styles.
With 6 tools, the set is well-scoped for a payment system, covering order creation, payment links, balance, and listings without being excessive or too thin.
The tool surface covers core payment workflows (create, retrieve, list) but lacks refund/cancel capabilities, which are minor gaps but not severe for basic usage.