ai_trading_journel_mcp
Related Servers
Alternatives to ai_trading_journel_mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables portfolio and trade journaling by tracking accounts, holdings, manual trades, open and closed positions, realized and unrealized P&L, and trade reasons through discoverable MCP tools, resources, and prompts.1-
- AlicenseNot gradedqualityCmaintenanceProvides AI-powered trading analytics and coaching by analyzing historical trades to identify strategies, emotional patterns, and behavioral mistakes via MCP tools.1MIT
- AlicenseNot gradedqualityAmaintenanceProvides market intelligence tools for crypto, Korean market, US equities, options, and backtests, as well as personal trading journal access, through MCP.17 PyPIMIT
- ISC

TapeLog MCPofficial
AlicenseAqualityBmaintenanceEnables users to import DAS Trader Pro and Robinhood CSV exports, reconstruct round trips, and analyze private trade-journal statistics, behavioral leaks, and period comparisons through any MCP client.6MIT- AlicenseAqualityDmaintenanceOfficial MCP Server for Indian Stock Market (NSE & BSE) equities, futures context, and option chains.6MIT
TDQS
Scored across 16 tools
Most tools have clearly distinct resource+action targets: logging vs annotating vs deleting a trade, note writing, searching, single-trade detail, and various reporting dimensions. The main overlap is get_coaching_context, which bundles data also available via get_performance, get_instrument_breakdown, and get_behavior_report, so an agent might wonder when to use the bundle versus the individual reports. save_ai_report vs save_trade_feedback is also a mild boundary that descriptions mostly resolve (report vs per-trade feedback).
All names follow a consistent snake_case verb_noun pattern (log_trade, annotate_trade, delete_trade, get_performance, save_ai_report, sync_mt5, etc.). Verb choice is predictable and domain-appropriate, with no mixed conventions or cryptic abbreviations.
16 tools is slightly above the ideal 3-15 range but each appears to earn its place: core CRUD on trades, journaling, tagging, rules, and several targeted analytics views. The set is well-scoped for a trading journal rather than padded with redundant operations.
Core lifecycle is well covered: log/annotate/delete trades, sync MT5, day notes, rules, search/detail, and rich analytics plus coaching reports. Minor gaps exist: no way to edit a manually logged trade's core fields (only annotate or delete), no tag creation/management beyond list_tags, and no update operation for day notes or trading rules beyond overwrite/append.