Connect TrendWake to your AI assistant (and your broker) with MCP

What MCP is

The Model Context Protocol (MCP) is the open standard that lets AI assistants like Claude plug into outside tools. A server exposes capabilities; your assistant calls them mid-conversation. TrendWake ships an MCP server, and brokers increasingly do too — Robinhood's MCP tooling, for example, exposes quotes, positions, and order placement to the same assistants.

What the TrendWake MCP server exposes

Connect mcp.trendwake.com (a Premium feature — mint your key under Account → Developer) and your assistant can:

• pull the latest signals and each signal's full plan,
• check whether a specific ticker has an active signal right now,
• read the bots' active positions and strategy performance,
• read the watchlist universe with grades and conviction notes.

Setup takes about two minutes — the full walkthrough lives at trendwake.com/mcp.

The pattern: intelligence here, execution at YOUR broker

The interesting workflow is combining connectors in one assistant:

1. TrendWake MCP supplies the derived intelligence — signals, plans, regime.
2. Your broker's MCP connection (e.g. Robinhood's) supplies your live quotes, your positions, your order flow.
3. You ask things like "does anything on my watchlist have an active TrendWake signal, and what would a 1%-risk position look like given my account?" — and the assistant crosses the two.

TrendWake never touches your brokerage account. We expose no order endpoints; anything you execute goes through your own broker connection, reviewed by you. That separation is the design, not a limitation.

A note on safety

Give your assistant read access freely; treat order placement with the same care you'd treat any automation — confirm each trade, size by risk, and remember signals are educational, not instructions.

Not financial advice. TrendWake MCP provides derived, educational data only.