High-performance multiplayer editor. Zed uses its own settings.json with a context_servers block.
#Zed
High-performance multiplayer editor. Zed uses its own settings.json with a context_servers block.
#Status
Manual — paste the snippet below into the indicated config file.
#Config file
macOS: ~/.config/zed/settings.json
Windows: %APPDATA%\Zed\settings.json
Linux: ~/.config/zed/settings.json
#Setup
Open the config file above, paste the block below, save:
json// Add under the top-level object in ~/.config/zed/settings.json { "context_servers": { "vault": { "command": { "path": "mcpvault", "args": ["server"] } }, "supabase": { "command": { "path": "mcpvault", "args": ["wrap", "supabase"] } }, "github": { "command": { "path": "mcpvault", "args": ["wrap", "github"] } }, "vercel": { "command": { "path": "mcpvault", "args": ["wrap", "vercel"] } }, "stripe": { "command": { "path": "mcpvault", "args": ["wrap", "stripe"] } } } }
#Restart
zed: reload (command palette) or fully restart Zed.
#Notes
- Zed calls them 'context_servers' instead of 'mcpServers' and nests the command + args under a
commandobject.
#Verify
Run mcpvault doctor --client zed to confirm Zed sees the vault.