strategy_schema_resource — Backtest360 MCP Resource

strategy_schema_resource is one of 1 resource on the Backtest360 MCP server. Connect the server and your client can attach it as context.

by client

How to attach strategy_schema_resource from your client

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

Backtest360 also offers 2 prompts — things you invoke, where a resource is context you attach.

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.