Local Desktop Runtime
Local machine runtime for desktop-hosted MCP servers, filesystem tools, browser automation, and IDE agent workflows.
Source boundary
MCP architecture documentation describes host, client, and server roles that often run locally for desktop workflows.
Relationships
| Type | Source | Target | Citation |
|---|
Compatibility
| Type | Target | Status | Evidence |
|---|---|---|---|
| runtime_deployment | local-desktop-runtime | supported | Claude Code is a local developer host that runs against local project workspaces and configured command-line tools. |
| runtime_deployment | local-desktop-runtime | supported | Claude Desktop local MCP setup runs desktop-hosted MCP server processes through local configuration. |
| runtime_deployment | local-desktop-runtime | adapter_required | Dify is designed for server deployment; desktop runtime requires container adapter. |
| runtime_deployment | local-desktop-runtime | supported | Filesystem MCP Server is a local stdio server pattern that fits a desktop runtime with explicit filesystem boundaries. |
| server_transport | local-desktop-runtime | supported | Notion MCP uses HTTP transport which is compatible with local desktop runtime. |
| runtime_deployment | local-desktop-runtime | supported | Playwright MCP Server runs browser automation through local process tooling and fits local desktop runtime workflows. |
| runtime_deployment | local-desktop-runtime | supported | VS Code manages workspace-level MCP server configuration and local tool execution from a desktop IDE runtime. |
| runtime_deployment | local-desktop-runtime | supported | Zed is a local IDE host for coding workflows and can participate in local agent context through its AI and MCP configuration. |