Latitude — Zed extension

One-click install of the Latitude MCP server inside Zed.

After installing and authorizing, the Zed Agent Panel can read and manage your Latitude workspace: projects, members, keys, traces, annotations, scores, searches, issues, datasets, and more. The full tool catalog is dynamically generated from the Latitude API.

How it works

Zed's extension API only supports spawn-based context servers (a Command with a binary + args), so an extension can't register a URL-only remote MCP the way Zed's own ~/.config/zed/settings.json can. To bridge that gap, this extension:

1. Uses Zed's bundled Node binary (zed::node_binary_path()) — no Node install required on your system.
2. Installs the mcp-remote npm package into its own working directory via zed::npm_install_package().
3. Spawns node node_modules/mcp-remote/dist/proxy.js https://api.latitude.so/v1/mcp as the context server.

mcp-remote handles the OAuth 2.1 + Dynamic Client Registration handshake against the Latitude MCP server and exposes a stdio transport that Zed talks to.

Install

From the marketplace

Install Latitude from the Zed extensions marketplace.

Manual (no extension)

If you'd rather skip the extension entirely, edit ~/.config/zed/settings.json:

{
  "context_servers": {
    "latitude": {
      "url": "https://api.latitude.so/v1/mcp"
    }
  }
}

This uses Zed's native remote MCP support directly (no Node bridge involved). Then Agent Settings → MCP Servers, click Authenticate on latitude.

Local development

1. Install Rust via rustup. Homebrew Rust will not work for Zed dev extensions.
2. From Zed's Extensions page, click Install Dev Extension (or run the zed: install dev extension action) and pick this zed/ directory.
3. Open the Agent panel and authenticate latitude.

For verbose logs, launch Zed in the foreground:

zed --foreground

Layout

.
├── extension.toml      # Extension manifest (id, version, context_servers binding)
├── Cargo.toml          # Rust crate compiled to Wasm
├── LICENSE             # MIT (required for marketplace acceptance)
├── src/lib.rs          # context_server_command spawns Zed-bundled Node + mcp-remote
├── assets/             # Icons
└── README.md

Submission

1. Mirror this zed/ folder into its own public repo with the MIT license at the root.
2. Fork zed-industries/extensions.
3. Add the extension as a Git submodule under extensions/latitude/:

   git submodule add https://github.com/<org>/<repo>.git extensions/latitude
   git add extensions/latitude

   Use the HTTPS URL (not SSH), point at a branch (not a detached commit), and make sure the repo is public.
4. Add an entry to extensions.toml:

   [latitude]
   submodule = "extensions/latitude"
   version = "0.1.0"

5. Run pnpm sort-extensions to keep extensions.toml / .gitmodules sorted.
6. Open the PR.

License

MIT