Skip to main content
Glama
apify-insights

apify-insights

by Devansh-365
README.md
<p align="center">
  <img src="docs/assets/cover.png" alt="apify insights: ask your AI about your Apify actors. Earnings, losses, broken runs and Store rank, over MCP. An example search, which actors lose money, returns an actor with its profit and break-even price." width="100%">
</p>

<h3 align="center">Find the Apify actors that lose money, leak users or need a fix.</h3>

<p align="center">
  Ask your AI about your own account and get exact numbers back:<br>
  profit, break-even prices, failing runs, quality fixes and Store rank.<br>
  <sub>Works in Claude, Codex, Cursor, Gemini, Grok and OpenCode.</sub>
</p>

<p align="center">
  <img alt="MCP server" src="https://img.shields.io/badge/MCP-server-246dff?style=flat-square">
  <img alt="Read-only" src="https://img.shields.io/badge/read--only-safe-1f9a4b?style=flat-square">
  <img alt="Node 20+" src="https://img.shields.io/badge/node-20%2B-e85d04?style=flat-square">
  <img alt="MIT license" src="https://img.shields.io/badge/license-MIT-1a1714?style=flat-square">
  <a href="https://github.com/Devansh-365/apify-insights-mcp"><img alt="Star on GitHub" src="https://img.shields.io/badge/GitHub-star-e3b341?style=flat-square&logo=github&logoColor=white"></a>
</p>

## 💬 What you can ask

| Ask | You get |
|---|---|
| *"How did I do yesterday?"* | Profit against the same days last month, plus the 3 actors to look at |
| *"Which actors lose money?"* | Each one with the price where it would break even |
| *"Is anything broken?"* | Actors that fail, that Apify flagged, or that charge nothing |
| *"Which actors had failed runs this week, and on which days?"* | Failed, timed-out and aborted runs per day and today so far; for one actor, the failed runs users shared, their last log lines and the build before it started |
| *"Tell me about maps-scraper"* | Users, runs, price, builds, reviews and 3 months of money |
| *"Which actors are leaking users?"* | Each actor marked Leaking, Rising, Fading or Converting, with the reason and what to do |
| *"What should I fix for quality?"* | Apify's quality suggestions across your actors, ranked by impact |
| *"Where do I rank for tiktok scraper?"* | Your Store search position and who ranks above you |
| *"Compare me with another creator"* | Your public portfolio next to theirs |

## ⚡ Install

**Let your AI agent do it.** Paste this into Claude Code, Codex, Cursor, Gemini CLI or OpenCode:

```text
Set up apify-insights for me by following https://github.com/Devansh-365/apify-insights-mcp/blob/main/skills/setup-apify-insights/SKILL.md
```

**Or run two commands yourself** (needs Node.js 20+):

```bash
npx -y apify-cli login                               # once: connects your Apify account
npx -y github:Devansh-365/apify-insights-mcp setup   # adds it to every AI client you have
```

Restart your AI client and ask *"How did my Apify actors do yesterday?"*

Revenue and profit need a small Chrome extension. Claude Desktop, one-click installs for single clients, updates and fixes are all in **[docs/install.md](docs/install.md)**.

## 💡 Good to know

- **Read-only.** It never changes anything in your Apify account.
- **Runs on your computer.** It talks only to Apify, and your token stays in the Apify CLI login.
- **No guessing.** A number it cannot get shows as "not available", never as zero.
- Every tool and how each metric is worked out: [docs/tools.md](docs/tools.md).

## 🛠️ Development

```bash
npm test             # tests on made-up data
npm run build        # bundles src/ into dist/index.js (committed, so rebuild before you commit)
npm run check:dist   # fails if dist/index.js is out of date
npm run pack:mcpb    # builds the Claude Desktop extension
```

Why it installs this way: [ADR 0001](docs/adr/0001-multi-client-distribution.md). Release notes: [CHANGELOG.md](CHANGELOG.md).

## 📄 License

[MIT](LICENSE), by Devansh Tiwari.

<p align="center">
  <sub>If it saves you a trip to the Apify Console, a ⭐ helps other creators find it.</sub>
</p>

TDQS

A3.7/5.0

Scored across 12 tools

Disambiguation4/5

Most tools target a distinct analysis axis (money, health, quality, acquisition, search rank, competition), and descriptions explicitly disambiguate the risky pairs, e.g. growth vs acquisition_score ('same numbers and field names as growth; for raw counts... use growth') and revenue_summary vs daily_brief. There is still a cluster of four tools answering 'which actors need attention' (run_health, actor_quality, acquisition_score, daily_brief) that an agent could plausibly misselect, though the rule sets differ enough to be workable.

Naming Consistency3/5

All names are snake_case and readable, but conventions differ: verb_noun (list_actors), noun_noun (auth_status, revenue_summary, run_health, actor_report), and bare noun phrases (growth, store_rank, competitor_benchmark). The actor_ prefix is used for some actor-scoped tools but not others (actor_profitability vs growth), so the namespace is inconsistent.

Tool Count5/5

Twelve tools is squarely in the well-scoped range, and each maps to a coherent analytics question (one actor, all actors, money, health, quality, rank, competitor) rather than redundant variants. Nothing feels padded.

Completeness4/5

The analytics domain is well covered end-to-end: auth, portfolio listing, per-actor deep dive, revenue/cost/margin, run health, quality, acquisition, store rank, and benchmarking, spanning both overview and drill-down. Minor gaps remain around longitudinal trending/export of metrics and explicit remediation or alerting actions, but agents can work around these via period parameters and date ranges.

Maintenance

ActivityNo data
ResponsivenessOutdated data