Claude Baremetrics connectorWhat Claude can do in your Baremetrics account.
The Claude Baremetrics connector exposes 17 tools. All 17 read, 0 write: metrics, cohorts, customers, subscriptions, plans, charges, events. Below: what Claude can answer from your revenue data, what it cannot touch, and what setup it needs.
Verified Trustpilot reviews · AI, automation & growth agency
What changes for founders and finance teams
Baremetrics turns your billing data into SaaS metrics. With the connector, those figures stop living only on a dashboard: you ask Claude about MRR, churn, a cohort or a single customer, and it pulls the numbers itself and explains them in the conversation. The extension only reads, which Baremetrics states for every tool.
Board numbers in one question. get_metrics_summary sums up all your metrics for a date range, and get_metric adds the month-by-month curve when someone asks why.
From a number to the names behind it. get_metric_customers and get_metric_plans split a metric by account or by plan, so a jump in expansion revenue comes with the customers and tiers that caused it.
One customer's story before a call. list_customers finds the account, then get_customer and list_customer_events give its details and its event history.
What Claude will not do here. By default the sheet only exposes reading, and Baremetrics labels all seventeen tools read-only: no refund, no plan change, no cancellation. It runs as a desktop extension, listed for Claude Desktop only, and it needs your Baremetrics API key. Nothing runs on its own either: no tool fires when a customer churns. Alerts of that kind belong to an automation tool, a different job, gathered on the Integrations hub. For another data source Claude can query, see the Claude airtable connector.
Five words before you plug it in
The vocabulary you will meet while connecting Baremetrics.
- Connector
- The link you set up once between Claude and an account you already have, so Claude can work in that account while it answers you.
- Tool
- One named thing the connector lets Claude do. Claude picks the ones it needs by itself, and the directory sheet lists them by name.
- Authorization
- The service's own sign-in screen, where you hand Claude the access it will use later. Given once per person, and taken back the same way.
- Approval
- The confirmation Claude waits for before it goes through with a change to your account, shown in the chat at the moment it matters.
- MCP
- The shared standard connectors are built on: it is what lets an assistant such as Claude talk to an outside service like Baremetrics.
Connecting Baremetrics to Claude in three steps
- 01
Open the connectors in Claude Desktop
This one is a desktop extension, listed for Claude Desktop only. In the app's settings, open Customize, then Connectors, and find Baremetrics. On a Team or Enterprise workspace, an Owner or Primary Owner turns it on first.
- 02
Add it and hand over your key
Click Connect on its row. Baremetrics' documentation lists an API key from your Baremetrics account among the requirements, so have one ready. If the link breaks later, Disconnect and connect again.
- 03
Know what the key opens
The key decides what Claude reaches, not Claude. Baremetrics hands out keys from the API page of its settings; to cut Claude off later, Disconnect the extension from its row in Claude.
The 17 tools, sorted by what they do
Baremetrics gives Claude 17 tools: 17 that read your account, 0 that change something in it.
One group only: every tool on the sheet reads. Tool names stay as Claude shows them.
- 17 read
What Claude reads (17)
17 toolsSeventeen tools that look up your metrics and billing records without changing anything.
get_account
Returns the basic details of the Baremetrics account the API key belongs to. It is a quick way for Claude to confirm which company it is looking at before it quotes a single figure back to you.
list_sources
Lists the data sources connected to your Baremetrics account, with their IDs. Most other tools need one of those IDs, so Claude usually calls this one first, before any metric or customer lookup.
get_metrics_summary
Gives a summary of all your metrics over a date range in a single answer, the widest view the extension offers. Claude can then pick out the figures that matter for your question.
get_metric
Returns the time series of one metric, such as MRR, ARR or churn, over the period you choose. Claude can then describe the trend or compare it with an earlier period.
get_metric_customers
Shows which customers contribute to a given metric, so a number on the dashboard turns into actual account names. It is the step from how much to who.
get_metric_plans
Breaks a metric down plan by plan, so the total shows what each tier contributes. Claude can rank plans or spot the one that is shrinking.
get_cohorts
Runs a cohort retention analysis: groups of customers who joined in the same period, and how many of them stay or leave over the following months.
list_customers
Lists your customers and lets Claude search among them. It is how a name mentioned in a message becomes a Baremetrics record you can then open.
get_customer
Brings up what Baremetrics holds on one customer, for when a question is about a single account. Claude usually reaches it after finding the customer in the list.
list_customer_events
Returns the events recorded for one customer, the account's own timeline rather than the whole company's. Claude can read it alongside the customer's details.
list_subscriptions
Lists subscriptions across the account, so Claude can count them, group them or compare them by plan or status. You get the whole picture rather than one customer at a time.
get_subscription
Reads the details of a single subscription, the level to reach when a question is about one contract rather than a trend. Claude can set it next to the customer's event history.
list_plans
Lists every plan defined in your Baremetrics account. It gives Claude the vocabulary of your pricing before it talks about revenue per tier or per interval.
get_plan
Returns the details of one plan, useful when a question hinges on a specific tier rather than the whole catalogue. Claude reaches for it once it knows which plan you mean.
list_charges
Lists charges, with filters to narrow the set down. It is the transaction level of Baremetrics, below subscriptions and metrics, where individual payments show up.
get_charge
Opens the details of a single charge. Claude uses it when a question is about one payment, after spotting it in the list of charges or in a customer's history.
list_events
Lists events across the whole account rather than for one customer, which is where patterns such as a wave of cancellations become visible at a glance.
What Claude checks with you before acting
By default, Claude stops and asks for your go-ahead before each action it takes on an account on your behalf. The request shows up in the chat, right when it matters.
On Team and Enterprise, the owners decide whether a member may let some actions through without being asked every time. They can also limit what a connector may do for the whole organisation, keeping reading open and closing writing, for instance. That setting applies to everyone and nobody works around it from their own account. And Claude only reaches what your Baremetrics API key opens: the extension passes requests straight to Baremetrics with that key.
Which Claude plans include it
Out of the 819 sheets in the official directory, none shows availability by plan. The connector-by-connector answer is not published anywhere: it is a real gap in the catalogue.
The general rule is published: remote connectors are open to every user on Claude, Cowork, Claude Desktop and mobile, while desktop extensions install on Claude Desktop. On Team and Enterprise, an Owner or Primary Owner turns the connector on for the organisation before members can connect. For the current state of this one, check the connector's sheet in the official directory. As a desktop extension, this one is listed for Claude Desktop only.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you: nothing starts when a customer churns, a charge fails or MRR drops.
Everything here comes from Baremetrics' own documentation, the README of its public repository: neither Claude's help centre nor Anthropic's developer docs have a page on this connector. The tool list is an observed floor, not a promise, since an admin can open actions no public sheet shows. The directory's partner badge is not a security audit either, and Anthropic writes on every sheet that it does not choose the tools a publisher exposes nor guarantee how they behave. By default the sheet only exposes reading, and Baremetrics labels every tool read-only; that describes today's extension, not a promise about later versions.
Need help connecting Baremetrics to Claude?
A person reads every message.
