Skip to main content

AI-Assisted Integration Setup

The AppCoins MCP server connects your AI assistant to live SDK documentation and integration tooling. Once configured, your assistant can read your codebase and implement a complete AppCoins billing integration — or add it alongside existing billing — using accurate, project-specific context.

📘
Your code never leaves your machine. The MCP server provides documentation and tooling to your local AI assistant. No Aptoide service receives your source code.

Connect your AI assistant​

Add one entry to your editor's MCP config, then restart.

Claude Code​

~/.claude.json (or a project-level .claude/claude.json):

{
  "mcpServers": {
    "appcoins": {
      "type": "http",
      "url": "https://ios-sdk.aptoide.com/mcp"
    }
  }
}

Codex​

~/.codex/config.toml:

[mcp_servers.appcoins]
enabled = true
url = "https://ios-sdk.aptoide.com/mcp"

Cursor​

~/.cursor/mcp.json:

{
  "mcpServers": {
    "appcoins": {
      "type": "http",
      "url": "https://ios-sdk.aptoide.com/mcp"
    }
  }
}

GitHub Copilot (VS Code)​

.vscode/mcp.json in your project root:

{
  "servers": {
    "appcoins": {
      "type": "http",
      "url": "https://ios-sdk.aptoide.com/mcp"
    }
  }
}

Run the integration​

/appcoins-integrate

Open your project in the editor before running this command — the agent scans your source files to understand your current setup.

The agent reads your existing billing code to identify your platform (Swift or Unity) and your billing setup — StoreKit 1/2, RevenueCat, Adapty, Unity IAP, a previous AppCoins SDK version, or nothing yet. For Unity projects, it checks your manifest.json to determine your Unity IAP version, since the upgrade path from v4 to v5 is different from adding AppCoins to an existing v5 project.

📘
Already on StoreKit 2 or Unity IAP v5? The AppCoins Swift SDK mirrors the StoreKit 2 API on purpose — Product, Transaction, and VerificationResult map directly to what you already have. The Unity Plugin is built as a Unity IAP v5 custom store provider — your existing events, product definitions, and confirm logic are the AppCoins integration. The agent will confirm this after reading your project, but in both cases you are closer to done than you think.

Once it has enough context, the agent asks which distribution strategy you want:

  • Single build — AppCoins sits alongside existing billing. isAvailable() routes to AppCoins on Aptoide-distributed builds; existing billing handles everything else. One binary for both App Store and Aptoide.
  • Separate builds — your main branch keeps existing billing untouched. An aptoide branch uses AppCoins as the exclusive billing path. Two binaries, no runtime check needed.
  • New app — AppCoins as the only billing path from the start.

The agent then implements the integration using both the step-by-step guide and the migration guide for your specific setup, handles Xcode capability configuration, SDK initialization at every entry point, transaction finishing, and unfinished transaction recovery on launch.

For a full comparison of the strategies, see iOS Billing Integration Strategies.

Diagnose your integration​

/appcoins-diagnose

Open your project in the editor before running this command.

The agent audits your integration against known failure points: Keychain Sharing configuration, URL scheme, MKSellsDigitalGoods, SDK initialization at every entry point, unfinished transaction handling, and others. It reports issues by file and line number and offers to fix them automatically.

Run this before a release or after an Xcode upgrade that may have dropped capabilities.

Ask questions​

/appcoins-help how do I handle a notEntitled error?
/appcoins-help what is the difference between single build and separate builds?
/appcoins-help what do I need to submit to Aptoide Connect?
/appcoins-help how do I recover unfinished transactions on app launch?

The agent answers from live SDK documentation. Responses are scoped to the AppCoins API.