About MCP Server for Iaptic
MCP Server for Iaptic connects AI clients to Iaptic data for customer, purchase, transaction, event, and statistics queries. It is primarily read-only, with separate Stripe session tools and app credential switching.
Key features
- 01Query customers and subscriptions
- 02Browse purchases and transactions
- 03Inspect events and revenue statistics
- 04Create Stripe checkout and portal sessions
- 05Switch the active Iaptic app
Use cases
- 01Answer questions about customer accounts
- 02Review purchase and transaction history
- 03Check revenue and app statistics
- 04Provide customers with Stripe payment or portal links
MCP support
Exposes Iaptic customer, purchase, transaction, event, and statistics queries as tools for MCP clients. It also provides Stripe session and app-selection tools; most Iaptic data operations are read-only.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
17Saved tool list · updated 3w ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| limit | number | No | Maximum number of customers to return (default: 100) |
| offset | number | No | Number of customers to skip for pagination |
Details
From the project READMEMCP Server for Iaptic
A Model Context Protocol server for interacting with the Iaptic API. This server allows Claude or other AIs to interact with your Iaptic data to answer questions about your customers, purchases, transactions, and statistics.
Scope
The server is read-only with respect to your Iaptic data: tools can query customers, purchases, transactions, events and statistics, but cannot modify records, issue refunds, or change your Iaptic configuration. Three groups of tools operate outside stored data: stripe_checkout / stripe_portal are the only tools that create anything — Stripe checkout or billing-portal sessions (links your customer uses to pay or manage their subscription), never Iaptic records; stripe_purchases looks up a customer's purchases by checkout-session access token; and iaptic_switch_app / iaptic_reset_app change which app's credentials are used for subsequent queries.
Installation
Installing via Smithery
To install Iaptic for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install mcp-server-iaptic --client claude
Manual Installation
# Run directly with npx
npx mcp-server-iaptic --api-key YOUR_API_KEY --app-name YOUR_APP_NAME
# Or install globally
npm install -g mcp-server-iaptic
mcp-server-iaptic --api-key YOUR_API_KEY --app-name YOUR_APP_NAME
Usage with Claude Desktop
Add to your Claude Desktop configuration file:
{
"iaptic": {
"command": "npx",
"args": [
"mcp-server-iaptic",
"--api-key", "your-api-key-here",
"--app-name", "your-app-name-here"
]
}
}
Available Tools
Customers
customer_list: List customers with paginationcustomer_get: Get detailed customer information by IDcustomer_subscription: Get customer's active subscription statuscustomer_transactions: Get customer's transaction history
Purchases
purchase_list: List purchaseslimit: Maximum number of purchases to return (default: 100, max: 1000)offset: Number of purchases to skip for paginationstartdate: Filter purchases after this date (ISO format, e.g. 2024-01-01)enddate: Filter purchases before this date (ISO format, e.g. 2024-12-31)customerId: Filter by customer ID
purchase_get: Get purchase details by ID
Transactions
transaction_list: List transactions with pagination and date filteringlimit: Maximum number of transactions to return (default: 100, max: 1000)offset: Number of transactions to skip for paginationstartdate: Filter transactions after this date (ISO format, e.g. 2024-01-01)enddate: Filter transactions before this date (ISO format, e.g. 2024-12-31)purchaseId: Filter by purchase ID
transaction_get: Get transaction details by ID
Statistics
stats_get: Get general statistics about transactions and revenuestats_app: Get app-specific statistics
Events
event_list: List recent events with pagination and date filteringlimit: Maximum number of events to return (default: 100)offset: Number of events to skip for paginationstartdate: Filter events after this date (ISO format, e.g. 2024-01-01)enddate: Filter events before this date (ISO format, e.g. 2024-12-31)raw: Return raw JSON instead of formatted output (default: false)
event_details: Get detailed information about a specific event (validator 3.12+)eventId: The event ID to get details forreceipts: Include receipt validation details (default: false)
Stripe
stripe_prices: Get available Stripe products and pricesstripe_checkout: Create a Stripe Checkout session and return its payment linkofferId: Offer ID to purchase, as returned bystripe_pricessuccessUrl: URL to redirect the customer to after successful paymentcancelUrl: URL to redirect the customer to if they cancelapplicationUsername: User identifier in your application (optional)mode:paymentorsubscription(optional; defaults per the price type)accessToken: Access token from a previous purchase, to reuse the existing Stripe customer (optional)
stripe_portal: Create a Stripe Customer Portal session and return its URLaccessToken: Access token received when the Stripe checkout session was createdreturnUrl: URL to return the customer to after managing their subscription
stripe_purchases: Get a customer's Stripe purchases using an access tokenaccessToken: Access token received when the Stripe checkout session was created
App Management
iaptic_switch_app: Switch to a different Iaptic appappName: Name of the app to switch toapiKey: API key for the app
iaptic_reset_app: Reset to the default Iaptic appiaptic_current_app: Get information about the currently active app
Development
# Install dependencies
npm install
# Run in development mode
npm run dev
# Build for production
npm run build
# Run production build
npm start
Requirements
- Node.js >= 18
- An Iaptic account with API credentials
License
MIT
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.