vehicle-due-diligence — CarScout MCP Prompt

vehicle-due-diligence 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 vehicle-due-diligence from your client

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

Other prompts on this server

• car-search-strategy
• scout-setup
• alert-triage

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.