Editor
VS Code extension
Writes each coding assistant's MCP config from the registry, and adds views for skills, agent context, server health, and remote tunnels.
Status: Runs in VS Code, not on this page · 5 synced docs pages
Loom
Loom turns a single registry file into matching MCP configs for each coding assistant. Loom Core is the CLI and daemon; the VS Code extension and the Zed config bring it into the editor.
Registry
Servers with an override for each client
A server's shared block is the default for every client Loom syncs. These bars count the servers that also carry an override for one client: a different launch command, environment, or secret source.
Snapshot generated · registry file dated 2026-03-31
Open the MCP mapThe line under each description says where that surface runs. Nothing on this page runs Loom.
Editor
Writes each coding assistant's MCP config from the registry, and adds views for skills, agent context, server health, and remote tunnels.
Status: Runs in VS Code, not on this page · 5 synced docs pages
CLI + daemon
Generates each client's config from the registry, runs the daemon that proxies and routes MCP servers, and serves the HUD.
Status: Its hub reads the registry snapshot above; nothing here talks to a daemon
Editor
Loom writes Zed’s MCP config from the same registry, so Zed sees the servers that VS Code and the CLI agents see.
Status: Listed as supported in the Loom README; no Zed-specific overrides in the registry snapshot
What Loom manages, the platforms it syncs, and how to install it.
Release notes for the extension, newest first.
Architecture, user guide, and runbooks for the CLI and daemon.