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 four integration layers AdsPower exposes, the recommendation for which to use, and a concrete end-to-end architecture + rollout plan.
The four 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 | 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 | AdsPower GUI drag-and-drop | Human operator in AdsPower UI | Bulk fixed-workflow runs (Phase 2+ scale lever) |
| 04 | Integration Plan | — | Rahul + Hermes | This synthesis — the actionable plan |
Layers 03 (MCP) and 03 (RPA) share one source doc because they are the two “automation” layers AdsPower offers; the integration plan in 04 explains how they complement each other.
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 | MCP architecture (TypeScript/Playwright/stdio), setup requirements, Reddit capability mapping, 6-step Hermes integration with config snippet, RPA overview (100-thread concurrency, scheduling, task logs), MCP-vs-RPA 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. |
Reading Order
- If you want the actionable plan only: read 00 (this file) → 04 (integration plan). The other three 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) 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 at /opt/data/skills/adspower-browser/ 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. It supports Docker deployment for the Hostinger VPS case. 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. 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 (Automation)
Two 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 is AdsPower’s built-in visual drag-and-drop process builder: compose a fixed workflow once (navigate → click → fill → submit → screenshot), then run it across up to 100 profiles concurrently via the GUI. RPA is high-volume but has no external trigger API — it cannot be called by Hermes directly; a human must trigger it in the AdsPower UI. Recommendation: hybrid. MCP Server as the primary AI-driven layer for research + adaptive engagement + comment authoring; RPA as the bulk-volume lever once a workflow is nailed down. Key risk flagged: AdsPower is a desktop app and cannot run on the Hostinger Linux VPS — it needs a Windows host reachable from Hermes.
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), whether to create a new adspower-operator Hermes profile or extend the existing reddit-marketer profile (concrete recommendation with rationale), 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 | /opt/data/skills/adspower-browser/ (14 reference files) + CLI help (ads -h) |
| 03-mcp-rpa.md | /opt/data/adspower_docs/extracted/MCP.txt + /opt/data/adspower_docs/extracted/rpa.txt |
| 04-integration-plan.md | Synthesis of 01 + 02 + 03 + Rahul’s GrowReach Reddit marketing context |
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 for Phase 2+ bulk volume. |
| Hermes profile strategy | Extend reddit-marketer, not a new adspower-operator profile. See 04 §2 for rationale. |
| AdsPower host | Windows machine (Rahul’s PC or a Windows VPS) reachable from the Hermes Hostinger VPS. MCP server runs on the VPS and points at the remote LocalAPI. |
| Phase 1 scope | 1 profile, manual trigger, MCP smoke test (launch → navigate → screenshot → stop). |