# MCP Server

Source: https://metadock.app/docs/mcp

# MCP Server

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.

## What is MCP?

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.

-   •Automate browser tasks — navigate, click, type, scroll, submit forms, run scripts
-   •Orchestrate many browsers — create and control dozens of instances at once
-   •Manage workspaces & layouts — create, switch, tile, and restore whole setups
-   •Extract data — read page content, state, console, cookies, and screenshots

Note

MCP acts on the browsers and workspaces in your **running** MetaDock, on your own machine. Keep the app open while your client is connected.

## Install to desktop tools (easiest)

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:

-   •Cursor
-   •Claude Code
-   •Claude Desktop
-   •VS Code
-   •Windsurf
-   •Codex
-   •Antigravity

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.

Tip

Prefer to wire it up by hand? The two sections below show the exact config for each connection type. They are the same entries the installer writes.

## Manual setup: command (stdio)

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

json

```
{
  "mcpServers": {
    "metadock": {
      "command": "C:\\Program Files\\MetaDock\\metadock.exe",
      "args": ["mcp"]
    }
  }
}
```

Note

The path above is an example. Use wherever MetaDock is installed on your machine. Codex uses TOML rather than JSON, but the same command/args apply. The **Install to desktop tools** button fills the correct path in automatically.

## Manual setup: Streamable HTTP

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

json

```
{
  "mcpServers": {
    "metadock": {
      "url": "http://localhost:8080/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}
```

Warning

Replace `YOUR_API_KEY`with a key from the API & Automation settings. Treat it like a password: anything holding it can drive your logged-in browsers.

## Tools & resources

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.

## Good to know

-   •Available on every plan — Explorer 10,000 calls/month, MetaDock 50,000, MetaDock Pro unlimited
-   •Works with any MCP client — the installer covers seven; anything implementing the spec can connect manually
-   •Both connection types coexist — run stdio and HTTP at the same time for different clients
-   •It drives real browsers — review important actions before you run them, just as you would any tool with that access

Note

Want the marketing overview, use cases, and the full tool breakdown? See the [MCP Server page](https://metadock.app/mcp).