Firebender + Subscription MCP: Manage Subscriptions from the IDE
Android work usually happens in Android Studio, but subscription operations have lived in a browser tab. Firebender closes that gap by connecting to a subscription platform's MCP server directly from the IDE, so an AI agent can create and inspect offerings, packages, entitlements and paywalls, and answer revenue questions from the Charts API, all through conversation.
Connecting with OAuth 2.0
Firebender reaches the subscription platform's MCP server through OAuth 2.0. Inside Android Studio or IntelliJ, open Firebender's settings, add the MCP server, and choose the sign-in option for your account. Authorization happens in your browser; Firebender completes the token exchange and stores the credentials.
After authorization the agent lists your projects and asks which one to work in. Every later action is scoped to that project. The OAuth grant covers project configuration, charts and metrics, and customer information, so the agent can read and change offerings, packages, entitlements and paywall configuration, and query revenue data, within the permissions you approved. Expired tokens refresh automatically, so sessions do not require manual reconnection.
Scope-to-capability map:
- Project configuration scope → create, read, update and delete offerings, packages, entitlements and products; generate paywalls.
- Charts and metrics scope → query the 21 available chart types, including MRR, ARR, churn, trial conversions, active subscriptions, new paid subscriptions and retention cohorts.
- Customer information scope → read customer data surfaced through the agent.
If you want to limit what the agent can touch, review the scopes shown during browser authorization before approving.
Creating offerings and packages by prompt
Once connected, the agent performs create, read, update and delete operations on offerings, packages, entitlements and products. You describe the change; the agent issues the API calls.
A worked example from the captured workflow: ask for a new offering called Premium with a monthly package at $9.99 and an annual package at $79.99. The agent creates the offering, builds both packages and attaches the matching products. If any of those resources already exist, it detects the duplicates and reuses them rather than creating new ones.
You can also extend an existing structure without rebuilding it. Asking the agent to add a weekly package to the existing Premium offering causes it to read the current offering, confirm what is already configured, and add only the new package.
Configuring entitlements and handling conflicts
Entitlements tie products to feature access in the app. Doing this by hand in the dashboard means moving through several screens and attaching products one at a time; through the agent it can be a single prompt.
For example, ask for an entitlement called pro_access attached to all subscription products. The agent creates the entitlement, lists existing products and attaches each one. If a product already belongs to a different entitlement, the agent does not reassign it quietly: it surfaces the existing attachment and leaves the choice of how to resolve it to you.
You can also target specific products, such as an entitlement called premium_features attached only to annual and monthly products. The agent looks up, creates and attaches in sequence without you supplying product identifiers.
Failure distinction to keep in mind:
- Entitlement conflict → the agent stops and reports that a product already belongs to another entitlement; you choose the resolution.
- Orphaned product → the agent surfaces products not attached to any package when you ask for an audit; nothing is changed automatically.
Auditing project configuration
The agent can also describe the current state of the project, which helps before submitting a build for review. Ask which offerings have paywalls and it returns a summary, explicitly calling out offerings without one. Ask which products are not attached to any package and it cross-references products, packages and offerings to surface orphaned resources. That cross-check is slow to do manually as a project grows; the agent returns it in one query.
End-to-end AI paywall generation
The most direct use of the connection is generating a paywall from a description. The agent creates the supporting offering and package structure if needed, then submits a generation job with the context from your prompt. The platform's AI uses that context to produce copy, imagery, styling and template selection suited to the app and audience.
A prompt such as generating a paywall for a fitness tracker aimed at health-conscious users is enough to start. The agent monitors the job in the background and notifies you when the paywall is ready, with a link into the paywall builder for review and publishing. You do not need to poll the dashboard.
Multiple requests can run in sequence; each job is tracked independently, so a premium paywall and a freemium paywall can be requested back to back without conflict. To iterate for a campaign, you can base a new paywall on an existing offering, for example a summer fitness challenge with a discount on the annual plan. The agent reuses the existing offering and package structure and submits the job with the campaign context.
Revenue questions with the Charts API
The agent can query 21 chart types from the Charts API, including MRR, ARR, churn rate, trial conversions, active subscriptions, new paid subscriptions and retention cohorts. Questions in plain English return data-backed answers without opening a browser.
Examples of the kind of question the agent handles:
- MRR trend over the last six months, queried with the appropriate date range and resolution.
- Trial-to-paid conversion rate by week, queried at weekly resolution, with the option to compare weeks or request an overall rate for a custom range.
- Revenue this month versus last month, useful between code reviews or before a release.
- Churn rate for annual subscribers, using available segment filters to narrow the result.
Because analytics and configuration share a session, you can move from a signal to an action. Asking why trial conversion dropped this week and which paywalls are live on the default offering returns both the chart data and the current paywall configuration.
When to use the agent and when to open the dashboard
The conversational workflow is strongest for repetitive configuration, quick audits and revenue checks you would otherwise context-switch for. A short checklist:
Use the agent when you are:
- Creating or extending offerings and packages from a description.
- Attaching entitlements across many products at once.
- Auditing which offerings lack paywalls or which products are orphaned.
- Generating a paywall from campaign context and monitoring the job.
- Pulling a chart or comparing periods without leaving the IDE.
Open the dashboard when you need:
- Visual review and publishing of a generated paywall in the builder.
- Detailed inspection of a specific configuration the agent has flagged for your decision.
- Any action outside the scopes you approved during OAuth.
The agent carries out API calls and monitors asynchronous jobs, but the final review and publish step for a paywall remains in the paywall builder.
Frequently asked questions
How does Firebender connect to the subscription platform's MCP server?
Through OAuth 2.0. You add the MCP server in Firebender's settings inside Android Studio or IntelliJ, sign in with your account in the browser, and Firebender completes the token exchange and stores the credentials. You then pick the project the agent should work in, and tokens refresh automatically when they expire.
What permissions does the OAuth flow request?
Scoped permissions for project configuration, charts and metrics, and customer information. That allows the agent to read and modify offerings, packages, entitlements and paywall configuration, and to query revenue data, within the bounds of what you approved.
What happens if an offering or package already exists?
The agent detects the duplicate and reuses the existing resource instead of creating a new one, so you can ask for a Premium offering with monthly and annual packages without duplicating what is already configured.
What if a product is already attached to another entitlement?
The agent reports the existing attachment back to you so you can decide how to proceed. It does not silently reassign the product.
Which revenue metrics can I ask about?
The agent can query 21 chart types from the Charts API, including MRR, ARR, churn rate, trial conversions, active subscriptions, new paid subscriptions and retention cohorts, with date ranges and resolutions you specify in plain English.
Does the agent publish the paywall for me?
The agent submits the generation job and monitors it in the background. When the paywall is ready, you get a notification with a link to the paywall builder, where you review the design and publish it.