AI SDK Integration via Singular MCP

Follow
Avatar
Support Team
Updated

Ship your Singular integration in 30 minutes — without reading the docs

Integrating an analytics SDK usually means hours of reading documentation, writing boilerplate, and debugging edge cases before your first event fires. The Singular MCP SDK Integration Skill cuts that down to a single conversation with your AI coding assistant.

Connect once, describe your app, and your assistant handles everything: detecting your platform and framework, asking only what it can't figure out automatically, writing the code, and validating the result — all without you leaving your editor. By the end you'll have a fully wired Singular SDK: initialization, privacy compliance (ATT, GDPR, COPPA), deep links, revenue tracking, and event mapping.

Works with Claude, Cursor, ChatGPT, Gemini CLI, VS Code Copilot, and any other MCP-capable assistant.

How the flow works

Once you connect the Singular MCP and open your project folder in your coding assistant, the integration runs in a guided, conversational flow. Here's what to expect:

  1. Connect to the MCP — connect the Singular MCP to your AI coding assistant. Follow the setup guide for your assistant: Singular MCP — Setup Guide. The MCP URL is: https://mcp.singular.net/mcp-server/mcp (OAuth with your Singular login).
  2. Scan — the assistant scans your project to detect your platform, framework, privacy requirements, deep linking setup, monetization, and any existing analytics events.
  3. Existing integration check — if Singular code is already present, you choose: fill in the gaps, start fresh, or exit.
  4. Targeted questions — only asks what it couldn't detect automatically, one question at a time: platform, framework, where to store your SDK key/secret, privacy requirements, ATT, deep linking, revenue, and event tracking.
  5. Summary & confirmation — before writing a single line, the assistant shows you a full summary of the planned integration. No files are changed until you confirm.
  6. Implementation — fetches the latest Singular documentation for your confirmed setup and writes the code into your project.
  7. Project memory — writes a Singular section to your agent config file (CLAUDE.md, AGENTS.md, or GEMINI.md) and drops a KNOWN_ISSUES.md for your framework.
  8. Validation — runs a pass/fail checklist covering: install, init, SKAdNetwork, events, deep links, revenue, and privacy. If anything fails, the assistant proposes fixes.
  9. "Before you test" checklist — prints your Android package name or iOS bundle ID and verifies the app is registered in your Singular account. If it's not found, you'll be prompted to create it in the Singular UI before running the app.

How long does it take? A typical run takes about 30 minutes — most of that time is waiting for your input at the question steps.

Supported AI assistants

Any AI coding assistant that supports remote MCP servers can run the SDK Integration Skill. This includes:

  • Claude / Claude Code (paid plan) — primary test environment
  • Cursor
  • ChatGPT (Developer Mode)
  • Gemini CLI
  • VS Code Copilot
  • Codex and other MCP-capable assistants

Supported platforms

Platform / Framework Status
Native Android (Kotlin / Java) Supported
Native iOS (Swift / Objective-C) Supported
React Native (bare & Expo) Supported
Flutter Supported
Unity Beta
Cordova / Ionic Beta
Unreal Engine Beta

What the skill covers

  • SDK dependency installation
  • SDK initialization with SingularConfig at the correct app lifecycle point
  • Secure SDK key/secret storage (never hardcoded)
  • ATT prompt & NSUserTrackingUsageDescription (iOS)
  • Privacy consent wiring: COPPA, GDPR, CCPA, LGPD
  • Deep links: Universal Links, App Links, deferred deep links, Singular Link callbacks
  • IAP revenue and SDK-based subscription revenue
  • Event tracking mapped to Singular standard or custom events
  • User ID (if an auth flow exists in your app)

FAQ

Can I use this if I already have a partial Singular integration?

Yes. When the skill detects existing Singular code, it asks whether you want to fill in the gaps, start over, or do nothing. It's designed to work with partial integrations.

Can I use SDK integration alongside a server-to-server (S2S) setup?

Yes. A common pattern is to run most events via S2S and use the SDK skill for initialization, privacy compliance, deep links, and selected events. Mixed setups are fully supported.

How does the assistant know which SDK key to use?

The skill asks you where to store your SDK key and secret during the question phase — it never hardcodes credentials into your source files. Common patterns include environment variables, build config files, or platform-specific secrets (e.g., EAS secrets for Expo).

Is the integration code reviewed before it's written to my files?

Yes. Step 5 of the flow shows you a full summary of what will be implemented before any files are modified. You must confirm before the assistant writes any code.

Are integrations with third-party subscription and ad monetization vendors supported?

Not directly. The skill handles SDK-based IAP revenue and standard subscription events natively. However, it does not configure integrations with third-party vendors such as RevenueCat, Adapty, or Superwall, or set up server-to-server (S2S) subscription flows, or ad monetization revenue attribution.

For these, refer to the relevant Singular documentation:

What else is outside the scope of this skill?

The following features are outside the scope of the AI SDK integration flow. Each links to the relevant Singular documentation:

The skill will point you to the relevant docs if you ask about these topics during a session.

My platform is listed as Beta (Unity, Cordova/Ionic, Unreal). What does that mean?

For Beta platforms, the assistant relies on live Singular Help Center documentation rather than a dedicated, pre-validated reference file. The integration should work in most cases, but we recommend reviewing the generated code carefully — especially the diffs — before merging or shipping to production.

What happens after the integration is written?

The assistant runs a validation checklist (install, init, SKAdNetwork, events, deep links, revenue, privacy) and proposes fixes for any failures. It also writes a Singular section to your project's agent config file so future sessions retain context about your integration.