How Daloopa MCP Usage Is Counted

This guide explains what counts toward your monthly Daloopa MCP limit, what doesn't, and how the count resets.

The Short Version

Your monthly limit counts unique datapoints you access during the month.
Pulling the same datapoint again in the same month is free. It only counts once.
On the 1st of each month, the count resets to zero. A datapoint you pulled last month counts again the first time you pull it in the new month.

What Is a Datapoint?

A datapoint is a single financial value for a specific company, metric, and period. For example:

Apple's revenue for Q2 2026 is one datapoint.
Apple's revenue for Q1 2026 is a different datapoint.
Apple's net income for Q2 2026 is also a different datapoint.

So if you ask for one metric across four quarters, that's four datapoints.

Repeat Pulls in the Same Month Are Free

Once you've accessed a datapoint in a given month, pulling it again that month doesn't add to your count. You can re-run the same analysis, refresh a model, or ask Claude the same question several times without using up more of your limit.

Example (all within October):

Date	What you pulled	New datapoints	Running monthly total
Oct 2	Apple revenue, last 4 quarters	4	4
Oct 9	Apple revenue, last 4 quarters (same request again)	0	4
Oct 15	Apple revenue, last 8 quarters	4 (only the 4 older quarters are new)	8
Oct 20	Apple net income, last 4 quarters	4	12

Only datapoints you haven't touched yet this month increase the count.

The Count Resets Every Month

The monthly count resets on the 1st of each month (based on UTC time). After the reset, every datapoint is "new" again for that month, including ones you pulled the month before.

Example (continuing from above):

Date	What you pulled	New datapoints	Running monthly total
Nov 1	Monthly reset		0
Nov 3	Apple revenue, last 4 quarters (same as Oct 2)	4	4
Nov 5	Apple revenue, last 4 quarters (again)	0	4

The November 3 pull counts because it's the first time those datapoints were accessed in November, even though they were already pulled in October.

Your Limit vs. Your Firm's Limit

Depending on your account, the datapoint limit applies either:

To you individually, so only your own pulls count, or
To your whole firm, so the limit is shared with everyone at your company and their pulls count toward the same total.

When you check your usage, Claude will tell you which applies to you.

What About "Companies Accessed"?

Your usage summary may also show how many companies you've accessed. This number is for information only. It is not a limit and will never block you from pulling data. The datapoint count is the only limit that can.

How to Check Your Usage

Ask Claude in any chat:

What is my Daloopa MCP usage?

You'll get your datapoints used this month, your limit, what's remaining, and the date it resets.

Getting Regular Updates on Your Daloopa MCP Usage

There are three ways to keep an eye on your Daloopa MCP usage with Claude. They range from zero setup to fully automated.

Option	Setup effort	Runs automatically?	Best for
Ask Claude manually	None	No	Occasional checks
Claude Cowork scheduled task	Low	Yes	Non-technical users who want a regular update
Claude Code routine	Medium–High	Yes	Technical users already working in Claude Code

Before any option: the Daloopa connector must be connected on your own Claude account. Usage is tracked per person, so each person needs to set this up for themselves.

Option 1: Ask Claude Manually (Simplest)

Open any Claude chat and type:

What is my Daloopa MCP usage?

Claude will check the Daloopa connector and return a short summary: datapoints used this month, your limit, what's remaining, and when it resets.

If your plan has unlimited datapoints, an occasional manual check is usually enough.

Option 2: Claude Cowork Scheduled Task (Recommended for Non-Technical Users)

A scheduled task saves a prompt and runs it automatically on a schedule you choose (daily, weekly, etc.).

Requirements

A paid Claude plan (Pro, Max, Team, or Enterprise)
The Claude Desktop app
The Daloopa connector connected to your account

Steps

Open the Claude Desktop app and switch to Cowork.
Click Scheduled in the left sidebar.
Create a new scheduled task.
Paste the prompt below.
Choose how often it should run (daily or weekly) and click Save. Claude may ask a few multiple-choice questions first; just click through them.

Prompt to paste

Check my Daloopa MCP usage using the Daloopa connector. Give me a short,
plain-English summary: how many datapoints I've used this month, my limit,
how much I have left, and when it resets. If I'm at 80% or more of any
limit, flag it clearly at the top. Keep it to a few lines.

Managing it later

Go back to Scheduled in the sidebar anytime to view, pause, or delete the task.

Troubleshooting

Depending on your setup, scheduled tasks may only run while your computer is awake and the Claude Desktop app is open. If a run seems to be missing, check that first.

Full guide: Schedule recurring tasks in Claude Cowork

Option 3: Claude Code Routine (For Technical Users)

In Claude Code, the durable scheduling option is called a routine. Routines run on Anthropic's cloud, so they keep working even when your laptop is closed. They're available on Pro, Max, Team, and Enterprise plans.

Create from the terminal

Run this inside Claude Code:

/schedule every Monday at 9am, check my Daloopa MCP usage with the Daloopa
connector and summarize datapoints used, limit, remaining, and reset date.
Flag anything at 80% or more.

Claude will ask follow-up questions about the schedule, repositories, and prompt before saving.

Or create from the web

Go to claude.ai/code/routines, click New routine, and fill in the name, prompt, schedule, and connectors.

Why this is harder for non-technical users

Routines are designed around code projects. The setup asks you to select a GitHub repository and a cloud environment, and routines need GitHub access to run. That's a lot of unfamiliar setup just to get a usage number.

Important gotchas

Use a claude.ai connector, not a local one. MCP servers added in the terminal with claude mcp add live only on your machine and won't show up in routines. Make sure Daloopa is connected at claude.ai/customize/connectors.
Trim the connector list. All of your connected connectors are included in a routine by default, and Claude can use every tool in them (including ones that make changes) without asking during a run. For a usage check, remove everything except Daloopa.
Research preview. Routines are still in research preview, so behavior and limits may change.

Other Claude Code scheduling options (less suitable here)

/loop: reruns a prompt inside an open terminal session, but recurring tasks expire automatically after 7 days, so it isn't set-and-forget.
Desktop scheduled tasks: run on your own machine rather than in the cloud.

Full docs: Automate work with routines

Quick Recommendation

Non-technical user? Use Option 2 (Cowork), or just Option 1 when curious.
Already living in Claude Code? Option 3 works well; just keep the connector list to Daloopa only.