Dealer MCP

What dealer-mcp does

dealer-mcp is described as a car-dealer AI assistant for three related tasks: searching inventory, matching Car Wanted buyer requests, and drafting private offers. These capabilities cover the path from finding available vehicles to identifying likely matches for a buyer and preparing an offer for review.

The supplied material identifies the associated source as BestCarFinder’s dealer AI assistant page. It does not provide a detailed API description, data model, or explanation of whether inventory and buyer-request data come from a particular dealership system. Treat the listed capabilities as the supported scope rather than assuming additional dealership operations.

How it works

An AI assistant can use dealer-mcp to search available inventory, evaluate that inventory against Car Wanted requests, and produce a draft private offer. The matching step connects a buyer’s stated request with vehicles in the searchable inventory. The offer step is described as drafting, so the available information supports preparation of an offer but not automatic delivery, acceptance, financing, purchase completion, or other transaction actions.

The dealer-mcp MCP server is therefore most relevant when an agent needs assistance with vehicle discovery and preliminary buyer matching. It may fit workflows where a dealer or salesperson reviews results before taking the next step, but the supplied description does not establish any approval, audit, CRM, messaging, or transaction workflow.

Tools and capabilities

The documented capabilities are:

• Search car dealer inventory.
• Match inventory to Car Wanted buyer requests.
• Draft private offers based on the relevant vehicle and buyer context.

No tool names, parameters, return formats, supported vehicle fields, filtering options, or matching criteria are provided. Those details should be confirmed before building an automated workflow around the dealer-mcp MCP server.

Setup and configuration

The available material does not include installation instructions, transport details, configuration steps, authentication requirements, environment variables, or client-specific setup. The source is a BestCarFinder dealer AI assistant page, but that reference alone does not establish how to connect the MCP server to an MCP client. Consult the project’s current documentation before deployment.

Limitations and notes

The dealer-mcp MCP server’s documented scope is limited to inventory search, Car Wanted matching, and private-offer drafting. There is no supplied evidence of vehicle purchasing, payment processing, financing, messaging, dealership-management-system synchronization, or automatic offer submission. The README is unavailable, so compatibility, licensing, runtime requirements, and operational safeguards cannot be verified from the provided material.