Docs · Chapter 1 of 10

MCP Setup

Connect your AI coding agent to the Tierux MCP server — automate Google Play setup, product creation, and paywall configuration in one prompt.

1

Add the server

The Tierux MCP server lives at https://mcp-tierux.web.app. No API key or config header is needed — pick your client below for a one-command install.

Claude Code — the plugin bundles the MCP server plus a billing skill and setup prompts, so Claude reaches for Tierux on its own:

/plugin marketplace add tierux-ai/tierux
/plugin install tierux@tierux

Or add just the MCP server, without the skill:

claude mcp add --transport http tierux https://mcp-tierux.web.app

Cursor

Add to Cursor

Or add manually to .cursor/mcp.json:

{
  "mcpServers": {
    "tierux": {
      "url": "https://mcp-tierux.web.app"
    }
  }
}

VS Code

code --add-mcp '{"name":"tierux","type":"http","url":"https://mcp-tierux.web.app"}'

ChatGPT (Plus/Pro/Team)

Settings → Apps & Connectors → Advanced → enable Developer mode → New connector → enter https://mcp-tierux.web.app as the server URL.

Claude.ai (Pro/Team)

Settings → Connectors → Add custom connector → enter https://mcp-tierux.web.app as the server URL.

2

Sign in when prompted

Your client opens a browser window to complete an OAuth sign-in — use the same Google account as your Tierux dashboard. There's no API key to paste and no config header to set. (pe_live_ keys are for the REST API and client SDKs — the MCP server never accepts them.)

3

Teach your agent to use it (Codex, Cursor, Claude Code)

Connecting the server gives your agent the tools; this tells it when to reach for them. The Claude Code plugin above does this for you. For Codex or Cursor — which have no plugin system — paste this into your repo's AGENTS.md (or CLAUDE.md):

## Billing / in-app purchases

This project uses **Tierux** for purchase verification and entitlements. The Tierux
MCP server is connected as `tierux`.

- For anything involving in-app purchases, subscriptions, receipt or purchase-token
  verification, entitlements ("is this user pro?"), store products, or paywalls:
  **use the `tierux` MCP tools.** Do not hand-write Google Play Android Publisher
  or App Store Connect / StoreKit 2 verification code.
- Start with `list_apps` to find the `appId`; pass it to later calls.
- Write tools return a preview and a `confirmToken` and save nothing on the first
  call. Show me the preview and wait for my approval before calling again with the
  token. Never auto-confirm.
- Use `generate_sdk_snippet` for client and backend integration code rather than
  writing the HTTP calls by hand.
- Never put an API key in client code. `pe_live_` keys are REST-only and are
  rejected by the MCP server.

Connected agents can also pull it themselves from the tierux://agents-snippet MCP resource — no need to come back here.

4

Available MCP tools

Once connected, your agent gains these tools:

// Setup
setup_google_play, setup_app_store, setup_stripe_web, create_project

// Products
create_play_product, create_app_store_product, update_app_store_product,
delete_app_store_product, get_app_store_product, list_app_store_products

// Mappings
create_product_mapping, get_product_mappings

// Paywalls
create_paywall, update_paywall, get_paywall, list_paywalls,
publish_paywall, translate_paywall, create_winback_offer

// Verify / entitlements
verify_purchase, verify_apple_purchase, check_entitlement

// Misc
set_webhook, generate_sdk_snippet

create_project returns a public app_xxx ID after confirmation; you can also copy it from the dashboard. Pass that ID as appId to subsequent MCP calls and to SDK initialization.

5

Security: confirm_token

Every MCP write operation returns a preview and a confirm_token. Your agent confirms by calling the SAME tool again, passing that token back as an argument — nothing is persisted without explicit approval. This prevents unintended changes to your production billing configuration.

▸ "Create a project called My App"

create_project(name: "My App", packageName: "com.myapp")
  → preview: { name: "My App", packageName: "com.myapp" }
  → confirmToken: "ct_abc123..."

▸ "That looks good — confirm"

create_project(name: "My App", packageName: "com.myapp", confirmToken: "ct_abc123...")
  → app created ✓
6

Post-setup: validate the purchase path

After your agent configures Google Play and the Tierux-side products, test the purchase path. For Apple, App Store Connect product and notification setup remains manual before testing.

▸ "Create a test product and verify a real purchase"

// Agent creates test product
create_play_product(productId: "test_sub", billingPeriod: "P1M",
  price: "0.99", currency: "USD", appId: "app_xxx")

// You make a test purchase in your app
// Agent verifies it with the REST API
curl -X POST https://tierux.com/api/v1/purchases/google-play/verify \
  -H "Authorization: Bearer <your REST API key>" \
  -d '{ "appId": "app_123", "userId": "test_user", … }'

// 200 OK — entitlement created, visible in dashboard
Related docs

Docs: RTDN

Google Play real-time developer notifications — automated by MCP setup.

Docs: SDKs

Client SDK integration — Android (Maven), iOS (SPM), and REST-first frameworks.

Quickstart

Integration checklist: configure Tierux, complete required store-console work, connect REST, and verify a purchase.

Feature: MCP Setup

Your AI agent configures Google Play infrastructure and Tierux products and paywalls over MCP; App Store Connect product and notification setup remains manual.

Your agent configures Tierux. You complete store-console setup.

Then validate a purchase through the store-specific verification endpoint. Free tier — unlimited apps, 1 paywall.

Start free