Przejdź do treści
Biblioteka skilli
Programowanie · Integracja z narzędziem

setup-apify-insights

/setup-apify-insights

Instaluje, łączy, aktualizuje lub usuwa apify-insights-mcp, serwer tylko do odczytu z danymi o aktorach Apify twórcy.

Licencja
MIT
Ostatnia zmiana repozytorium
11.11.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
1
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
2
Przestarzałość

Brak sygnałów. Repozytorium zmienione 11.11.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Instaluje, łączy, aktualizuje lub usuwa apify-insights-mcp, serwer tylko do odczytu z danymi o aktorach Apify twórcy.

Wyzwalacze z opisu

set up the Apify MCP
Oryginalny opis (EN)

Install, connect, update or remove apify-insights-mcp, the read-only MCP server that answers an Apify creator's questions about their own actors (earnings, profit, failing or flagged actors, users, acquisition, quality scores, Store rank). Use when the user asks to install or set up apify-insights, connect their Apify account to Claude, Codex, Cursor, Gemini CLI, Grok Build or OpenCode, turn on revenue or money data, fix an apify-insights connection, or update or uninstall it, even if they only say "set up the Apify MCP".

Jak działa

  1. 1. Check the computer
  2. 2. Find the Apify token
  3. 3. Register the server with every client
  4. 4. Confirm it works
  5. 5. Offer money data (optional)
  6. Update or remove
  7. When it is done
Sekcje z nagłówków SKILL.md, w oryginale · 74 linii, 657 słów
Podgląd SKILL.md
---
name: setup-apify-insights
description: Install, connect, update or remove apify-insights-mcp, the read-only MCP server that answers an Apify creator's questions about their own actors (earnings, profit, failing or flagged actors, users, acquisition, quality scores, Store rank). Use when the user asks to install or set up apify-insights, connect their Apify account to Claude, Codex, Cursor, Gemini CLI, Grok Build or OpenCode, turn on revenue or money data, fix an apify-insights connection, or update or uninstall it, even if they only say "set up the Apify MCP".
---

# Set up apify-insights

The detailed reference is [docs/install.md](https://github.com/Devansh-365/apify-insights-mcp/blob/main/docs/install.md). Follow these steps, and read that page only when a step points there.

The repository may be private. If a link does not open, read the file with `gh` (`gh api repos/Devansh-365/apify-insights-mcp/contents/<path> --jq .content | base64 -d`) or from a clone.

The server only reads data. Nothing here changes the user's Apify account. Never print, log or paste the user's Apify token, and never write it into a file yourself: the Apify CLI login keeps it out of every config.

## 1. Check the computer

- `node -v` must print v20 or later. If not, ask the user to install Node.js 20+ and stop.
- `git ls-remote https://github.com/Devansh-365/apify-insights-mcp.git HEAD` must print a commit. If it fails, the user's git cannot reach the repository. Tell them to ask the owner for access, or to sign in to GitHub (`gh auth login`), and stop.

## 2. Find the Apify token

The server reads `APIFY_TOKEN`, then the Apify CLI login in `~/.apify/auth.json`. Check only that the file exists (`test -f ~/.apify/auth.json`). Do not read it.

If neither exists, the user runs the login, because it opens a browser:

```bash
npx -y apify-cli login
```

Use the CLI login rather than `APIFY_TOKEN` in a config: Gemini CLI strips variables with `TOKEN` in the name, and Codex passes no environment variables unless told to.

## 3. Register the server with every client

```bash
npx -y github:Devansh-365/apify-insights-mcp setup
```

This copies the server to `~/.apify-insights/app/index.js` and adds it to each client it finds:
- **Claude Code, Codex, Gemini CLI and Grok Build:** through their own `mcp add` command.
- **Cursor and OpenCode:** one entry merged into their JSON config.

Read its output line by line and tell the user what happened for each client:

- `added`: done.
- `could not add (...)`: the line below it is the exact command. Run it if the reason is something you can fix, such as a stale entry. If the reason is an old client version (for example `Unknown arguments`), tell the user to update that client.
- `is not plain JSON, left unchanged`: the config has comments. Add the printed entry to that file by hand, keeping its comments.

For a client that `setup` does not list (Claude Desktop, VS Code, Windsurf, Zed), use the matching section of docs/install.md. In Claude Desktop, the `.mcpb` file from the latest release installs with a double-click.

## 4. Confirm it works

The user restarts the client, or you run `/mcp` if your client supports it. Then call the `auth_status` tool. Expect `Apify API: connected as <username>`. If you are running inside the client you just set up and its tools are not loaded yet, ask the user to restart and say *"Check my apify-insights connection"*.

If something fails, use the "Check it works" table in docs/install.md.

## 5. Offer money data (optional)

Revenue, cost and profit need the bridge, a small Chrome extension that shares the user's Apify Console session. Ask before installing it. If they want it:

```bash
npx -y github:Devansh-365/apify-insights-mcp install
```

You cannot load a browser extension yourself, so give the user these steps:
1. Open `chrome://extensions` (or `brave://`, `edge://`, `arc://`) and turn on Developer mode.
2. Click **Load unpacked** and pick `~/.apify-insights/bridge`.
3. Stay logged in to console.apify.com in that browser.

Then call `auth_status` again: `Console session: ok` means the money tools work. `install` supports macOS and Linux only. On Windows, the public tools still work.

## Update or remove

- **Update:** run step 3 again. If the bridge is installed, run `install` again and ask the user to click reload on the extension.
- **Remove:** follow "Update or remove" in docs/install.md. Ask before deleting `~/.apify-insights`, because it also holds the usage log.

## When it is done

Tell the user which clients now have the server and whether money data is on. Then suggest a first question: *"How did my Apify actors do yesterday?"*

Wersje

W bazie nie ma innych skilli o nazwie setup-apify-insights.

Migawka bazy z 13.11.2026 · wersja paczki 9afd1e470e52 (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100apify-install-auth
    Instaluje i konfiguruje SDK Apify, CLI i uwierzytelnianie klienta API, w tym tokeny API, w nowym projekcie Apify.
  • 100apify-local-dev-loop
    Konfiguruje lokalne tworzenie aktorów Apify z Apify CLI i Crawlee: polecenie apify run, inspekcja lokalnego storage i szybki cykl develop-test-deploy.
  • 100apify-actorization
    Zamienia istniejące projekty w Apify Actory: JavaScript i TypeScript z SDK, Python z asynchronicznym menedżerem kontekstu lub dowolny język przez wrapper CLI.
  • 100apify-actor-development
    Tworzy, debuguje i wdraża Apify Actory, czyli bezserwerowe programy w chmurze do web scrapingu, automatyzacji i przetwarzania danych.
  • 100setup
    Instaluje, konfiguruje, aktualizuje lub usuwa t3-orchestration w projekcie w T3 Code, gdy użytkownik o to prosi.
  • 95Apify
    Zbiera dane z mediów społecznościowych, firm i sklepów przez aktory Apify i aktualizuje ich katalog.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.