buying-workflow — CarScout MCP Resource

buying-workflow is one of 3 resources on the CarScout MCP server. Connect the server and your client can attach it as context.

by client

How to attach buying-workflow from your client

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

Other resources on this server

• tool-catalog
• server-card

CarScout also offers 4 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.