MetaDock

What MetaDock MCP server does

The MetaDock MCP server gives an MCP-compatible agent access to the MetaDock desktop workspace. The supplied description identifies four supported areas: browsers, layouts, bookmarks, and downloads. It also indicates that additional workspace functions may be available, but does not enumerate them.

This makes MetaDock relevant for agents that need to work with a desktop environment spanning web browsing and workspace organization. Browser control can support tasks involving the workspace’s browser context. Layout controls relate to how that workspace is arranged. Bookmark and download controls cover two common forms of browser-related organization.

The available material does not describe whether these controls are read-only, mutating, or both. It also does not specify individual tool names, argument formats, return values, permissions, or the exact operations supported within each area. Developers should verify those details from the service documentation before building an automated workflow.

How it works

An MCP client connects an AI agent to MetaDock, allowing the agent to invoke the workspace capabilities exposed by the MetaDock MCP server. The listing identifies the target as the MetaDock desktop workspace, rather than a general browser service or standalone bookmark and download API.

No transport type, authentication flow, request examples, or session behavior is provided in the available material. As a result, the connection cannot be accurately described as stdio, HTTP, or another MCP transport. The same applies to access controls and confirmation behavior for actions that change the workspace.

Limitations and notes

The repository README is unavailable, so installation steps, configuration fields, supported MCP clients, environment variables, license information, and detailed tool schemas are not documented here. The source reference is the MetaDock MCP page at https://metadock.app/mcp.

The phrase “and more” in the listing confirms that the four named areas may not be exhaustive, but it does not provide enough information to name additional capabilities. Treat browser, layout, bookmark, and download control as the documented scope, and consult the source for the complete tool inventory and operational requirements before implementation.