CarMax MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BROWSERBASE_CDP_URL | Yes | Browserbase CDP URL with API key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_inventoryA | Search CarMax inventory for used vehicles. Filter by make, model, year range, price range, and location (ZIP code). Returns a list of matching vehicles with stock numbers, prices, mileage, and links. |
| get_vehicle_detailsA | Get full details for a specific CarMax vehicle by stock number or URL slug, including specs, features, photos, Carfax history, and store location. |
| schedule_test_driveA | Schedule a test drive appointment at CarMax for a specific vehicle. Returns confirmation details or next steps. |
| get_instant_offerA | Get an instant cash offer from CarMax for selling your car. Provide VIN or license plate + state. Returns estimated offer range and next steps. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clear, distinct purpose: search_inventory finds vehicles, get_vehicle_details provides specifics on a single vehicle, schedule_test_drive books an appointment, and get_instant_offer handles selling a car. There is no overlap or ambiguity between them.
All tool names follow a consistent verb_noun pattern in snake_case: search_inventory, schedule_test_drive, get_instant_offer, get_vehicle_details. The naming is uniform and predictable.
With four tools, the server is well-scoped for a car marketplace use case. Each tool covers a distinct step in the buyer or seller journey, and none feel redundant or unnecessary.
The tool set covers the core lifecycle: search inventory, view details, schedule test drive, and get an offer for selling. Missing features like financing or purchase tools are gaps, but they are outside the immediate scope and do not break common workflows.