car-search-strategy — CarScout MCP Prompt
car-search-strategy
is one of 4 prompts on the
CarScout
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke car-search-strategy from your client
- Claude Code CarScout Prompt/car-search-strategy run in your project directory
- Claude Desktop CarScout Prompt/car-search-strategy ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor CarScout Prompt/car-search-strategy ~/.cursor/mcp.json
- VS Code CarScout Prompt/car-search-strategy .vscode/mcp.json
- Zed CarScout Prompt/car-search-strategy ~/.config/zed/settings.json
- Windsurf CarScout Prompt/car-search-strategy ~/.codeium/windsurf/mcp_config.json
- Cline CarScout Prompt/car-search-strategy ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI CarScout Prompt/car-search-strategy ~/.gemini/settings.json
- Grok CarScout Prompt/car-search-strategy .mcp.json (in your project root)
- ChatGPT CarScout Prompt/car-search-strategy Settings → Connectors → Advanced → Developer mode
- Claude.ai CarScout Prompt/car-search-strategy Settings → Connectors → Add custom connector
- LangChain CarScout Prompt/car-search-strategy pip install langchain-mcp-adapters
Other prompts on this server
CarScout also offers 3 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.