Track Skool MRR Automatically: Stop Guessing Your Revenue

To track Skool MRR automatically you need two things: a connection to your community that can read member and revenue data on demand, and a way to pull those numbers on a schedule so you can compare one period to the last. Creator OS does both. You sign in to Skool once through Skool’s own page, share your communities read or read & write, and then your MRR, member counts and growth become readable from the web app, the CLI, or an AI agent over MCP. No exporting CSVs, no rebuilding a spreadsheet every Monday morning.

This post walks through what actually counts as MRR in a Skool community, why snapshotting it by hand keeps failing, and the exact commands and tool calls that give you the number on a schedule.

  Skool community
        |
        |  members, MRR, growth, engagement
        v
  Creator OS  ----->  web app
        |          ----->  creatoros skool:revenue
        |          ----->  MCP: skool_revenue
        v
   your agent / dashboard / export

One connection, three ways to read the same MRR number.

Why Manual MRR Tracking Breaks Down on Skool

Skool shows you revenue inside the community. It does not hand you a running time series you can chart without effort. So the usual workflow looks like this: on the first of the month, you open the community, write the figure down, and paste it into a spreadsheet. Twelve times a year. That works until it does not.

It breaks in three places:

You forget. One missed first-of-month screenshot and your chart has a hole in it.
You can’t see the middle of the month. MRR moves whenever members join or leave. A monthly snapshot hides all of that movement.
You can’t answer follow-up questions. Was growth better in March or April? Which tier drove it? A static cell in a spreadsheet cannot tell you.

If you are already automating other parts of your community, like join request approvals, the gap becomes obvious. You are approving members automatically but counting their money by hand.

Get started for $0

What Counts as MRR in a Skool Community

MRR is monthly recurring revenue. In a Skool community the recurring part comes from paid memberships, which can be billed monthly or annually. There is a real trap here: annual plans. If someone pays for a year up front, that is not one month of MRR. Divide it by twelve before you add it to the total.

Three numbers matter, and they are not the same number:

MRR. The normalized monthly value of every active paid membership.
Gross revenue. Actual money that landed, including annual payments in full. Higher than MRR in the month an annual member joins, lower than MRR in the months after.
Net revenue. What is left after refunds, chargebacks and payment fees.

Most Skool owners who “track MRR” are actually tracking gross revenue and calling it MRR. That is one of the reasons their numbers never line up with what they expected to earn.

The Data You Need: Members, Status, and Growth

To track MRR properly you need four streams of data, not one:

Current members by status. Active, churned, banned, pending, invited. Only active paying members contribute MRR.
Revenue. The recurring figure Skool reports for the community.
Growth over time. How the number changed, not just where it sits today.
Member movement. Who joined and who left, and when. Churn is the half of MRR that most people never look at.

Creator OS reads all four. The Skool integration covers members by status, collected emails, MRR, 30-day growth and engagement, and it exposes them through a CLI and an MCP server so you can pull them on a schedule instead of by hand. Details are in the Skool docs.

Spreadsheets, Custom Scripts, and What You Actually Need

The manual route is: log into Skool, read the MRR figure, log into your payment tool, export a CSV, paste the numbers into Google Sheets, build a formula that handles annual members, and repeat every month. It fails for one structural reason. Every step depends on a human remembering to do it, and none of the steps talk to each other. Your community member list and your payment list are two different views of the same people, and reconciling them by hand is where the errors live. A membership can end in one system on a different day than it ends in the other, and nobody notices until the chart looks wrong. If you want a worked comparison of what direct access looks like versus manual exports, the post on Skool API alternatives covers that ground.

You could also build it yourself. A scheduled job that hits an endpoint, writes to Postgres, and renders a chart. That is a weekend of work, plus ongoing maintenance when something upstream changes. The harder part is not the fetching. It is the normalization. You need to decide how annual plans convert, how upgrades mid-cycle count, how refunds flow through, and how you store periodic snapshots so period-over-period comparisons are possible. Then you need to keep it running when your server reboots.

Creator OS takes the third route. Connect once, then read the numbers however you like, from the web app, the CLI, or an AI agent over MCP. The Skool MCP server write-up shows what that connection exposes if you want the shape of it before you start.

Automatic MRR Tracking With the CLI

After installing the CLI and authenticating, your community’s revenue is one command:

creatoros skool:revenue your-community-slug

Growth, on its own:

creatoros skool:growth your-community-slug

