InventPay MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| INVENTPAY_API_KEY | Yes | Your merchant API key (pk_live_...). Used for all operations: payments, invoices, store, products, orders, balances. | |
| INVENTPAY_BASE_URL | No | API base URL (default: https://api.inventpay.io) | https://api.inventpay.io |
| INVENTPAY_WITHDRAWAL_KEY | No | Withdrawal-only key (wk_live_...). Used exclusively for withdrawing funds to external wallets. Cannot be used for any other operation. |
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 |
|---|---|
| create_paymentB | Create a crypto payment. Returns a unique wallet address, QR code, and invoice URL for the customer to pay. |
| create_invoiceA | Create a multi-currency invoice. The customer can choose which cryptocurrency to pay with. Returns an invoice URL. |
| get_payment_statusA | Check the current status of a payment or invoice. Returns status, amount, confirmations, and transaction details. |
| get_balancesA | Get all cryptocurrency balances for your merchant account. Shows available, pending, total earned, and total withdrawn for each currency. |
| create_withdrawalA | Create a withdrawal request to send funds to an external wallet address. Requires INVENTPAY_WITHDRAWAL_KEY to be configured (a separate withdrawal API key generated from Dashboard → Settings). |
| get_withdrawalA | Check the status of a withdrawal request. Returns status, amount, transaction hash, and processing details. |
| create_storeB | Create a new merchant storefront. Each merchant gets one store with a unique URL slug. Customers can browse and purchase digital products with crypto. |
| get_storeA | Get your store details including name, slug, URL, product count, and order count. |
| update_storeA | Update your store details. Only provided fields are changed. |
| create_productA | Add a digital product to your store. Products are priced in USDT and auto-converted to crypto at checkout. Attach digitalContent for automatic delivery after payment. |
| list_productsA | List all products in your store with optional search and pagination. |
| update_productA | Update a product in your store. Only provided fields are changed. Updating the name regenerates the slug. |
| delete_productA | Deactivate a product from your store. Products with existing orders are soft-deleted (hidden, not removed). |
| add_product_keysA | Upload unique keys/codes to a product's key pool. Each customer gets one unique key on purchase (FIFO). Use this for license keys, activation codes, gift cards, etc. |
| list_product_keysA | List keys in a product's key pool with status filter and pagination. |
| get_key_pool_statsA | Get key pool statistics for a product: available, assigned, revoked, and total counts. |
| list_ordersA | List all orders for your store with optional status filter and pagination. |
| get_orderA | Get full details of a specific order including items, payment status, customer info, and timestamps. |
| update_order_statusA | Update the fulfillment status of an order. Valid transitions: PAID→PROCESSING, PROCESSING→SHIPPED/COMPLETED, SHIPPED→COMPLETED, COMPLETED→REFUNDED. Digital orders auto-transition to COMPLETED. |
| get_store_analyticsA | Get store analytics: total orders, revenue breakdown by status, product count, and recent order activity. |
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 20 tools
Most tools target distinct resources and actions. Slight overlap exists between get_store and get_store_analytics (both show order/product counts) and between create_payment and create_invoice, but descriptions clarify their different use cases.
All tool names follow a consistent verb_noun pattern with snake_case: get, create, update, delete, list, add. Resources are singular for single-item operations and plural for list operations, with only minor naming variance like get_key_pool_stats.
With 20 tools, the count is higher than the ideal 3-15 range but appropriate for the broad merchant platform scope covering stores, products, keys, payments, withdrawals, orders, and analytics. Each tool has a distinct purpose, so it does not feel bloated.
The tool surface covers core lifecycle operations for stores, products, keys, payments, withdrawals, and orders. Minor gaps exist (e.g., no store deletion, no key revocation, no payment cancellation), but these are typically not required for merchant operations and can be worked around.