Ghostlink MCP Server

What the code does

We read the source, 21 h ago · rules 3dff92dd89df

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

    const child = spawn(bin, args, {

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add ghostlink -- npx -y @bgorzelic/ghostlink

{
  "mcpServers": {
    "ghostlink": {
      "args": [
        "-y",
        "@bgorzelic/ghostlink"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.ghostlink]
command = "npx"
args = ["-y", "@bgorzelic/ghostlink"]

{
  "mcpServers": {
    "ghostlink": {
      "args": [
        "-y",
        "@bgorzelic/ghostlink"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "ghostlink": {
      "args": [
        "-y",
        "@bgorzelic/ghostlink"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: GHOSTLINK_REPO_ROOT (Absolute path to the repository the server is confined to. Every tool call is sandboxed beneath this path.), GHOSTLINK_LOG (Optional path for the JSON audit log of tool calls. Omit to disable file logging.). The author declared them in the registry entry; get the values from the project itself.