Zed Integration

Loom is designed around a single source of truth: a shared MCP registry that can generate consistent client configurations across platforms.

This page documents the Zed integration path for Loom.

What You Get

• Consistent MCP server definitions (same registry, same names)
• Repeatable profiles for switching between local-only and hub routing
• A place to converge on one workflow across editors

Setup (High Level)

1. Ensure your Loom registry is up to date (the same one used for VS Code).
2. Generate a Zed-compatible MCP configuration from the registry.
3. Point Zed at the generated config and verify connectivity with a simple tool call.

Notes

• Keep secrets out of the repo. Use your platform-specific secret manager or local env files.
• Prefer read-only/public endpoints for any demos exposed from production infrastructure.