Loading documentation
MetaDock ships a built-in Model Context Protocol (MCP) server, so AI assistants like Claude Desktop, Claude Code, and Cursor can drive your real, logged-in browsers, layouts, and profiles in plain English. It exposes 172 tools covering navigation, interaction, capture, and multi-browser orchestration.
The Model Context Protocol is an open standard that lets AI assistants call external tools through one consistent interface. MetaDock registers itself as an MCP server, and any MCP-compatible client can then act on your browsers on your behalf.
Open Settings → API & Automation and click Install to desktop tools. MetaDock detects the MCP clients you have installed, writes the connection into each one's config for you, and turns on the matching connection. No hand-editing JSON, and no need to find the install path yourself.
It can install into:
The dialog offers two connection types. Local CLI (recommended) wires up the stdio command below and needs no API key. HTTP server uses the local endpoint with a generated key. Install a single tool, or install into all detected tools at once.
Your client launches MetaDock's stdio MCP server and talks to it over standard input/output, so there is no port, URL, or API key to manage. The command must be the full path to metadock.exe in your MetaDock install folder (a bare metadock.exe only works if that folder is on your PATH).
| Field | Value |
|---|---|
| Command | Full path to metadock.exe (in the install folder) |
| Args | ["mcp"] |
| Transport | stdio |
| Auth | Local. The client launches the process, no key needed |
{
"mcpServers": {
"metadock": {
"command": "C:\\Program Files\\MetaDock\\metadock.exe",
"args": ["mcp"]
}
}
}Connect over HTTP when your client prefers a URL. First enable MCP under Settings → API & Automation and create an API key there, then point your client at the local endpoint.
| Field | Value |
|---|---|
| Protocol | MCP 2025-06-18 |
| Endpoint | http://localhost:8080/mcp |
| Transport | Streamable HTTP |
| Auth | Bearer API key |
{
"mcpServers": {
"metadock": {
"url": "http://localhost:8080/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}YOUR_API_KEYwith a key from the API & Automation settings. Treat it like a password: anything holding it can drive your logged-in browsers.MetaDock exposes 172 tools, grouped by area. The full list ships with the app and is advertised to your client on connect.
| Group | What it covers |
|---|---|
| Navigation | Go to URL, back/forward, reload, stop |
| Page info & source | URL, title, HTML source, full browser state |
| Interaction | Click, type, set values, submit forms, scroll |
| JavaScript & injection | Execute JS, inject CSS/JS, read & clear console |
| Capture | Screenshots and print-to-PDF |
| Cookies | Set, get, list, delete, and clear cookies |
| Settings & DevTools | User agent, viewport, zoom, open/close DevTools |
| Device emulation | Emulate devices, geolocation, offline, headless |
| Wait & batch | Wait for element or load, batch many operations |
| Browser management & bulk | Create/list browsers, act on all at once |
| Layouts | List, create, delete, rename, inspect layouts |
| Profiles | List, create, delete, temporary profiles, proxies |
| Workspaces | List, switch, create, rename, set homepage & startup |
Alongside tools, MetaDock publishes read-only resources: browser state, HTML source, console messages, and cookies per browser, plus layout, workspace, profile, and system status.