Apify Status and Cost History

VerifiedSafe

Shows current Apify/mcpc session state and run cost history. Use when checking Apify usage, mcpc session status, costs, or reviewing recently run actors.

Sby Skills Guide Bot
DevelopmentBeginner
306/2/2026
Claude Code
#apify#mcpc#session-status#cost-tracking#actor-runs

Recommended for

Our review

Displays current Apify/mcpc session state and historical run costs.

Strengths

  • Quick overview of connected MCP sessions
  • Automatically sums total spending across all actor runs
  • Zero manual setup required for cost tracking

Limitations

  • Only works if mcpc and the cost log file are present
  • The cost log file is only created after the first run with --json
When to use it

Use this skill when you need to check the status of your Apify MCP connections or review the cost history of your actor runs.

When not to use it

Do not use it to set up new MCP sessions or to execute Apify actors directly.

Security analysis

Safe
Quality score85/100

The skill only executes read-only Bash commands (mcpc, tail, awk) to display session status and cost history. No external network calls, no file modification, no destructive actions, and no sensitive data exfiltration.

No concerns found

Examples

Show current sessions
Show me which mcpc sessions are active right now.
Show cost history
What are my recent Apify costs and total spending?
Show all status information
Give me the full Apify status including sessions and costs.

name: apify-status description: "Shows current Apify/mcpc session state and run cost history. Use when the user asks about their Apify usage, mcpc session status, costs, or wants to see what actors were run recently." allowed-tools: Bash(mcpc *), Bash(tail *), Bash(awk *) argument-hint: "[sessions | costs | all]"

apify-status

Run the following commands and present the results to the user.

Sessions

Current mcpc sessions (shows which MCP servers are connected):

mcpc

Cost history

Recent actor runs (last 20 entries from cost log):

tail -n 20 ~/.apify-costs.log

Total spend across all logged runs:

awk -F'\t' '{match($0,/usd=([0-9.]+)/,a); sum+=a[1]} END{printf "Total: $%.4f USD\n", sum}' ~/.apify-costs.log

If either cost command fails (file not found), inform the user that cost tracking starts automatically once they run an actor with call-actor ... --json. No manual setup needed.

Notes

  • Cost log: ~/.apify-costs.log — auto-populated by a PostToolUse hook on every call-actor --json call. Override path with $APIFY_COST_LOG.
  • Sessions: managed via mcpc mcp.apify.com connect @apify. If sessions are missing, run the setup commands from the /apify-mcpc skill README.
Related skills