Request to StrategyQuant: MCP Integration Access for KI and clients

1) Confirmation/Setup of the Existing MCP Interface

• Confirm MCP server status: Does the MCP server run automatically and continuously alongside the SQX instance, or does it need to be separately activated/kept running (even when the GUI is minimized/in the background)?

• Clarify port reservation: The MCP server shares its port with "Remote Access" (default 8080, or the first available port). Can a fixed, dedicated port be configured so external clients don't need to search for the current port after every restart?

• Authentication/security: Not mentioned in the current documentation — is there (or is it planned) any access control for the MCP server (token/password), or is it open by default to any local process on localhost?

• Concurrent access: SQX currently only allows one running instance at a time (confirmed via CLI test: sqcli.exe refuses to start if the GUI is already open). For automation purposes, it would be relevant to know: can an MCP client work against the same running instance while the user is simultaneously active in the GUI — or do the two block each other?

2) Missing Functionality in the Current MCP Toolset (as of "first release")

Currently available: list_projects, list_strategies, list_databanks, get_strategy_stats, run_project, stop_project. For our use case (automated snippet creation + trade evaluation), the following are missing:

• Snippet management via MCP: A tool to create/update Java snippets (currently only possible via direct filesystem access to the extend/Snippets/SQ/... folder + manual restart to trigger recompilation — no MCP tool exists for this)

• Detailed trade export via MCP: get_strategy_stats only returns aggregated metrics (Fitness, Net Profit, Number of Trades, Sharpe Ratio, Drawdown) — no individual trades. An MCP equivalent to the existing CLI commands -tools action=orderstocsv and -databank action=export would be needed to retrieve full trade lists programmatically

• Snippet reload without restart: Currently, a restart of the SQX instance appears necessary for new/changed Java snippets to be detected and recompiled (hash comparison on boot). An MCP tool for targeted reloading/recompiling of individual snippets without a full restart would be significantly more practical for automated workflows

• Robustness tests via MCP: Not currently mentioned in the toolset — Monte Carlo, System Parameter Permutation, and Walk-Forward runs can indirectly be triggered via the existing CLI through -project tasks, but a dedicated MCP tool with a structured return value (instead of plain log text) would be desirable

3) Open Question Regarding the Roadmap

• Is there a timeline for when the functionality listed above (snippet management, detailed trade export) will be added to the official MCP toolset