For Iaptic MCP Server

Model Context Protocol server for interacting with iaptic

Local serverstdio

What is the For Iaptic MCP server?

Connect For Iaptic to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Model Context Protocol server for interacting with iaptic. The for iaptic mcp server is what makes that connection.

What the server does

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.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • Customers — The Customers tool exposed by this server
  • Purchases — The Purchases tool exposed by this server
  • Transactions — The Transactions tool exposed by this server
  • Statistics — The Statistics tool exposed by this server
  • Events — The Events tool exposed by this server
  • Stripe — The Stripe tool exposed by this server

Credentials and setup notes

Configuration is passed through the environment: YOUR_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

  • Node.js >= 18 - An Iaptic account with API credentials

Installation

Installation goes through your MCP client rather than a global install: point it at @smithery/cli on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

Where it fits

This sits in the payments and commerce group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. For Iaptic's toolset — Customers, Purchases, Transactions and 3 more — is a fair guide to whether it matches your workflow. It is maintained by iaptic; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against For Iaptic's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
CustomersThe Customers tool exposed by this server.
PurchasesThe Purchases tool exposed by this server.
TransactionsThe Transactions tool exposed by this server.
StatisticsThe Statistics tool exposed by this server.
EventsThe Events tool exposed by this server.
StripeThe Stripe tool exposed by this server.

How to install the For Iaptic MCP server

{
  "mcpServers": {
    "server-iaptic": {
      "command": "npx",
      "args": ["-y", "@smithery/cli"],
      "env": {
        "YOUR_API_KEY": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

  • Node.js >= 18 - An Iaptic account with API credentials
VariableDescriptionRequired
YOUR_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use For Iaptic to Customers.
  • Use For Iaptic to Purchases.
  • Use For Iaptic to Transactions.

Frequently asked questions

Node.js >= 18 and an Iaptic account with API credentials.