three.ws Signals MCP Server

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 signals-mcp -- npx -y @three-ws/signals-mcp

{
  "mcpServers": {
    "signals-mcp": {
      "args": [
        "-y",
        "@three-ws/signals-mcp"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.signals-mcp]
command = "npx"
args = ["-y", "@three-ws/signals-mcp"]

{
  "mcpServers": {
    "signals-mcp": {
      "args": [
        "-y",
        "@three-ws/signals-mcp"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "signals-mcp": {
      "args": [
        "-y",
        "@three-ws/signals-mcp"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: THREE_WS_BASE (Base URL of the three.ws API that serves the signal-marketplace endpoints. Override only when self-hosting or targeting a preview deployment.), THREE_WS_TIMEOUT_MS (Per-request timeout in milliseconds for the live marketplace reads and subscription writes.), THREE_WS_API_KEY (three.ws API key (sk_live_… / sk_test_…) for the account-scoped follower tools (get_subscriptions, subscribe_signal, set_subscription_status). Optional — the public discovery and leaderboard tools work without it. subscribe_signal in live mode spends real USDC, so treat this key like cash.). The author declared them in the registry entry; get the values from the project itself.