Let Claude, Claude Code, or Cursor drive real browsers
MetaDock implements the Model Context Protocol (MCP), enabling AI assistants like Claude Desktop, Claude Code, and Cursor (and any MCP-compatible tool) to programmatically control browser automation, workspace management, and multi-browser orchestration.
198 production-ready MCP tools for complete browser control. Add one line to your MCP config and your AI has a real browser.
Headless browsers are headless for a reason.
Debugging automation you cannot see. Logs and screenshots instead of watching it run.
Cloud browser costs ballooning with per-hour billing.
No visual feedback when your scraper hits a captcha or layout change.
What is MCP?
The Model Context Protocol is an open standard that lets AI assistants drive external applications through one common interface. MetaDock implements it as a server, so an assistant can automate browser tasks, orchestrate many browsers at once, manage workspaces, extract page data, and chain those into multi-step workflows.
In practice that means you can:
- •Automate browser tasks - Navigate, click, type, scroll, and interact with web pages
- •Orchestrate multiple browsers - Control many browser instances simultaneously; the REST bulk route accepts up to 50 browsers in one request
- •Manage workspaces - Create, switch, and organize different work environments
- •Extract data - Get page content, screenshots, and browser state information
- •Build AI workflows - Let your AI assistant handle complex multi-step browser automation
How do I connect my AI client to MetaDock?
MetaDock speaks MCP over two transports: stdio, where your client launches metadock.exe itself and needs no port or key, and Streamable HTTP on a local endpoint. Pick whichever your client prefers, or run both at once. The one-click installer configures the stdio option for seven desktop clients.
Option 1: Command (stdio)
How it works
MetaDock ships a built-in stdio MCP server. Your client launches it for you and talks to it over standard input/output, so there is no port to open, URL to configure, or API key to manage.
The one-click Install to desktop tools option sets this up automatically for Cursor, Claude Code, Claude Desktop, VS Code, Windsurf, Codex, and Antigravity.
…\MetaDock\metadock.exe mcpstdioLocal (no key)Claude Desktop Config
{
"mcpServers": {
"metadock": {
"command": "C:\\Users\\YOU\\AppData\\Local\\MetaDock\\bin\\metadock.exe",
"args": ["mcp"]
}
}
}command must be the full path to metadock.exe. MetaDock installs per-user rather than into Program Files, so the default is %LOCALAPPDATA%\MetaDock\bin and you substitute your own username above. Easiest of all: Settings → API, Automation & AI → Install to desktop tools writes this for you.
Option 2: Streamable HTTP
Connection Details
MCP 2025-11-25http://localhost:8080/mcpStreamable HTTP2025-11-25 is the latest version MetaDock speaks; it negotiates down to 2025-06-18 for clients that ask for it.
Claude Desktop Config
{
"mcpServers": {
"metadock": {
"url": "http://localhost:8080/mcp",
"headers": {
"Authorization": "Bearer [api-key-here]"
}
}
}
}198 production-ready MCP tools
The cards below show the areas the 198 tools cover, with a few representative tools from each. They are samples, not the full list, which ships with the app.
Browser Navigation
Sample tools- • Navigate to URL
- • Go back/forward
- • Reload
- • Stop loading
Page Info & Source
Sample tools- • Get URL & title
- • Get page source
- • Get browser state
Page Interaction
Sample tools- • Click elements
- • Type text
- • Set input values
- • Submit forms
- • Scroll to/by
Element Query
Sample tools- • Get element text
- • Get attributes
- • Check visibility
JavaScript & Injection
Sample tools- • Execute JS
- • Inject CSS/JS
- • Read & clear console
Capture
Sample tools- • Screenshot
- • Get last screenshot
- • Print to PDF
Cookie Management
Sample tools- • Set/get cookies
- • List all
- • Delete & clear
Settings & DevTools
Sample tools- • User agent
- • Viewport & zoom
- • Open/close DevTools
Device Emulation
Sample tools- • Emulate device
- • Geolocation
- • Offline
- • Headless
Wait & Batch
Sample tools- • Wait for element
- • Wait for load
- • Batch commands
Browser Management & Bulk
Sample tools- • Create/list browsers
- • Create multiple
- • Navigate/reload/close all
Layout Management
Sample tools- • List/create/delete
- • Rename
- • Get browsers & apps
- • Screenshot
Profile Management
Sample tools- • List/create/delete
- • Temporary profiles
- • Set default
- • Proxy get/set
Workspace Management
Sample tools- • List/switch
- • Create/delete
- • Rename & homepage
- • Startup workspace
Anti-Fingerprint
Sample tools- • Get/set fingerprint
- • Canvas & WebGL
- • Audio
- • Clear spoofing
Native App Docking
Sample tools- • List running processes
- • Mount/dismount
- • App info
- • Lock & set title
Bookmarks
Sample tools- • List & open
- • Create/update/delete
- • Categories
- • Tags
Browsing History
Sample tools- • List visits
- • Delete a visit
- • Remove a URL
- • Clear history
Downloads
Sample tools- • Start & list
- • Pause/resume/cancel
- • Remove
- • Clear completed
Search & Aliases
Sample tools- • Run a search
- • Manage search engines
- • Set/resolve aliases
Ad & Tracker Blocking
Sample tools- • List/add/remove filter lists
- • Update lists
- • Per-site overrides
- • Whitelist
Site Permissions
Sample tools- • List granted permissions
- • Set & remove
- • Clear by host
App Settings & Themes
Sample tools- • List/get/set settings
- • List themes
A catalog is not enough on its own
Handing an assistant 198 tools against your logged-in browsers raises three fair questions. Here is how each is answered.
You decide what it can reach
You choose which tools are exposed at all, and that choice covers every surface at once. The sensitive groups are off to begin with, browsing history among them. A key can be narrowed further still: to a set of capabilities, to named profiles and layouts, or to an allowlist of domains it may navigate to at all. The password vault and the clipboard are not toggles, they are simply absent from the catalog.
It does not burn tokens on markup
Raw HTML is mostly script and style a model cannot use. The reader converts a live page to markdown with a readability pass, in three modes, scoped by selector and paged by character count. Tables come back as markdown, CSV or JSON rows, links as a deduplicated list, forms as named fields. For driving a page rather than reading it, a snapshot of the visible controls costs a fraction of a screenshot.
Simple mode for smaller clients
198 tool definitions is a lot for a client to hold. Turn on Simple MCP Mode and MetaDock advertises five compact tools instead: search the catalog, list it, describe one tool, get help, and call a tool by name. Your assistant finds what it needs rather than being handed everything up front.
What can I actually do with MCP?
Tell your assistant what you want in plain English. It can name things in your setup because it can read your setup: profiles, bookmarks, aliases, and history are all queryable. What it cannot do is sign in for you, because no tool on any surface reaches your password vault, by design.
So “the ‘Client A’ profile” or “my ‘Invoices’ bookmark” resolve to real things rather than a guess.
Compare Vendor Pricing Pages
"Open the Stripe, PayPal, and Adyen pricing pages and tell me which one has the lowest fee for $25 transactions"
The AI opens each vendor's published pricing page, extracts the relevant fee structure, and summarizes the comparison for you.
Test Your App As Multiple User Roles
"Open localhost:3000 in two browsers, one under my 'Admin' profile and one under 'Free user', both visible at once"
The assistant reads your profile list, then opens a browser on each. It never signs in for you and has no access to your vault: those two profiles are already logged in, because a profile keeps its own cookies and session indefinitely. Watch a feature behave across permission tiers without re-logging. MetaDock gives you unlimited profiles, so there is no ceiling to plan around.
Web Testing
"Test the login flow on staging.myapp.com - try valid credentials, then invalid ones, and screenshot the results"
The AI automates form filling, submission, and captures screenshots for documentation. Supply the credentials in your prompt: it cannot read them out of MetaDock.
Data Extraction
"Go through the first 10 pages of search results and collect all product names and prices"
Batch operations enable efficient multi-page scraping workflows.
Multi-Account Workflows
"Open the bookmark named 'Client dashboard' in two browsers, one under profile 'Client A' and one under 'Client B', side by side"
The assistant looks the bookmark up by name and opens it under each profile you named. Every profile keeps its own cookies, cache, and session, so both accounts stay logged in side by side. Scale the same prompt to as many clients as your hardware allows.
How does the MCP server work under the hood?
The server runs inside MetaDock itself and exposes 198 tools against the browsers already open on your desktop. Each browser is addressed by UUID, so a call reaches one specific panel, and a bulk request can drive several at once with no cap on the actions sent to each.
Which resources can a client read?
Read-only access to MetaDock's state: browser state, HTML source, console messages and cookies, plus your layouts, workspaces, profile list, and app and API server status. Resources are for reading rather than acting, so a client can inspect what is open before deciding what to do about it.
Browser Resources
- • Browser state (URL, title, loading)
- • HTML source code
- • Console messages
- • Cookies
Layout & Workspace
- • List all layouts
- • Active layout info
- • List all workspaces
System
- • System status
- • App info & version
- • API server status
- • Profile list
Ready to let your AI assistant drive a real browser?
MCP is part of MetaDock Pro, $49/mo, with no monthly or daily request quota. The 14-day free trial grants MetaDock Pro with no credit card, so you can test every tool before you decide.
Setting it up now? Read the MCP server documentation for connection details, or the built-in AI assistant guide if you would rather not wire up an external client. Scripting rather than chatting? The same 198 tools are shell commands through the mdk command line.
Steam reviews
What people are saying
“Brilliant software. Main use case for me is the ability to resize windows that can't usually be resized. I'm able to do almost as much on 2 monitors now as I could on 3.”
“Very interesting application, great for productivity. This has fast become a tool in my tool box.”
All quotes are from pseudonymous Steam reviewers. Verify on Steam. Reviews curated and re-checked against the live page as of 2026-07-29.
14-day free trial, no credit card
Start a 14-day free trial with a short form and an email address. No card, no charge. Subscribe when you are ready.
Cancel anytime
Paid plans renew automatically until you cancel, and you can cancel from the billing portal at any time to stop every future charge.
Local-first data
Multi-monitor layouts, profiles, and browsing data stored locally. No cloud sync.