And if you want the underlying time series rather than a single figure, the chart command takes a metric name. For MRR you would use mrr, and related series include new_mrr_by_day, new_mrr_by_source, members, members_cohorts, retention_members and conversion_by_day. For example:

creatoros skool:chart your-community-slug mrr

Because these are CLI commands, they compose. You can run them from a cron job, pipe the output into a file, and end up with a daily MRR log without writing a line of integration code. The same connection also answers the churn question: creatoros skool:members your-community-slug --tab churned returns the members who left, so “churn was high last month” turns into a specific list.

Automatic MRR Tracking With an AI Agent Over MCP

Creator OS ships a hosted MCP server at https://mcp.creatoros.ca/mcp. There is nothing to install. You add it as a connector in Claude or ChatGPT, or as an entry in Claude Code, Cursor, Windsurf or VS Code, and the agent gets tools including skool_revenue and skool_find_posts. Setup steps are in the MCP docs.

Once connected, a prompt like this works:

“Pull my Skool revenue and growth for the community, compare it to the member count, and tell me whether MRR grew faster or slower than the member base over the last 30 days.”

That is a question a spreadsheet cannot answer without you doing the math. It is also the kind of thing agents are good at when they have the right tools. If you want a ready-made agent instead of wiring one yourself, Social Agents is an open-source harness that runs your socials and community on Creator OS. Start it with npm start creatoros social-agents. It interviews you about your brand, then posts, replies and reports. You can watch walkthroughs of that on the KevBuildsApps YouTube channel.

Read-only is an option

If you only want reporting, connect with read-only access. Read-only connections only see read tools, and the API refuses writes from them. So an analyst account or a reporting agent physically cannot post, delete or change anything in your community. That is a useful safety property when you hand a tool to an AI app you are still getting used to.

Reading Your MRR Dashboard: Growth, Churn, and Net Revenue

Getting the number is the easy part. Knowing what it means is where the value sits. Three comparisons matter:

Compare	What it tells you
MRR this period vs last period	Whether the community is compounding or flat
MRR growth vs member growth	Whether you are adding volume or adding value per member
New MRR vs churned MRR	Whether growth is real or just churn being masked by new joins

That third row is the one people skip. A community can add a lot of new MRR in a month and lose almost as much to churn. The headline number goes up. The business does not. Pulling new_mrr_by_day and the retention series side by side makes that visible in a way a single period figure never will.

Pair this with how people are actually moving through the community. The Skool community posting tool write-up covers the publishing side, and it is worth reading the two together: posting drives joins, and joins drive MRR.

Common Mistakes That Inflate or Hide Your Real MRR

Counting annual plans at full value. Divide the annual price by twelve before adding it to MRR, otherwise one annual join swamps the month.
Ignoring refunds. Refunds reduce net revenue. If your MRR number never moves after a refund, it is not tracking net.
Treating gross and net as the same thing. They diverge the moment fees and refunds enter the picture.
Only snapshotting once a period. You lose the daily signal that tells you which day of the month churn actually happens.
Mixing communities. If you run several communities, track them separately before rolling them up. A blended number hides which one is healthy. The skool:chart command takes one community slug at a time for exactly this reason.
Measuring MRR but never measuring churn. Revenue going up while retention goes down is a countdown, not growth.

If churn is your actual problem rather than measurement, look at whether members are getting answers to their questions. Running the community well and measuring it well are related but separate jobs. The CLI has commands for finding unanswered posts and posting to several communities at once, which is a practical lever on the first one.

Get Started: Connect Skool and See Your MRR Today

The setup is short. In Creator OS, connect Skool by signing in on Skool’s own page and sharing your community read or read & write. Then either run creatoros skool:revenue your-community-slug from a terminal, or add https://mcp.creatoros.ca/mcp as a connector and ask your AI app for the number in plain English.

The Creator plan is $14.99/month or $59.99/year and covers 11 platforms plus Skool, one account on each. API keys, the MCP server, the CLI and the agent skills are included in every plan, so MRR tracking does not cost extra on top. Agency plans are available if you run more than one community or client set.

Sign up at creatoros.ca/sign-up, connect your community, and put the reporting on a schedule instead of on your calendar. If you want to see the automation side first, the KevBuildsApps channel has walkthroughs, and the launch video covers the open-source agent tools that sit on top of this. The full command reference lives in the docs.

Get started for $0
Free trial for new subscribers. Cancel anytime.