three.ws Signals — Claude Code MCP server: setup guide
Connects AI agents to copy-trade feeds and verified on-chain publisher rankings. Useful when automating trade monitoring or mirror-trading.
claude mcp add --env THREE_WS_BASE=<THREE_WS_BASE> --env THREE_WS_TIMEOUT_MS=<THREE_WS_TIMEOUT_MS> --env THREE_WS_API_KEY=<THREE_WS_API_KEY> --transport stdio signals-mcp -- npx -y @three-ws/signals-mcpWhat three.ws Signals does
This server exposes the three.ws marketplace over stdio. Public discovery tools like list_signal_feeds and get_mirror_leaderboard let agents search signal providers filtered by realized edge, win-rate, and on-chain P&L without an account.
Account-scoped tools manage trading execution. The subscribe_signal tool configures copy-trading with position scaling and slippage caps. Setting mode to simulate evaluates performance without moving funds, while live charges USDC per signal via x402 and mirrors orders on-chain. Charges occur at signal delivery rather than subscription time.
Missing a THREE_WS_API_KEY environment variable prevents any subscription actions from executing. Calling set_subscription_status with killed freezes all trades and pending payments before transactions broadcast.
What it helps with
- inspect signal provider rankings backed by verified transaction history
- test copy-trade execution in risk-free simulation mode
- automate mirror-trading on live feeds with custom SOL exposure caps
- halt subscription spend and trading executions instantly with a kill switch
Example prompts for the agent
- Show the top signal feeds on mainnet sorted by edge score
- Subscribe agent agt_99 to feed 42 in simulate mode with 0.1 SOL base size
- Check my current subscription list and total USDC spent
How to install three.ws Signals
Platform CLI
claude mcp add --env THREE_WS_BASE=<THREE_WS_BASE> --env THREE_WS_TIMEOUT_MS=<THREE_WS_TIMEOUT_MS> --env THREE_WS_API_KEY=<THREE_WS_API_KEY> --transport stdio signals-mcp -- npx -y @three-ws/signals-mcpReplace <…> with your own values
Platform CLI
codex mcp add signals-mcp --env THREE_WS_BASE=<THREE_WS_BASE> --env THREE_WS_TIMEOUT_MS=<THREE_WS_TIMEOUT_MS> --env THREE_WS_API_KEY=<THREE_WS_API_KEY> -- npx -y @three-ws/signals-mcpReplace <…> with your own values
Config file
{
"mcpServers": {
"signals-mcp": {
"command": "npx",
"args": [
"-y",
"@three-ws/signals-mcp"
],
"env": {
"THREE_WS_BASE": "<THREE_WS_BASE>",
"THREE_WS_TIMEOUT_MS": "<THREE_WS_TIMEOUT_MS>",
"THREE_WS_API_KEY": "<THREE_WS_API_KEY>"
}
}
}
}Replace <…> with your own values
Config file
{
"servers": {
"signals-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@three-ws/signals-mcp"
],
"env": {
"THREE_WS_BASE": "<THREE_WS_BASE>",
"THREE_WS_TIMEOUT_MS": "<THREE_WS_TIMEOUT_MS>",
"THREE_WS_API_KEY": "<THREE_WS_API_KEY>"
}
}
}
}Replace <…> with your own values
Platform CLI
gemini mcp add -e THREE_WS_BASE=<THREE_WS_BASE> -e THREE_WS_TIMEOUT_MS=<THREE_WS_TIMEOUT_MS> -e THREE_WS_API_KEY=<THREE_WS_API_KEY> signals-mcp npx -y @three-ws/signals-mcpReplace <…> with your own values
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about three.ws Signals
How do I install three.ws Signals in Claude Code?
Run claude mcp add signals-mcp -e THREE_WS_API_KEY=<THREE_WS_API_KEY> -- npx -y @three-ws/signals-mcp in your terminal. Replace the placeholder with your valid key.
Can I browse signal feeds without an API key?
Yes, list_signal_feeds and get_mirror_leaderboard are public read-only functions. You only need an API key when subscribing or checking account usage.
When are fees charged in live mode?
Payments move when a publisher emits a trade signal, not upon initial subscription. You can cancel execution early by setting the status to killed.
