Superwall MCP

The Superwall MCP lets AI agents manage your Superwall account through the Model Context Protocol. Instead of clicking through the dashboard, you can manage apps, products, campaigns, paywalls, and more, query your analytics, and work with App Store Connect and Apple Search Ads directly from tools like Claude, Claude Code, Cursor, and Codex.

Installation

In Claude, you can add the MCP from Claude's connector directory instead, along with a plugin that adds Superwall's skills. See Install in Claude. The steps below add the MCP by URL.

Add the Superwall MCP to your platform of choice using the URL https://mcp.superwall.com/mcp. You'll be prompted to log in to your Superwall account on first use.

Claude.ai

Go to Settings → Connectors, click Add Custom Connector, and enter https://mcp.superwall.com/mcp:

Cursor

Add the following to your ~/.cursor/mcp.json file:

{
  "mcpServers": {
    "superwall": {
      "url": "https://mcp.superwall.com/mcp"
    }
  }
}

Claude Code

claude mcp add superwall --transport http https://mcp.superwall.com/mcp

Codex

codex mcp add superwall --url https://mcp.superwall.com/mcp

To get the MCP and Superwall's skills together, install the Superwall plugin instead.

When you add the MCP via a CLI tool (Claude Code, Codex, or Cursor), a browser window will open to complete authentication. Log in to your Superwall account, and it will authenticate automatically. To check the connection, ask the agent something like "list my Superwall apps".

How it works

Every tool is a command of the Superwall CLI. The MCP serves the CLI's own commands, generated from the same definitions, so a tool takes the command's arguments and flags as input, runs the command's code, and answers with exactly what the command prints with --json, errors included. A command and its tool can't drift apart: a new CLI release brings its commands to the MCP too.

• Tool names are the command's words joined by _, with dashes turned into _ as well: superwall apps get is apps_get, superwall campaigns audiences readout is campaigns_audiences_readout, and superwall asc subscription-groups create is asc_subscription_groups_create.
• Inputs are the command's arguments and flags, in snake_case: --event-name is event_name. Each tool's description ends with the CLI command it runs.
• app takes an app's id, its name, or its dashboard link, the way --app does in the CLI. There are no organizations or projects to pick first.

What you can do

There are 208 tools:

App Store Connect and Apple Search Ads tools reach Apple through Superwall, with the keys and credentials already connected to your apps, so your agent never handles an Apple key. See the CLI reference for what each command does.

It does not control the live paywall editor canvas. For live design edits, use AI Chat Builder inside the editor or connect an external agent with Editor MCP.

The Superwall skill

The MCP serves the superwall skill too, so your agent knows how to approach each kind of task without installing anything. Clients that read MCP resources find every file of it at skill://superwall/SKILL.md and the references and workflows it links to; for the rest, the skill tool returns SKILL.md or any of those files by name. It is the same skill the CLI installs, as of the CLI release the MCP runs. The framework skill isn't served: building paywalls as code needs the CLI on your machine.

Permissions

Each call reaches the Superwall API as the person who signed in, so the tools can do exactly what your dashboard role allows, and nothing more. To limit what an agent can change, connect it with a teammate account that has a narrower role.

Every tool says what kind of change it makes, so your client knows when to ask you first:

The CLI asks before deleting, archiving, or anything else that can't be undone. A tool doesn't ask: your MCP client's approval prompt is the confirmation, so keep approvals on for destructive tools.

CLI-only commands

Some commands need your machine: they read your code, write files, open a browser, or sign in to Apple with your password. They have no tool, and the MCP tells your agent to ask you to run them in a terminal with npx superwall <command>, after npx superwall login:

Quick setup

You can use the Superwall MCP to go from zero to a fully working paywall setup without ever opening the dashboard. Just ask your AI agent to set up Superwall for your app. You can give it your app name, platform, bundle ID, and store product IDs, and it can create the app, products, entitlements, paywall, and campaign for you.

When the agent creates an app, it returns its public API key (pk_…). That's what you pass to Superwall.configure() in your app. From there, fire a placement event with register and your paywall will show.

Upgrading from the first version

The first Superwall MCP had its own, smaller set of tools. Its tools are gone, and agents pick up the new ones on their own. If you wrote prompts or automations around the old names:

Related

• Superwall CLI: The same commands in your terminal, plus the ones that need your machine.
• Plugins: The MCP and the skills in one install for Claude, ChatGPT, and Codex.
• Skills: Docs access, guided SDK integration, and account management through the CLI.
• Superwall Agents: AI workspace for Superwall analysis with connected tooling, automations, webhooks, and hosted machines.
• Editor MCP: Connect an external agent to the paywall currently open in the editor.
• AI Chat Builder: Build and refine paywalls with Superwall's built-in editor chat.
• Use Superwall with AI: Every AI tool for Superwall, and which one to pick.