Profile Management
Manage browser profile lifecycle and configuration.
- List Profiles
- Create Profile
- Update Profile
- Start Profile
- Stop Profile
- Delete Profile
- Check Status
Use the MasBrowser Local API to programmatically manage browser profiles, groups, and proxies, then connect Selenium, Puppeteer, and supported AI workflows.
When profile creation, launch, proxy configuration, and status checks depend on manual clicks, larger workflows become slower and harder to integrate.
More tasks lead to more repeated clicks
Large profile sets require repeated opening, closing, and maintenance.
Without a standard local interface, systems need additional adapters.
Profiles, groups, and proxies may be duplicated across tools.
UI-only management becomes inefficient as task volume grows.
Expose profile, group, and proxy operations through a local interface for scripts and internal systems.
Use one local interface for the core resources required by browser automation.
Manage browser profile lifecycle and configuration.
Maintain profile organization through the API.
Maintain proxies used by browser workflows.
After starting a profile, retrieve the Puppeteer WebSocket, Selenium debuggerAddress, local WebDriver path, and Debug Port for your existing scripts.
Install and connect the MasBrowser Skill to manage profiles, groups, and proxies through natural language. Skill and Local API Key access require the Professional plan or above.
MasBrowser Skill and Local API Key require the Professional plan or above. Actions remain limited by team member permissions.
The Local API listens only on 127.0.0.1 and does not directly expose itself to LAN or internet clients. API Key checks add another control layer.
127.0.0.1:30520API KeyExternal networks cannot connect directly
The service listens on 127.0.0.1, so external networks cannot connect directly.
When security validation is enabled, requests must provide a valid API Key.
Refreshing a key immediately revokes the previous key.
API actions inherit the signed-in desktop account and member permissions.
Skill credentials are stored for the current system user and removed when disconnected.
Start the desktop client to use the Local API locally, enable API Key validation, or connect the MasBrowser Skill.

Open Local API from the API entry in the MasBrowser desktop client. No separate service deployment is required.
Control profiles, proxies, and groups through one API and connect browser work to scripts, frameworks, and supported AI tools.
Turn browser profiles into local resources your system can schedule and control.
Control profile lifecycle through scripts.
Retrieve debugging connections for existing scripts.
Connect profile, proxy, and group management to internal workflows.
Use natural language for controlled local operations.
Review the Local API documentation for profiles, groups, proxies, and automation connections.
Use the Local API when isolated browser profiles need to become part of an existing process.
Control isolated profiles with Python, Selenium, and Puppeteer.
Programmatically start and manage many browser profiles.
Connect profile, proxy, and group operations to internal platforms.
Use MasBrowser Skill for supported natural-language local calls.
Local API works with isolated profiles, proxies, groups, team collaboration, and automation in one anti-detect browser.
Give each task its own browser profile and configuration.
Manage profiles, proxies, groups, and collaboration centrally.
Connect scripts through local debugging interfaces.
Keep actions within current account and member permissions.
Understand local access, framework connections, plans, and permission boundaries.
It can list, create, update, start, stop, and delete browser profiles, and manage groups and proxies. Proxy create and update operations support connectivity checks.
Yes. A start response can provide the Puppeteer WebSocket, Selenium debuggerAddress, local WebDriver path, and Debug Port.
No. It listens on 127.0.0.1 and is not directly available to LAN or internet clients.
Generating, refreshing, and copying API Keys, and connecting MasBrowser Skill, require the Professional plan or above.
No. API operations inherit the permissions of the account signed into the desktop client.
Yes. Profiles can start in headless mode or with a visible browser window.
Get Started with MasBrowser Local API
Connect MasBrowser to automation systems and supported AI workflows with less manual work.