Options analytics glossary — flashalpha MCP Resource

Options analytics glossary 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 Options analytics glossary from your client

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

Other resources on this server

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

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.