tgebrowser

TgeBrowser MCP Operations

Use MCP tools to operate TgeBrowser environments, groups, proxies, and browser automation via the mcp__tgebrowser__* tools.

When to Use This Skill

Apply when the user:

• Asks to create, update, delete, or list TgeBrowser environments
• Mentions opening or closing browsers/profiles, fingerprint, UA, or proxy
• Wants to manage groups, proxies, or check API status
• Needs browser automation (navigate, click, fill forms, screenshot, etc.)
• Refers to TgeBrowser or tgebrowser operations

Ensure TgeBrowser is running (default port 50326). The MCP server connects to the TgeBrowser Local API.

Smart Defaults & Best Practices

When creating browsers:

• Always use {"protocol": "direct"} for proxy if user doesn't specify one
• Default fingerprint OS to "Windows" if not specified
• Set webrtc: "disabled" by default for better privacy
• Use clearCacheOnStart: true for clean sessions

When opening browsers:

• Use args: ["--headless"] for automation tasks unless user needs to see the browser
• Let the system auto-assign port unless user specifies one

When automating:

• Always call mcp__tgebrowser__open-browser first and extract the ws URL from response
• Then call mcp__tgebrowser__connect-browser-with-ws with that ws URL
• After connection, you can use navigation and interaction tools

Error handling:

• If browser open fails, check if TgeBrowser app is running via mcp__tgebrowser__check-status
• If envId not found, list browsers first with mcp__tgebrowser__get-browser-list
• Before deleting cache, always close the browser first

Common Workflows

Quick Start: Create and Use a Browser

1. Create: mcp__tgebrowser__create-browser with minimal params (name + proxy)
2. Open: mcp__tgebrowser__open-browser with returned envId
3. Connect: mcp__tgebrowser__connect-browser-with-ws with ws URL from step 2
4. Automate: Use navigation/interaction tools
5. Close: mcp__tgebrowser__close-browser when done