Iaptic MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| IAPTIC_API_KEY | Yes | Your API key for accessing the Iaptic server. | |
| IAPTIC_APP_NAME | Yes | Your application name for the Iaptic server. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| customer_listA | List customers from your Iaptic account.
|
| customer_getB | Get detailed information about a specific customer.
|
| customer_add_purchaseA | Manually associate a customer with a purchase.
|
| customer_subscriptionA | Get customer's subscription status.
|
| customer_transactionsA | Get customer's transaction history.
|
| purchase_listA | List purchases from your Iaptic account.
|
| purchase_getA | Get detailed information about a specific purchase.
|
| transaction_listA | List financial transactions from your Iaptic account.
|
| transaction_getA | Get detailed information about a specific transaction.
|
| stats_getA | Get general transactions, revenue and usage statistics from your Iaptic account.
|
| stats_appB | Get statistics specific to your application.
|
| stripe_pricesA | Get available Stripe products and prices.
|
| event_listA | List recent events from your Iaptic account.
|
| event_detailsA | Get detailed information about a specific event.
|
| iaptic_switch_appA | Switch to a different Iaptic app.
|
| iaptic_reset_appA | Reset to the default Iaptic app.
|
| iaptic_current_appA | Get information about the currently active Iaptic app.
|
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 17 tools
Each tool targets a distinct resource (customer, purchase, transaction, event, stats, app, stripe) with clear actions (list, get, add, details). No overlapping purposes; agents can easily distinguish.
Tools consistently use snake_case with a resource-first pattern (e.g., customer_list, purchase_get). However, some names like 'customer_subscription' and 'event_details' use nouns instead of verbs, causing minor inconsistency.
17 tools cover the Iaptic domain comprehensively without being excessive. Each tool has a clear purpose, and the count is well-balanced for managing in-app purchases and subscriptions.
The tool surface covers core operations (list, get, add) for customers, purchases, transactions, events, and stats. Missing create/update for customers and purchases, but these are typically handled client-side, so no major gap.