Integrations

Cline

Set up zn-gate in Cline 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 VS Code (or your editor).

  2. In the Cline panel, click the MCP Servers icon, open the Configure tab and click Configure MCP Servers. Cline opens its settings file.

  3. Paste this:

    {
  "mcpServers": {
    "zn-gate": {
      "command": "npx",
      "args": [
        "-y",
        "zn-gate",
        "mcp"
      ],
      "disabled": false,
      "autoApprove": []
    }
  }
}

    If the file already has a "mcpServers" section, add only the "zn-gate": {...} part inside it.

  4. Save the file. The zn-gate server appears in Cline's list of MCP servers.

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

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

In Cline, 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 Cline
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 hooks in the Cline extension's documentation that zn-gate could use (hooks are documented for the Cline SDK only), and zn-gate does not install any for Cline. So in Cline 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

The file opened by Configure MCP Servers (Cline CLI: ~/.cline/data/settings/cline_mcp_settings.json).

Check the output of your other MCP servers

To check the output of the other MCP servers you use in Cline, 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:

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

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 Cline's settings.

Cline documentation