# Browser Proxy
SUMMARY: Browser automation service — separate Docker container on port 13000 for headless browser control.

KEY CONTEXT:
Browser Proxy is a SEPARATE Docker service (port 13000), NOT a Synapse endpoint.
Synapse endpoints do NOT include /browser/* paths.
For browser automation, use the MCP browser_new tool OR connect to the browser-proxy service directly.
Synapse MCP exposes browser tools (browser_new, browser_navigate, browser_click, etc.)

Browser Proxy
The Browser Proxy is a separate Docker service that provides headless
browser automation via Playwright. It is NOT part of the Synapse API directly —
Synapse endpoints do not include  paths.
Architecture
[CODE BLOCK]
Access Methods
Method 1: Via Synapse MCP Server (recommended)
The Synapse MCP server exposes browser tools as MCP tools. Use this for
LLM-driven browser automation:
[CODE BLOCK]
Available MCP browser tools:
-  — open a new browser tab
-  — navigate to a URL
-  — click an element
-  — type text into a field
-  — capture a screenshot
-  — close the tab
- (and more — see MCP integration)
Method 2: Direct Browser Proxy Access
For non-MCP integrations, connect directly to the browser-proxy service:
[CODE BLOCK]
Common Use Cases
Web scraping
[CODE BLOCK]
Form automation
[CODE BLOCK]
Screenshot capture
[CODE BLOCK]
Related Services
| Service | Port | Purpose |
|---------|------|---------|
| Synapse API | 12800 | Memory, chat, tasks |
| Synapse MCP | 13100 | MCP server (79 tools) |
| Browser Proxy | 13000 | Headless browser automation |
| SSH Proxy | 12900 | SSH access to remote machines |
Next Steps
- MCP Integration — how to use browser tools via MCP
- Computer Control API — for GUI automation on registered machines