Integrations

Zed

Set up zn-gate in Zed in two minutes: add it as an MCP server, and what zn-gate does not cover there.

View .md

Quick start (no coding needed)

  1. Check that Node.js is installed. Open a terminal (in most editors: menu Terminal → New Terminal; or your computer's Terminal app), type node --version and press Enter. If you see a version number (18 or later), go on. If you see "command not found", install the LTS version from nodejs.org and restart Zed.

  2. Open the Command Palette (Ctrl+Shift+P, or Cmd+Shift+P on a Mac), type zed: open settings file and press Enter.

  3. Paste this:

    {
  "context_servers": {
    "zn-gate": {
      "command": "npx",
      "args": [
        "-y",
        "zn-gate",
        "mcp"
      ],
      "env": {}
    }
  }
}

    If the file already has a "context_servers" section, add only the "zn-gate": {...} part inside it. Or use Settings → AI → MCP Servers → Add Server → Add Local Server.

  4. Save the file.

Status: these steps follow Zed's documentation; not yet verified by us in Zed.

What zn-gate protects in Zed, and what it does not

In Zed, zn-gate works as an MCP server: the agent can ask it to check a prompt, a tool call or a tool result (analyze_prompt, check_tool_call, check_tool_result). The agent decides when to call these tools, so on its own this is not automatic protection.

In Zed
zn-gate's checks available to the agent (MCP) Yes
Your other MCP servers checked for prompt injection and secrets Yes, if you wrap them (below)
Blocks reads of .env and credential files No
Removes secrets from shell output and file contents No
Blocks a secret pasted into the chat No

We found no agent hooks in Zed's documentation, so zn-gate can only work as an MCP server there. In Zed zn-gate does not block reads of your .env or credential files and does not remove secrets from shell output or file contents. If you need that today, use zn-gate with Claude Code, Codex CLI, Cursor or OpenCode: see compat.md.

Technical reference

Where the configuration lives

Your Zed settings.json, key context_servers.

Check the output of your other MCP servers

To check the output of the other MCP servers you use in Zed, start each local server through zn-gate: replace its command with npx and put -y zn-gate shield -- in front of its original command and arguments. For example, a server started with uvx mcp-server-fetch becomes:

{
  "context_servers": {
    "fetch": {
      "command": "npx",
      "args": [
        "-y",
        "zn-gate",
        "shield",
        "--",
        "uvx",
        "mcp-server-fetch"
      ],
      "env": {}
    }
  }
}

Every result of that server is then checked for prompt injection, and secrets zn-gate recognizes are removed, before the agent sees it. zn-gate init, which does this automatically for Claude Desktop, Claude Code, Cursor, Codex and OpenCode, does not edit Zed's settings.

Zed documentation