BillDog

🐶 BillDog MCP Server

Set up and inspect paywalls, subscriptions and analytics for your app — from your AI coding agent.

https://api.billdog.io/mcp

Install · What you can ask · Tools · Permissions · Troubleshooting

BillDog is paywalls, in-app purchases, subscriptions, analytics, messaging, surveys and journeys behind one SDK for iOS, Android, React Native, Flutter, Expo and the web. This repository is how AI agents connect to it:

• A hosted MCP server. 57 tools: diagnose an integration, build the product catalog, design and publish paywalls, and query revenue and retention.
• Plugins for Claude Code, Cursor and Antigravity. The server plus three skills: wiring the SDK into an app, paywall A/B experiments and feature flags, and migrating from RevenueCat, Superwall, Adapty and others.

Nothing runs on your machine. The server is hosted by BillDog and every client connects to the same URL.

Install

You need a free BillDog account at billdog.io with at least one project.

The first time a tool runs, your browser opens Sign in with BillDog. That's the whole setup.

Config file snippets

Cursor (~/.cursor/mcp.json) and most clients:

{

"mcpServers": { "billdog": { "url": "https://api.billdog.io/mcp" } } }

VS Code (.vscode/mcp.json):

{

"servers": { "billdog": { "type": "http", "url": "https://api.billdog.io/mcp" } } }

Antigravity (mcp_config.json, which uses serverUrl rather than url):

{

"mcpServers": { "billdog": { "serverUrl": "https://api.billdog.io/mcp" } } }

Clients that only launch local (stdio) servers, bridged with mcp-remote:

{

"mcpServers": { "billdog": { "command": "npx", "args": ["-y", "mcp-remote", "https://api.billdog.io/mcp"] } } }

Sign in with BillDog

The server uses OAuth 2.1 with PKCE and dynamic client registration, so your client registers and authenticates itself:

1. Your client discovers the authorization server from the server's 401 (RFC 9728).
2. It registers itself and opens BillDog in your browser.
3. You sign in, pick one project, and choose what the agent may do.
4. The agent gets a short-lived token for that project only. It refreshes on its own, and you can disconnect it at any time.

Using a key instead

For scripts, CI, or clients without OAuth, create a key at [Dashboard → AI Assistant (MCP) Keys](https://billdog.io/dashboard/analytics/api-keys). MCP keys start with bd_mcp_ and are read-only.

claude mcp add --transport http billdog https://api.billdog.io/mcp \

--header "Authorization: Bearer bd_mcp_YOUR_KEY"

[!IMPORTANT]

bd_public_… and bd_secret_… keys are SDK keys for your app and won't work here. The server tells you so if you paste one.

What you can ask

*"Why isn't my paywall showing on iOS?"*

→ get_setup_status and resolve_placement_preview show exactly what's missing, with dashboard links.

*"Set up monthly and annual Pro plans with a 7-day trial and an onboarding placement."*

→ apply_setup_plan creates the products, entitlement, offering and placement in one step. Everything starts inactive.

*"Design a dark paywall for the annual plan from a template, show me a preview, then publish it."*

→ list_templates → create_paywall_from_template → update_paywall → preview_paywall → publish_paywall

*"What was MRR last month and which paywall converts best?"*

→ run_analytics_query

*"Migrate this app from RevenueCat."*

→ the billdog-migration skill (Claude Code plugin) rewrites the call sites and recreates the catalog.

Tools

29 read · 28 write · *publish* means it changes what live users see and needs the publish permission. Machine-readable list: tools.json.

Setup & diagnostics

Analytics

Catalog: products, entitlements, offerings, placements

Paywalls

Experiments & feature flags

Projects & SDK keys

| list_projects | read | List all BillDog projects accessible to the auth