Get the FREE Ultimate OpenClaw Setup Guide →

mcp -iaptic

Model Context Protocol server for interacting with iaptic

Installation
Run this command in your terminal to add the MCP server to Claude Code.
Run in terminal:
Command
claude mcp add --transport stdio iaptic-mcp-server-iaptic npx mcp-server-iaptic --api-key YOUR_API_KEY --app-name YOUR_APP_NAME

How to use

This MCP server provides a bridge to the Iaptic API, enabling Claude or other AI assistants to query and analyze customer data, purchases, transactions, and statistics hosted in Iaptic. The server exposes a suite of tools grouped under Customers, Purchases, Transactions, Statistics, Events, Stripe, and App Management, allowing you to list, fetch, or filter data (for example by date ranges, customer IDs, or event IDs) and to interact with app configurations. To connect, configure your client (e.g., Claude Desktop) to invoke the server via the provided command, passing your Iaptic API key and app name so the server can authenticate requests to Iaptic on your behalf.

How to install

Prerequisites:

  • Node.js v18 or newer
  • npm or npx available in your shell
  • An Iaptic account with API credentials

Installation steps:

  1. Ensure Node.js is installed. You can verify with: node -v npm -v
  2. Install and run the MCP server using npx (no global install required): npx mcp-server-iaptic --api-key YOUR_API_KEY --app-name YOUR_APP_NAME
  3. (Optional) If you prefer a local installation, you can install globally and run: npm install -g mcp-server-iaptic mcp-server-iaptic --api-key YOUR_API_KEY --app-name YOUR_APP_NAME
  4. For Claude Desktop configuration, reference the server with the command and arguments: { "iaptic": { "command": "npx", "args": [ "mcp-server-iaptic", "--api-key", "your-api-key-here", "--app-name", "your-app-name-here" ] } }

Additional notes

Tips and notes:

  • Replace YOUR_API_KEY and YOUR_APP_NAME with your actual Iaptic API key and desired app name.
  • The server supports pagination and date filtering for list endpoints (e.g., purchases, transactions, events) and can return detailed records via individual get endpoints.
  • Ensure your environment variables are set securely and avoid hardcoding credentials in shared configurations.
  • If you encounter authentication errors, verify that the API key has the necessary read/write scopes for the Iaptic data you intend to access.
  • The command is designed for runtime usage via npx; if you need a persistent service, consider wrapping the command in a systemd or similar daemon manager on your host.
  • The available tools mirror the Iaptic data model: Customers, Purchases, Transactions, Statistics, Events, Stripe, and App Management.
  • Check Iaptic API rate limits and design queries to respect them to avoid throttling.

Related MCP Servers

Sponsor this space

Reach thousands of developers