Skip to content
mcp/harbor

Zed KnownFix Resource/Fix __dirname is not defined in ES module scope in Node.js

How to: Zed KnownFix Fix __dirname is not defined in ES module scope in Node.js

client:Zed transport:streamable-http resource:Fix __dirname is not defined in ES module scope in Node.js

Add KnownFix to Zed

  1. 01

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

{
  "context_servers": {
    "knownfix": {
      "url": "https://knownfix-backend-28.b-hash88.deno.net/mcp"
    }
  }
}
  1. 02

    Save the file and restart Zed.

  2. 03

    Fix __dirname is not defined in ES module scope in Node.js is surfaced wherever your client lets you attach context. It is context to attach, not an action to run.

  3. 04

    If it does not appear, check that KnownFix is connected and that you are looking at its resources rather than its tools.

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

Same resource, other clients

Read from the server itself, by connecting to it and calling resources/list on 24 September 2026. A listing does not declare its resources, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each resource's type and contents.

KnownFix MCP server