three.ws Herald MCP Server

What the code does

We read the source, 3 h ago · rules 995398eba69f

Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.

        'http://metadata.google.internal/computeMetadata/v1/instance/service-accounts/default/token',

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.

        UPDATE destination_whitelist_settings
        SET cooldown_seconds = ${ch.cooldown_seconds ?? row.cooldown_seconds},

        const r = await redis.eval(

        const proc = spawn(ffmpegPath(), ['-hide_banner', '-loglevel', 'error', '-i', 'pipe:0', ...args, 'pipe:1']);

                return JSON.parse(await readFile(path.join(base, rel), 'utf8'));

        lambda: subprocess.run(

            if (reset) { state.cursor = null; state.total = 0; grid.innerHTML = skeletons(); stateEl.hidden = true; }

        `https://api.telegram.org/bot${cfg.token}/sendMessage`,

    "bytecode": "0x60806040523480156200001157600080fd5b5060405162000dd238038062000dd2833981016040819052620000349162000351565b8383600362000044838262000477565b50600462000053828262000477565b5050506001600160a01b038116620000a65760405162461bcd60e51b8152602060048201526011602482015270726…

import { existsSync, mkdirSync, readdirSync, statSync } from 'fs'

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 herald-mcp -e 'THREE_WS_API_KEY=<THREE_WS_API_KEY>' -- npx -y @three-ws/herald-mcp

{
  "mcpServers": {
    "herald-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@three-ws/herald-mcp"
      ],
      "env": {
        "THREE_WS_API_KEY": "<THREE_WS_API_KEY>"
      }
    }
  }
}

[mcp_servers.herald-mcp]
command = "npx"
args = ["-y", "@three-ws/herald-mcp"]
env = { THREE_WS_API_KEY = "<THREE_WS_API_KEY>" }

{
  "mcpServers": {
    "herald-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@three-ws/herald-mcp"
      ],
      "env": {
        "THREE_WS_API_KEY": "<THREE_WS_API_KEY>"
      }
    }
  }
}

{
  "servers": {
    "herald-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@three-ws/herald-mcp"
      ],
      "env": {
        "THREE_WS_API_KEY": "<THREE_WS_API_KEY>"
      }
    }
  }
}

Put your own value in place of <THREE_WS_API_KEY> (A three.ws API key (sk_live_… / sk_test_…) with the herald:announce scope, or an OAuth access token for the same account, carried as Authorization: Bearer. Required: an announcement is always delivered to the key owner's own sessions. Aliases: THREE_WS_TOKEN, THREE_WS_BEARER. Treat like a password). The author’s registry entry marks it as required.

Optional settings from the registry entry, left out of the block above: THREE_WS_BASE (Base URL of the three.ws API. Override only when self-hosting or targeting a preview deployment), THREE_WS_TIMEOUT_MS (Per-request timeout in milliseconds for the announce call).