Car Deals Search MCP Server

An MCP server that searches for car deals from Cars.com, Autotrader, and KBB. The car deals search mcp mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 14 defined tools rather than through you.

What it actually does

An MCP (Model Context Protocol) server that aggregates and searches car listings from multiple sources. Scrapes listings in parallel, extracts price, mileage, dealer info, and applies optional CARFAX-style filters (1-owner, no accidents, personal use).

Its toolset

Everything the assistant can do here goes through one of these:

• Command — node
• Args — ["/src/server.js"]
• Multi — source aggregation**: Search Cars.com, Autotrader, and KBB simultaneously
• Scraping — Puppeteer (headless Chromium) with stealth plugin to bypass bot detection
• Concurrency — Parallel scraper workers for simultaneous multi-source queries
• Protocol — Implements MCP (Model Context Protocol) for AI assistant integration
• macOS — Chrome is typically at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
• Linux — Usually auto-detected by Puppeteer or at /usr/bin/chromium-browser
• Windows — Typically at C:\Program Files\Google\Chrome\Application\chrome.exe
• Repository — https://github.com/SiddarthaKoppaka/car_deals_search_mcp
• Issues — https://github.com/SiddarthaKoppaka/car_deals_search_mcp/issues
• Source — Price

Configuration

You will need one environment variable: PUPPETEER_EXECUTABLE_PATH. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Node.js (v16 or higher) - Chrome/Chromium browser installed (required by Puppeteer) - If Chrome is not in the default location, set PUPPETEER_EXECUTABLE_PATH environment variable to point to your Chrome/Chromium binary

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

When to reach for it

Among the browser automation options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Car Deals Search MCP's toolset — Command, Args, Multi and 11 more — is a fair guide to whether it matches your workflow. It is maintained by siddarthakoppaka; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Car Deals Search MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Car Deals Search MCP.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the car deals search mcp mcp server does with a few real requests.