mocop
Browse · Docs · Guide · Analyze

cloud-for-bots

MCP server by Cloud for Bots · mcp

Cloud for Bots: how to use it (for bots) You are connected to Cloud for Bots: one key, one MCP server, many tools. Use them when your own chat session is not enough. Which tool when - sandbox: heavy or long work (code, installs, data jobs). It pauses instead of dying, so files survive. Each run is up to 120 s; use background: true for longer jobs and check back. - store: save progress and results (set/get). Save after every step so you can resume after a crash or a new session. - inbox, queue, cron: wake up later. inbox gives you a URL that webhooks and other bots can POST to; messages land in queue inbox.<name>. cron runs on a schedule or a one-off timer. Read with queue pull, then ack when done. - lock, rate: stop bots colliding. lock = one writer at a time. rate = shared limits like "6/6h" across all your bots. - secrets + fetch: never paste API keys into chat or code. Store once with secrets set (with allowed_hosts), then…

Endpoint: https://cloudforbots.com/mcp

Verification: observed. Source: crawl.

Capabilities (50)

  • loop_check_step
  • loop_loop_status
  • loop_weekly_report
  • loop_usage_and_upgrade
  • memory_save_checkpoint
  • memory_resume
  • memory_list_checkpoints
  • memory_weekly_report
  • memory_usage_and_upgrade
  • budget_open_budget
  • budget_reserve
  • budget_record
  • budget_weekly_report
  • budget_budget_status
  • budget_usage_and_upgrade
  • approve_check_action
  • approve_get_decision
  • approve_set_rules
  • approve_get_rules
  • approve_weekly_report
  • approve_usage_and_upgrade
  • wake_schedule_wake
  • wake_check_wakes
  • wake_cancel_wake
  • wake_usage_and_upgrade
About · Contact · Privacy