place_prediction — predictDEX MCP Prompt

place_prediction is one of 2 prompts on the predictDEX MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke place_prediction from your client

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

Other prompts on this server

• analyze_market

predictDEX also offers 4 resources — data you attach as context, where a prompt is something you run.

Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026. A listing does not declare its prompts, 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 prompt's arguments.