AdsPower Knowledge Base — Index
Root index for the AdsPower integration knowledge base. Start here. Audience: Rahul / GrowReach Reddit marketing automation via Hermes Agent. Generated: 2026-07-19 (kanban task t_02d15aad).
Purpose
This KB is the consolidated reference for integrating AdsPower (anti-detect multi-profile browser) with Hermes Agent to drive Reddit marketing at scale for GrowReach. It covers the integration layers AdsPower exposes, the recommendation for which to use, and a concrete end-to-end architecture + rollout plan.
The layers, from lowest to highest abstraction:
| # | Layer | Interface | Who drives it | In-scope for Hermes Reddit workflow |
|---|---|---|---|---|
| 01 | Local API (REST) | HTTP on localhost:50325 (app) / :50725 (CLI runtime) | Any HTTP client | Foundation — wraps every other layer |
| 02 | CLI (ads / adspower-browser skill) | Shell + Hermes skill | Hermes terminal | Profile farm management (create/open/close/proxy/fingerprint) |
| 03 | MCP Server | stdio MCP tools (TypeScript + Playwright) | AI agent (Hermes) | In-browser automation: navigate, click, fill, screenshot |
| 03 | RPA Plus | AdsPower GUI node-based process builder | Human operator in AdsPower UI | Bulk fixed-workflow runs (up to 100 threads / 5,000 profiles) |
| 03 | Synchronizer | AdsPower GUI multi-window sync | Human operator in AdsPower UI | Manual multi-account operations (warming, coordinated logins) |
| 04 | Integration Plan | — | Rahul + Hermes | This synthesis — the actionable plan |
Layers 03 (MCP), 03 (RPA Plus), and 03 (Synchronizer) share one source doc because they are the three “automation” layers AdsPower offers; the integration plan in 04 explains how they complement each other. RPA Plus detail lives in
06-rpa-plus-reference.md, Synchronizer in07-synchronizer.md.
Table of Contents
| File | Layer | What it covers |
|---|---|---|
| 00-index.md | — | This index. Overview + layer summaries + reading order. |
| 01-local-api.md | REST API | Authentication, base URL, rate limits, 43 endpoints, v1 vs v2, deep-dives for the 4 most important endpoints, user_proxy_config + fingerprint_config appendices, Reddit workflow API mapping. |
| 02-cli-skill.md | CLI + Hermes skill | Install/aliases, auth, full 32-command catalog, inline config objects, Docker usage, EN+ZH intent-mapping table, the CRITICAL CLI ≠ browser-automation boundary, Reddit profile-farm workflow. |
| 03-mcp-rpa.md | MCP Server + RPA Plus | MCP architecture (TypeScript/Playwright/stdio), setup requirements, Reddit capability mapping, Hermes integration (already live — 47 mcp__adspower__* tools), RPA Plus overview (node canvas, variables, if/loops, data processing, third-party tools, 100-thread concurrency, 5,000 profiles/task, scheduling, task logs), MCP-vs-RPA-Plus comparison table, hybrid recommendation. |
| 04-integration-plan.md | Synthesis | The deliverable. Layer recommendation, profile recommendation, end-to-end architecture, MCP setup commands, Reddit engagement pseudo-workflow, risks & mitigations, 3-phase rollout. |
| 05-profile-recommendation.md | Hermes profile | adspower-operator profile: skills, MCP servers, toolsets, env vars, delegation flow. |
| 06-rpa-plus-reference.md | RPA Plus reference | Comprehensive RPA Plus reference: RPA vs RPA Plus, core concepts (process/task/task log/marketplace), process editor, all 8 operation categories, variables (system/global/process), control flow, selectors (CSS/XPath/Text), sharing codes + import/export, task management, error handling, headless mode, timeout/delayed execution, official use-case templates. |
| 07-synchronizer.md | Synchronizer | Multi-window sync: main vs controlled window, window management (tile/grid/overlapped/uniform/layout), text sync (identical/designated/type-as-human/random numbers), tab control, sync actions, multi-screen sync, group filtering, settings. |
Reading Order
- If you want the actionable plan only: read 00 (this file) → 04 (integration plan). The others are reference.
- If you are implementing profile management: read 01 (REST) and 02 (CLI) side-by-side — the CLI wraps the REST API one-to-one.
- If you are implementing browser automation: read 03 (MCP/RPA Plus) then 04 §4 (MCP setup commands).
- If you are onboarding a new operator: read 00 → 04 → 02 (CLI commands you’ll run daily) → 03 (MCP for the AI-driven engagement).
Layer Summaries
Layer 01 — Local API (REST)
The Local API is a REST HTTP service running on the machine where the AdsPower client is installed (default http://localhost:50325). It is the foundation every other layer wraps. Authentication is a Bearer token (API key generated in the AdsPower client). The catalog spans 43 endpoints across Profiles (29), Tags (4), Groups (3), Proxies (4), Extensions (2), and Connection Status (1). Profile count drives the rate limit: 2 req/sec at 0–200 profiles, 5 at 200–5k, 10 at 5k+. Five endpoints (profile list, group list, cookies, kernel download) are fixed at 1 req/sec regardless. The Open Profile endpoint returns a WebSocket/Debug Port that bridges profile management to browser automation — that bridge is what the MCP server consumes to attach Playwright. Recommendation: use v2 endpoints wherever available (better filtering, multi-account platform support, batch ops).
Layer 02 — CLI + Hermes Skill
The adspower-browser npm package exposes the Local API as a shell CLI with three aliases (adspower-browser, adspower, ads). It is also installed as a Hermes skill with 14 reference files, so Hermes can run any command directly from the terminal. The CLI covers 32 commands: profile CRUD, open/close, cookies, UA, fingerprint rotation, cache clearing, sharing, groups, tags, proxies, kernels, and patch updates. Critical boundary: the CLI manages profile lifecycle (create/open/close/proxy/fingerprint/cookies) but CANNOT do in-page automation (navigate, click, fill, screenshot) — that requires the MCP server or RPA Plus. For the Reddit workflow, this layer is the profile farm backbone: create N isolated Reddit accounts, each with unique proxy + fingerprint, rotate fingerprints periodically, clear sessions between campaigns, launch profiles, and hand the returned WebSocket endpoint to the MCP layer for the actual engagement actions.
Layer 03 — MCP Server + RPA Plus + Synchronizer (Automation)
Three complementary automation layers. MCP Server (local-api-mcp-typescript, TypeScript + Playwright, stdio transport) exposes AdsPower’s LocalAPI as MCP tools so an AI agent like Hermes can drive browser actions via natural language: launch profile → navigate to Reddit post → click upvote → fill comment → screenshot → switch profile. It is adaptive (AI decides what to engage, writes context-aware comments, recovers from errors) but sequential and AI-paced. RPA Plus is AdsPower’s built-in visual node-based process builder: compose a workflow once (navigate → click → fill → submit → screenshot) with variables, if/loops, data processing, and third-party tools, then run it across up to 100 threads / 5,000 profiles concurrently via the GUI. RPA Plus has no external trigger API — it cannot be called by Hermes directly; a human must trigger it in the AdsPower UI. Synchronizer is a manual multi-window sync tool (actions in the main window replicate across controlled windows) — human-only, not scriptable. Recommendation: hybrid. MCP Server as the primary AI-driven layer for research + adaptive engagement + comment authoring; RPA Plus as the bulk-volume lever once a workflow is nailed down. On this setup, AdsPower runs directly on the same Windows VPS as Hermes (Local API :50325 app / :50725 CLI runtime) — no remote host needed.
Layer 04 — Integration Plan (this synthesis)
The actionable plan that ties layers 01–03 together for GrowReach Reddit marketing. Covers: which layers to use for which use case (recommendation table), the adspower-operator Hermes profile (created and in use), end-to-end architecture showing Hermes orchestrating CLI → MCP → CLI across a profile batch, exact hermes mcp add config for the AdsPower MCP server, step-by-step Reddit engagement pseudo-workflow with rate-limiting and anti-detection guidance, risks & mitigations (ban risk, fingerprint detection, IP rotation, comment quality), and a 3-phase rollout (MVP → cron-driven 3-5 profiles → scale + monitoring).
Source Map
| KB file | Source material |
|---|---|
| 01-local-api.md | AdsPower help page (api.txt) + Postman API reference (browser-rendered) |
| 02-cli-skill.md | adspower-browser skill reference files (14 files) + CLI help (ads -h) |
| 03-mcp-rpa.md | AdsPower MCP help page + MCP blog post + RPA Plus User Guide (rpa-plus-doc-en.adspower.com) |
| 04-integration-plan.md | Synthesis of 01 + 02 + 03 + Rahul’s GrowReach Reddit marketing context |
| 06-rpa-plus-reference.md | All 26 pages of rpa-plus-doc-en.adspower.com |
| 07-synchronizer.md | https://help.adspower.com/docs/synchronizer |
Decisions (quick reference — full rationale in 04-integration-plan.md)
| Decision | Recommendation |
|---|---|
| Primary automation layer | MCP Server (AI-driven, adaptive, callable by Hermes). CLI for profile management. RPA Plus for Phase 2+ bulk volume. |
| Hermes profile strategy | adspower-operator profile — created and in use (see 05-profile-recommendation.md). |
| AdsPower host | Same Windows VPS as Hermes (EC2, C:\Users\Administrator). Local API on localhost:50325 (app) / :50725 (CLI runtime). MCP server runs locally. |
| Phase 1 scope | 1 profile, manual trigger, MCP smoke test (launch → navigate → screenshot → stop). |