TrendWake MCP — connect your AI agent

How it fits together

MCP servers don’t talk to each other — your agent is the hub. You connect two servers to it: TrendWake (signals) and your broker’s agentic server (e.g. Robinhood or Webull). The agent reads a signal from us, pulls a live quote from your broker, asks us to size it, and places the order through your broker — with your approval. TrendWake never sees your brokerage and never places a trade.

Brokers your agent can trade through

TrendWake never integrates with any broker directly — your agent is the only bridge. That’s why every broker that opens agentic rails works with TrendWake on day one.

1. Connect with one click

No keys to copy — TrendWake speaks OAuth, so MCP clients that support it connect in one click. You'll approve the connection on a TrendWake consent page (a Premium subscription is required).

claude.ai (web or desktop):

1. Go to Settings → Connectors → Add custom connector.
2. Enter the URL https://mcp.trendwake.com/mcp.
3. Leave the OAuth fields blank and click Add.
4. Approve on the TrendWake consent page when it opens — done.

Claude Code (terminal):

claude mcp add --transport http trendwake https://mcp.trendwake.com/mcp

OAuth is handled automatically on first use — a browser window opens for you to sign in and approve. Other OAuth-capable MCP clients work the same way with the same URL.

2. Add your broker (for execution)

To actually place trades, connect your brokerage’s own agentic MCP server alongside TrendWake — this is set up on the broker’s side, with a dedicated, separately-funded account and per-trade approval.

Webull (live for all US clients) — connector URL:

https://api.webull.com/mcp

Robinhood (Agentic Trading beta):

claude mcp add robinhood-trading --transport http https://agent.robinhood.com/mcp/trading

Both keep you in control: Webull previews every order and supports size caps + symbol allowlists; Robinhood sandboxes your agent into a budgeted Agentic account. Other brokers work via their APIs — TrendWake is broker-agnostic and sits next to whichever you connect.

What TrendWake exposes

• get_latest_signalsThe most recent signals across the live strategies (ticker, direction, strategy, derived stop %).
• check_signal_for_tickerWhether a specific ticker has a signal today.
• get_signal_planRisk-based position sizing for a signal — you pass the current price from your brokerage; it returns shares / stop / max loss.
• get_active_positionsWhat the public paper-trading bot is holding right now.
• get_watchlistThe curated signal universe (symbol, grade, sector).
• get_strategy_performanceBacktest summary for a strategy (win rate, profit factor, drawdown, return) with the survivor-bias caveat.

Signals only — TrendWake never returns raw market price data. Your agent gets live prices from your brokerage connection.

Example prompts

• “What are TrendWake’s latest long signals today?”
• “Does COIN have a TrendWake signal right now, and what’s the daily strategy’s backtest look like?”
• “Check TrendWake for new long signals. For any with profit factor above 1.5, get the current price from my broker, size it for my $10,000 account at 2% risk, and show me the plan before placing anything.”

Advanced: static API keys

Prefer a long-lived credential — for scripts, CI, or an MCP client without OAuth support? In the app, go to Account → Developer and create a key. It starts with tw_mcp_, expires after 90 days, and is shown once — copy it then. You can revoke it anytime; keys are capped at 5 active per account.

Claude Code (terminal):

claude mcp add trendwake --transport http https://mcp.trendwake.com/mcp \
  --header "Authorization: Bearer tw_mcp_your_key_here"

Claude Desktop / Cursor — add to your MCP config:

{
  "mcpServers": {
    "trendwake": {
      "transport": "http",
      "url": "https://mcp.trendwake.com/mcp",
      "headers": { "Authorization": "Bearer tw_mcp_your_key_here" }
    }
  }
}

ChatGPT and other MCP-capable clients use the same URL + Bearer header.