Client portalGet started

Built to be scripted.
By you or your agent.

A Local API and cloutctl for Clout Browser, MCP servers for AI assistants, and APIs for Hydra X and Studio VIP.

API referencecloutctl docs

cloutctl

Every profile from a terminal.

Import, list, launch and stop profiles from the command line; a launched browser keeps running after the command exits.

  • 81 commands with JSON output
  • Imports from five antidetect browsers
  • Runs anywhere with Node 24 or later
~/fleet
# every antidetect browser on this computer, with counts

MCP

Hand your assistant the browser.

Clout Browser’s MCP server gives Claude, Codex, Cursor and other clients 14 tools: list, start and stop profiles, manage folders and check proxies.

  • Setup shown for each client
  • Discovers the running Local API
  • Studio VIP and Hydra X have MCP too
Clout Browser new profile form with the identity summary

What comes with it

Local API

v1 routes that match AdsPower’s, plus v2 and v3, on your own computer.

Hydra X API

Scoped API keys, webhooks and an MCP server.

Studio VIP API

An API for your own tools and a read-only MCP server.

Tokens stay local

The MCP server reads the Local API token from your computer; the setup does not embed it.

Two engines

SunBrowser and Chroma, pinned per profile, managed for you.

Every platform

macOS, Windows and Linux, and cloutctl as its own download.

Questions

Will my AdsPower scripts work?
Yes: the Local API’s v1 routes match AdsPower’s for browsers, users and groups. Point them at Clout’s address and key.
Where is the full reference?
In the docs: the Local API, MCP and cloutctl references for Clout Browser, and the API chapters for Hydra X and Studio VIP.

Script your whole fleet.
Start with Clout Browser today.

Get startedClient portal