Gemini · verify client MCP support
TradeJournal MCP with Google Gemini
Confirm Gemini's MCP client path in Google's docs; until then use TradeJournal's on-site agent.
Quick summary
- Token: Connect AI → personal MCP token (your account only).
- Configure client: Follow steps below for Google AI Gemini docs.
- Tools: Call
get_runtime_contextfirst — full list on the MCP tools reference page.
Key takeaway
TradeJournal.co users on Google Gemini should use the on-site AI assistant for read-only trade and stats queries until Gemini MCP client support is documented and TradeJournal connector OAuth ships.
Setup steps
-
On-site assistant (recommended)
Same nine tools via session—see ai-trading-assistant guide.
-
Check Gemini MCP docs
When Google documents MCP for your client, mirror Cursor-style URL + Bearer token.
Official client docs: Google AI Gemini docs · MCP specification
TradeJournal MCP tools (summary)
Full parameters on the MCP tools reference page.
| Tool | Purpose |
|---|---|
| get_runtime_context | User portfolios, active portfolio, plan flags, privacy rules. Call this first in every session. |
| list_portfolios | Portfolio id and name list for disambiguation. |
| list_trades | Filtered trade list (portfolio, symbol, status, limit). User-owned rows only. |
| get_trade | Single trade by id (must belong to the authenticated user). |
| get_trade_stats | Aggregate win rate, profit, and related stats for the user. |
| get_dashboard_stats | High-level public/private trade and post rollups. |
| list_posts | Published posts metadata for the user. |
| get_post | One published post by id. |
| get_portfolio_stats | Per-portfolio performance rollup. |
FAQ
Tools reference · Security & privacy · MCP hub · Onboarding call