run_dca_backtest — dca tools MCP Tool Mutating
run_dca_backtest
(run dca backtest) is one of 3 tools on the
dca tools
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call run_dca_backtest from your client
- Claude Code dca tools run_dca_backtest run in your project directory
- Claude Desktop dca tools run_dca_backtest ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor dca tools run_dca_backtest ~/.cursor/mcp.json
- VS Code dca tools run_dca_backtest .vscode/mcp.json
- Zed dca tools run_dca_backtest ~/.config/zed/settings.json
- Windsurf dca tools run_dca_backtest ~/.codeium/windsurf/mcp_config.json
- Cline dca tools run_dca_backtest ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI dca tools run_dca_backtest ~/.gemini/settings.json
- Grok dca tools run_dca_backtest .mcp.json (in your project root)
- ChatGPT dca tools run_dca_backtest Settings → Connectors → Advanced → Developer mode
- Claude.ai dca tools run_dca_backtest Settings → Connectors → Add custom connector
- LangChain dca tools run_dca_backtest pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http dca-tools https://dcamethod.com/api/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.