AI SDK Integration via Singular MCP – Singular Help Center

Overview

Integrating a mobile SDK usually means hours of reading documentation, writing boilerplate, and debugging edge cases before your first event fires. The Singular SDK Integration Skill turns that into a single conversation with your AI coding assistant.

Connect the Singular MCP, describe your app, and the assistant does the rest: it detects your platform and framework, asks only what it can't work out on its own, writes the code, and validates the result, all without leaving your editor. By the end you have a fully wired Singular SDK: initialization, privacy compliance (ATT, COPPA, GDPR, CCPA, LGPD), deep links, revenue tracking, and event mapping.

Works with Claude, Cursor, ChatGPT (Developer Mode), Gemini CLI, VS Code Copilot, and other MCP-capable assistants.

How the flow works

Once you connect the Singular MCP and open your project folder in your coding assistant, the SDK Integration Skill runs as a guided conversation. Here's what to expect:

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

How long does it take? A typical run takes about 30 minutes. Most of that time is spent waiting for your answers 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)
Cursor
ChatGPT (Developer Mode)
Gemini CLI
VS Code Copilot
Other MCP-capable assistants, such as Codex. The Singular MCP setup guide does not cover these, so follow your assistant's own instructions for adding a remote MCP server.

Supported platforms

Platform / Framework	Status
Native Android (Kotlin / Java)	Supported
Native iOS (Swift / Objective-C)	Supported
React Native (bare and 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 point in the app lifecycle
Secure SDK key and secret storage (never hardcoded)
ATT prompt and 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 your app has a sign-in flow)

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 the SDK integration alongside a server-to-server (S2S) setup?

Yes. A common pattern is to send most events through S2S and use the SDK Integration 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 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, and platform-specific secrets (for example, 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. It does not configure integrations with third-party vendors such as RevenueCat, Adapty, or Superwall, set up server-to-server (S2S) subscription flows, or set up ad monetization revenue attribution.

For these, see the relevant Singular documentation:

Subscription Event Technical Implementation Guide: covers SDK, S2S, and third-party options
Ad Revenue Attribution FAQ and Troubleshooting
Ad Monetization Analytics FAQ
Server-to-Server Fundamentals

What else is outside the scope of this skill?

The following features are outside the scope of the SDK Integration Skill. Each links to the relevant Singular documentation:

Referrer short links: Android, iOS, React Native, Flutter, Unity, Cordova, Unreal Engine. To create short links from your server instead, see Dynamic Short Links and Referral Tracking.
Global properties: Android, iOS, React Native, Flutter, Unity, Cordova

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

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

For Beta platforms, the assistant relies on the live Singular Help Center documentation rather than a dedicated, pre-validated reference file. The integration should work in most cases, but review 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, initialization, 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 keep context about your integration.