Feature

MCP setup

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

CapabilityWith TieruxWithout Tierux
Google Play setupMCP agent automates service account creation and API enablement — RTDN delivery runs on Tierux's shared Pub/Sub topic, so there's no Pub/Sub topic or subscription to create. Finance access and pointing Play Console at the topic stay manual.Manual Google Cloud + Play Console configuration, plus your own Pub/Sub topic and subscription
Product configurationGoogle Play and Tierux-side configuration via MCP; App Store Connect products remain manualManual entry in Play Console / App Store Connect
Paywall configurationAgent builds packages, copy, and layoutCustom code or separate paywall builder
Entitlement mappingAgent maps products to entitlements in one stepCustom DB or config mapping
Preview before persistconfirm_token required for every writeN/A — manual changes are direct
Cross-agent portabilityStandard MCP — works with any compatible agentN/A — no MCP integration

Tierux is pre-launch. The MCP server is live at mcp-tierux.web.app and ships today with tools for Google Play setup plus Tierux product, entitlement, and paywall configuration. For production Apple verification, provide both the Bundle ID and App Apple ID; App Store Connect product and notification setup remains manual.

Related features

Purchase verification

After configuring Tierux and completing required store-console work, verify purchases server-side over the store-specific REST endpoint.

Entitlement mapping

Agent-configured product-to-entitlement mappings — read over REST from your backend.

Docs: MCP setup guide

Step-by-step instructions for connecting your AI agent to the Tierux MCP server.

Frequently asked questions

What is MCP-first billing?
MCP-first means Tierux exposes Google Play setup and Tierux-side product, paywall, and entitlement configuration as MCP tools that your AI coding agent can call directly. App Store Connect product and notification setup remains manual.
Which AI agents work with Tierux MCP?
Any agent that supports the Model Context Protocol — Claude Code, Cursor, Codex, and other MCP-compatible coding assistants. You add the Tierux MCP server URL to your agent's MCP config and sign in with Google when prompted (OAuth — no API key), and the tools appear in the agent's tool palette.
What can the MCP agent automate?
The agent can set up Google Play billing infrastructure (service account creation, API enablement), configure Tierux products and paywalls, map products to entitlements, and validate the purchase path with a preview before persisting changes. RTDN delivery runs on Tierux's shared Pub/Sub topic, so there's no Pub/Sub infrastructure for the agent to provision. Granting the service account Finance access in Play Console, pointing Play Console at Tierux's RTDN topic, and App Store Connect product and notification setup all remain manual. Each write operation shows a confirm_token you approve.
Is MCP setup secure?
Yes. The MCP connection authenticates with an OAuth sign-in, not a key, and your server-side REST API key never goes in client code. Write operations require a confirm_token that's shown in preview before anything is persisted. You approve every change explicitly.

Your AI agent configures Tierux.

Complete required store-console steps, then verify purchases through Tierux. Free tier — unlimited apps, 1 paywall.

Start free