MetaDock vs Windows MCP
A side-by-side look at the MetaDock and Windows MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
M
MetaDockOS Automation · Remote HTTP/SSEControl the MetaDock desktop workspace over MCP: browsers, layouts, bookmarks, downloads, and more.38FairAuth: not declaredVerdict: choose MetaDock for os automation work over a hosted endpoint; choose Windows MCP for os automation as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
MChoose MetaDock when
- You need dedicated capabilities in the OS Automation domain.
- You prefer a remote HTTP/SSE transport.
Choose Windows MCP when
- You need dedicated capabilities in the OS Automation domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | M MetaDock | |
|---|---|---|
| Category | OS Automation | OS Automation |
| Quality signal | 38/100 · Fair | 48/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 10,089 |
| Directory activity | 0 views 0 installs 0 upvotes | 6 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View MetaDock | View Windows MCP |
Tools & capabilities
MetaDock tools
No tool names declared yet. Check the project README from the listing page.
Windows MCP tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
MetaDock
{
"mcpServers": {
"metadock": {
"url": "https://metadock.app/mcp"
}
}
}
Windows MCP
{
"mcpServers": {
"windows-mcp": {
"command": "uvx",
"args": [
"windows-mcp"
]
}
}
}
Frequently asked questions
MetaDock is categorized under OS Automation and uses a remote HTTP/SSE transport. Windows MCP belongs to OS Automation and uses a local stdio subprocess. Pick MetaDock for os automation work and Windows MCP for os automation.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
MetaDock has no declared pricing — check the project's own site. Windows MCP is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add metadock and windows-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MetaDock has a quality signal of 38/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Windows MCP has 48/100 (Fair) with 6 views, 0 installs and 10,089 GitHub stars.