strategy-dsl-spec — EmidLabs Backtest MCP Resource

strategy-dsl-spec is one of 1 resource on the EmidLabs Backtest MCP server. Connect the server and your client can attach it as context.

by client

How to attach strategy-dsl-spec from your client

• Claude Code EmidLabs Backtest Resource/strategy-dsl-spec run in your project directory
• Claude Desktop EmidLabs Backtest Resource/strategy-dsl-spec ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor EmidLabs Backtest Resource/strategy-dsl-spec ~/.cursor/mcp.json
• VS Code EmidLabs Backtest Resource/strategy-dsl-spec .vscode/mcp.json
• Zed EmidLabs Backtest Resource/strategy-dsl-spec ~/.config/zed/settings.json
• Windsurf EmidLabs Backtest Resource/strategy-dsl-spec ~/.codeium/windsurf/mcp_config.json
• Cline EmidLabs Backtest Resource/strategy-dsl-spec ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI EmidLabs Backtest Resource/strategy-dsl-spec ~/.gemini/settings.json
• Grok EmidLabs Backtest Resource/strategy-dsl-spec .mcp.json (in your project root)
• ChatGPT EmidLabs Backtest Resource/strategy-dsl-spec Settings → Connectors → Advanced → Developer mode
• Claude.ai EmidLabs Backtest Resource/strategy-dsl-spec Settings → Connectors → Add custom connector
• LangChain EmidLabs Backtest Resource/strategy-dsl-spec pip install langchain-mcp-adapters

Read from the server itself, by connecting to it and calling resources/list on 24 September 2026. A listing does not declare its resources, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each resource's type and contents.