Skip to main content
Glama

Related Servers

Alternatives to Backtrader MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      A local-first MCP server that bridges AI coding agents with MetaTrader 5 for inspection, market data, MQL5 development, compiling, Strategy Tester review, workspace sync, logs, audit trails, demo trading, and carefully gated live trading.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Exposes market data, public strategies, backtesting, subscriptions, and AI generation capabilities as MCP tools that AI clients such as Claude Desktop, Cursor, and Cline can call. It runs locally over stdio or remotely over Streamable HTTP, with anonymous, API-key, or OAuth access.
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      Local-first backtesting engine with built-in overfitting detection (PBO, deflated Sharpe, bootstrap CI, walk-forward) and a native MCP server for AI agents to validate trading strategies.
      4
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      MCP server for the FLOX trading framework. About 30 tools to run backtests, scaffold strategies, validate for lookahead bias, compute indicators, place orders, and query PnL from Claude/Cursor.
      38
      945 PyPI
      231
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      The MCP server for AlphaForge — the agent-native quant CLI: write strategies in JSON, optimize with Optuna TPE, validate with walk-forward, export to TradingView Pine v6. This server lets your AI agent drive the whole pipeline over MCP.
      17
      1
      Apache 2.0

    TDQS

    B3.4/5.0

    Scored across 30 tools

    Disambiguation4/5

    The toolset separates phases clearly (inspect/register/preview, draft/validate/change, prepare/start/run), and most tools have unique resource-action pairings. Minor confusion exists between register_dataset and register_local_dataset, and between inspect_dataset and preview_dataset, since both deal with bounded CSV/dataset inspection.

    Naming Consistency4/5

    Almost every tool follows a consistent verb_noun snake_case pattern (register_dataset, preview_dataset, start_strategy_run, get_run_logs). The single outlier 'doctor' breaks the pattern, and 'list_jobs' is slightly less descriptive than the strategy-specific names, but the convention is otherwise uniform.

    Tool Count2/5

    30 tools is above the 25+ threshold and feels heavy for a typical MCP server, even though the lifecycle is broad. The set could be consolidated into fewer, higher-level tools or grouped behind subresources.

    Completeness4/5

    The server covers the full dataset/strategy/run lifecycle: ingest and derive datasets, create/validate/deploy strategy drafts, execute and compare runs, and render reports. Notable gaps are lack of dataset enumeration/listing and no explicit discard/delete operation for strategy drafts, though immutability and approval flows mitigate this.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues