Historical replay reference — flashalpha MCP Resource

Historical replay reference is one of 9 resources on the flashalpha MCP server. Connect the server and your client can attach it as context.

by client

How to attach Historical replay reference from your client

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

Other resources on this server

• Live screener reference
• Volatility estimators reference
• Live API reference
• Dealer positioning methodology
• Plan tiers & endpoint access
• Screener field taxonomy
• MCP server reference
• Options analytics glossary

flashalpha also offers 41 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.