Skip to content

Zed Edge report_issue

How to: Zed Edge report_issue

client:Zed transport:stdio tool:report_issue

Add Edge to Zed

  1. 01

    Open ~/.config/zed/settings.json and merge this in. Keep any servers already there.

{
  "context_servers": {
    "edge": {
      "command": "npx",
      "args": [
        "-y",
        "@getedge/mcp"
      ],
      "env": {
        "EDGE_KEY": "<EDGE_KEY>"
      }
    }
  }
}
  1. 02

    Save the file and restart Zed.

  2. 03

    Ask for something report_issue does. Zed lists the server's tools on connect and calls report_issue itself — you do not invoke it by name.

  3. 04

    If nothing happens, check the server is running and that Edge's identifier in your config matches the one above exactly.

Merge this into your existing settings object — do not replace the file. Zed docs

Set these first

Edge will not start until these are set, so report_issue never becomes available.

  • EDGE_KEY

Same tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 8 October 2026. It is what the server actually exposes, not what its listing claims.

Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.