Developer documentation

Connect local scripts and MCP clients to the running TabGecko desktop application. These guides cover setup, permissions, profile operations and the boundaries of automation and transfers.

Choose an interface

Interface	Use it for
Native Local API	New integrations using HTTP, JSON and explicit token scopes.
MCP	Clients that discover and call tools. HTTP and a Node.js stdio bridge use the same local application.
AdsPower compatibility	Existing scripts using the supported AdsPower-style routes on a separate optional listener. It is not the native API.

Start with a read-only connection

Set up a local token and verify the address → Create, inspect, start and stop profiles → Connect an MCP client

Browse the complete generated API reference · Download OpenAPI, Postman, CLI and Skill

Version and scope

The reference snapshot describes API version 0.5.12 with 320 operations. This snapshot follows the development build; an older installer can expose fewer operations even under the same version number. The running application’s authenticated /openapi.json and MCP tools/list are authoritative. Missing response schemas are marked explicitly.

This documentation does not enable a cloud API, grant a subscription entitlement or announce an installer release. Local tokens and website accounts are separate.