Iaptic

Iaptic MCP Server

Model Context Protocol server for interacting with iaptic.

What is an MCP Server?

MCP Info

Image Building Info

Available Tools (17)

Tools Details

Tool: customer_add_purchase

Manually associate a customer with a purchase.

• Links a purchase to a specific customer
• Takes priority over receipt validation links
• Useful for manual purchase management
• Purchase format should be "platform:purchaseId", for example apple:123109519983
• Required: customerId and purchaseId

Tool: customer_get

Get detailed information about a specific customer.

• Returns complete customer profile including:
  • Application username
  • Purchase history
  • Active and expired subscriptions
  • Last purchase details
  • Subscription renewal status
  • Trial and introductory period information
• Required: customerId parameter

Tool: customer_list

List customers from your Iaptic account.

• Returns a paginated list of customers with their purchase status
• Each customer includes:
  • Application username
  • Last purchase information
  • Subscription status (active/lapsed)
  • Renewal intent
  • Trial/introductory period status
• Use limit and offset for pagination (default: 100 customers per page)
• Results are ordered by creation date (newest first)

Tool: customer_subscription

Get customer's subscription status.

• Returns active subscription details if any
• Includes:
  • Subscription status and expiry
  • Payment and renewal information
  • Trial/introductory period status
• Simpler alternative to customer_get for subscription-only apps

Tool: customer_transactions

Get customer's transaction history.

• Returns list of all transactions
• Includes:
  • Payment details
  • Transaction status
  • Associated purchases
  • Timestamps

Tool: event_details

Get detailed information about a specific event.

• Returns both analyzed data (context, content) and raw event data (request, response, external API calls)
• Raw data includes the HTTP request/response and any external requests made (e.g. Apple/Google/Stripe API calls)
• Sensitive fields are removed and large payloads are trimmed
• Optionally includes receipt validation details
• Use an eventId from event_list results
• Requires validator version 3.12+

Tool: event_list

List recent events from your Iaptic account.

• Returns a paginated list of system events
• Events include:
  • Receipt validations
  • Platform notifications (Apple/Google/etc)
  • Webhook deliveries
  • Purchase status changes
  • Subscription renewals
• Use limit and offset for pagination
• Results ordered by date (newest first)

Tool: iaptic_current_app

Get information about the currently active Iaptic app.

• Returns the current app name
• Indicates whether using default or custom credentials

Tool: iaptic_reset_app

Reset to the default Iaptic app.

• Reverts to the original app credentials provided during server initialization
• All subsequent API calls will use the default app name and API key
• Use this after using iaptic_switch_app to return to the default app

Tool: iaptic_switch_app

Switch to a different Iaptic app.

• Allows temporarily using a different app's credentials
• All subsequent API calls will use the new app name and API key
• Useful for managing multiple apps in the same session
• Required: appName parameter (apiKey required only if not using master key)

Tool: purchase_get

Get detailed information about a specific purchase.

• Returns complete purchase details including:
  • Product information
  • Purchase status
  • Associated transactions
  • Customer information
  • Subscription details (if applicable)
• Required: purchaseId parameter

Tool: purchase_list

List purchases from your Iaptic account.

• Returns a paginated list of purchases
• Use limit and offset for pagination (default: 100 per page)
• Filter by date range using startdate and enddate (ISO format)
• Filter by customerId to see purchases from a specific customer
• Results include purchase status, product info, and transaction details
• Results are ordered by purchase date (newest first)

Tool: stats_app

Get statistics specific to your application.

• Returns app-specific metrics including:
  • App revenue and growth
  • Active subscriptions for this app
  • Customer metrics for this app
  • Product performance statistics
  • Transaction metrics
• Uses the app name provided during server initialization

Tool: stats_get

Get general transactions, revenue and usage statistics from your Iaptic account.

• Returns aggregated metrics including:
  • Total revenue
  • Number of active subscriptions
  • Customer growth metrics
  • Transaction success rates
  • Revenue by product type
• Data is aggregated across all your applications

Tool: stripe_prices

Get available Stripe products and prices.

• Returns list of products with their associated prices
• Each product includes:
  • Product ID and display name
  • Description and metadata
  • Available pricing offers
  • Subscription terms if applicable
• Results are cached for 5 minutes

Tool: transaction_get

Get detailed information about a specific transaction.

• Returns complete transaction details including:
  • Transaction status
  • Amount and currency
  • Payment method details
  • Associated purchase information
  • Customer information
  • Timestamps and audit data
• Required: transactionId parameter

Tool: transaction_list

List financial transactions from your Iaptic account.

• Returns a paginated list of transactions
• Use limit and offset for pagination (default: 100 per page)
• Filter by date range using startdate and enddate (ISO format)
• Filter by purchaseId to see transactions for a specific purchase
• Results include transaction status, amount, currency, and payment details
• Results are ordered by transaction date (newest first)
• Important: Use date filtering to avoid retrieving too many records

Use this MCP Server

{
  "mcpServers": {
    "iaptic": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "IAPTIC_APP_NAME",
        "-e",
        "IAPTIC_API_KEY",
        "mcp/iaptic"
      ],
      "env": {
        "IAPTIC_APP_NAME": "your-app-name-here",
        "IAPTIC_API_KEY": "your-api-key-here"
      }
    }
  }
}

Why is it safer to run MCP Servers with Docker?