Superwall MCP server, with a policy gate.
Paywall and subscription access for AI agents, classified the way Superwall labels its own tools: Gentkey proxies the official Superwall MCP server's 214 tools, gives free access to the 90 reads that expose nothing sensitive, and puts customer data, analytics SQL, and Superwall's Apple Search Ads and App Store Connect proxies behind their own narrow grants.
https://app.gentkey.com/mcpclaude.ai (web & mobile) · Claude Code · Cursor · any MCP clientWhat’s free, what needs a grant.
Reads: 90 tools work with no grant — every tool Superwall itself labels read-only, from apps, paywalls, campaigns, and products to Apple Search Ads reports and App Store Connect listings — except 20 that stay grant-gated for what they expose: individual customers' data, webhook delivery logs that replay event payloads, and app details that carry App Store notification URLs with live tokens.
Writes: Apple Search Ads and App Store Connect changes, which Superwall proxies to Apple, each offer a narrow grant, as does analytics SQL. The full write grant authorizes every gated tool, including customer data, ad spend, and App Review submissions. Other changes — paywalls, campaigns, products, entitlements, webhooks, and raw API requests — and unclassified new tools require that full grant.
Gentkey proxies the official Superwall MCP server (https://superwall-mcp.superwall.com/mcp) — you get the vendor’s own tools, with custody, gating, and audit added in front.
| Grant | What it governs |
|---|---|
mcp-superwall.users.read | Individual customers — subscriptions, spend, attributes, events, and audience members |
mcp-superwall.webhooks.read | Webhook configs and delivery logs, and app details carrying App Store notification tokens |
mcp-superwall.data.read | Raw ClickHouse analytics SQL |
mcp-superwall.apple_search_ads.write | Apple Search Ads campaigns, keywords, ads, and budget orders — uncapped; budget caps live in the native Apple Search Ads connector |
mcp-superwall.app_store_connect.write | App Store Connect subscriptions, prices, offers, versions, and submitting for review |
mcp-superwall.write | Every gated tool, including customer data, Apple ad spend and App Review submissions, raw API requests, and unclassified tools |
Connect once, use everywhere.
Sign in at gentkey.com, add Superwall (oauth), then point each client at your endpoint. Every client completes a standard OAuth flow and lands in your Gentkey — your connections, nobody else’s.
claude.ai (web & mobile)
- Settings → Connectors
- Add custom connector
- Paste
https://app.gentkey.com/mcpand finish the OAuth prompt
Claude Code
claude mcp add --transport http \
gentkey https://app.gentkey.com/mcpCursor
// .cursor/mcp.json
{
"mcpServers": {
"gentkey": { "url": "https://app.gentkey.com/mcp" }
}
}Things agents do with Superwall here.
- How did paywall conversion change after last week's edit?
- List the active campaigns and their placements.
- Which search terms drove installs on the brand campaign last week?
- Which products are attached to the annual entitlement?
Custody, gating, and audit — built in.
The model never sees a credential
Your Superwall token is encrypted at rest and injected server-side at call time. Your stored credential never enters a context window.
Writes need a grant
Anything that changes state needs a capability you granted explicitly — revoke it and the next call is denied.
A trail you can act on
Every decision is attributed to the agent that made it — allowed, denied, or denied by constraint.
Fair questions.
Can Superwall itself limit what Gentkey can do?
Yes, and it should be your hard limit. Superwall's MCP sign-in carries your member role rather than API scopes, so connect while signed in as a Superwall member with a restricted role — Reader or Analyst, or Viewer on specific projects. Superwall enforces that role; Gentkey's grants apply within it.
Why is analytics SQL a grant when it only reads?
Superwall itself labels its query tool as more than a read: the query endpoint can provision credentials before running read-only SQL. Gentkey follows Superwall's label and keeps it behind mcp-superwall.data.read, far narrower than full write.
What happens when an agent calls a Superwall write tool it hasn't been granted?
The call is denied at the gateway — nothing reaches Superwall — and the denial is recorded in the audit log along with the grant that would have authorized it, so you can decide deliberately instead of finding out later.
Where are my credentials stored?
Encrypted at rest (AES-256-GCM) on Gentkey's server and injected server-side at call time. No credential you store with Gentkey ever enters a model's context window or an agent's config file.
Can I use this from claude.ai's free plan?
Yes — and it's the strongest case for a gateway: free claude.ai accounts currently get a single custom connector, so pointing that one slot at Gentkey puts every connector you've linked behind it.
How do I revoke an agent's access?
Revoke the grant (the next write is denied) or revoke the agent's tokens entirely in one click. Other agents and their grants are untouched — no shared key to rotate.
Is Gentkey affiliated with Superwall?
No. Gentkey is an independent MCP gateway. Trademarks belong to their owners; where an official Superwall MCP server exists, Gentkey proxies it and adds custody, gating, and audit on top.
Often connected together.
Cut Superwall a smaller key.
Sign in, connect Superwall, and grant your first scoped capability in under a minute.