ZapSign (unofficial) MCP Server

What the code does

We read the source, 5 d ago · rules 995398eba69f

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 dir = path.join(logRoot, settings.logDir);

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 zapsign-mcp -- npx -y zapsign-mcp

{
  "mcpServers": {
    "zapsign-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "zapsign-mcp"
      ]
    }
  }
}

[mcp_servers.zapsign-mcp]
command = "npx"
args = ["-y", "zapsign-mcp"]

{
  "mcpServers": {
    "zapsign-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "zapsign-mcp"
      ]
    }
  }
}

{
  "servers": {
    "zapsign-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "zapsign-mcp"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: ZAPSIGN_SANDBOX_TOKEN (API token for sandbox. On macOS it can live in the Keychain instead (see the README)), ZAPSIGN_PROD_TOKEN (API token for production. On macOS it can live in the Keychain instead (see the README)).