Loading documentation
Real workflows from power users: saved workspaces bound to a task, one profile per identity, keyboard-first navigation, and knowing when to hand a job to automation instead of doing it by hand.
The same few patterns come up again and again: one profile per identity, one workspace per task, and a saved layout for anything you reopen more than twice. The workflows below each combine profiles, tiling, and workspace restore rather than relying on a single feature.
Create separate profiles for different research contexts. Each has its own proxy, cookies, history, and bookmarks. Nothing bleeds between contexts. Use folders or tags to organize within a profile, and the All Profiles view to search across all of them at once.
Let auto-tiling build your grid, then lock it to prevent accidental changes.
Control multiple browsers simultaneously with the REST API's batch endpoint.
Connect Claude or another AI assistant via MCP to automate complex multi-browser workflows.
Build a complete trading dashboard in under 30 seconds.
Use bookmarks and batch operations to avoid tab overload during research.
Eliminate context-switching friction by creating a workspace for each role.
Navigate MetaDock entirely from the keyboard.
Quickly review what you've customized.
Combine browsers and native apps (Beta) in a single workspace.
MetaDock Pro offers 5automation protocols. Here's how to pick the right one for your task:
| Use Case | Best Protocol |
|---|---|
| AI assistant control (Claude, Cursor) | MCP: the AI sends tool calls to control MetaDock |
| Simple scripts (Python, curl, bash) | REST API: standard HTTP requests, easy to write |
| Real-time event monitoring | WebSocket: subscribe to events, get instant notifications |
| Existing Selenium test suites | WebDriver: drop-in W3C compatible, minimal code changes |
| Low-level browser debugging | CDP: full DevTools Protocol, use Puppeteer or Playwright |
| Complex multi-step automation | REST API + WebSocket: commands via REST, events via WebSocket |
Get the most out of MetaDock with these performance practices:
Instead of making 10 separate API calls to navigate 10 browsers, use a single batch request. The batch endpoint supports up to 100 operations per browser. This is dramatically faster and reduces network overhead.
If you need to know when a page finishes loading, subscribe to WebSocket events instead of polling the REST API in a loop. WebSocket delivers events instantly with zero wasted requests.
Running automation across multiple accounts? Use a separate profile for each. This prevents cookie/cache conflicts and ensures each browser instance is truly independent.
Press F9 to lock your layout before running automation scripts. This prevents accidental panel rearrangement if a script interaction triggers a drag event.