Journal + AI · read-only
AI for Your Day Trading Journal
Stop building spreadsheets—import sessions automatically and ask AI about intraday stats, heatmaps, and which setups to cut.
Journal data → read-only AI tools
Quick summary
- Journal first: See Day Trading Journal (Don't Build Your Own) for platform fit.
- Connect AI: MCP token or on-site chat—same nine read-only tools.
- Ask with context: Always
get_runtime_contextbefore trade questions.
Key takeaway
TradeJournal.co day traders use MCP or the on-site AI assistant to analyze their own imported intraday trades and stats read-only—without building a custom journal (free trial and included pro trader onboarding).
Start with the right journal page
Day Trading Journal (Don't Build Your Own)
Why building a journal wastes hundreds of hours—use a battle-tested platform instead.
Read guideWhy add AI on top
Session discipline
Review morning vs. afternoon P&L with AI after import.
Setup retirement
Ask which playbooks bleed—backed by your tags.
No custom code
Same nine MCP tools as every other asset class.
Example prompts (read-only)
- What is my win rate on closed trades this week?
- Summarize my dashboard stats for my day-trading portfolio.
- List trades tagged as opening drive plays.
MCP tools (summary)
| 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. |