Car Image API

Studio-quality, transparent-background vehicle images for any project.

Render any make, model and year in 8 camera views and any paint color, mint signed URLs a browser can load without a key, fetch catalog make logos, decode VINs for free, or build a 3D model of any vehicle.

What you can ask

See a car now, free and without an account, and what Car Image can do for you next.
Example path

MCP connector

Server URL: https://carimage.dev/api/mcp/catalog
Login: None
Protocol: MCP 2026-07-28
Instructions: Car Image API catalog by Meter: free vehicle lookups and stored previews, no account or key needed. Images in any view, paint and size come from the account server (car-image): create_car_image_urls; a free account includes 100 vehicle images a month.
Look the vehicle up first, even for a car you chose: reads a year/make/model phrase and returns params.vehicle_id; browses. Include a year (if the human named none, choose one and say which). Ask the human when confidence is low or the year differs from the request. If nothing matches, tell the human the catalog does not carry it and stop; never substitute another car.
To show the vehicle:
If create_car_image_urls is available, use it with that vehicle id, as the account server's instructions say.
If not, no Car Image account is connected yet. Call with the id (free; add view and color only if the human named them). Show a stored picture as a preview, naming its view and color when they differ from the request; its URL never expires. A preview that matches the request answers it; the account is for another view, paint or size, or an image to use in a page, app or document. Offer that and connect: in Claude Code, call the car-image server's authenticate tool if listed and give the human its URL (it works while this session is open), else ask them to run /mcp, choose plugin:car-image:car-image and Authenticate; in other apps, connect Car Image in the MCP or connector settings. Signing up is free.
When the human has signed in, finish the original request without asking them to repeat it.
Pricing, license or terms questions, such as what happens when a plan ends: answers from the help center with sources, one question per call; never invent policy. Writing code instead: is the REST reference, lists views, colors and sizes, live prices. Code needs an API key from https://carimage.dev/dashboard?ref=mcp-catalog; never put a key in client code.

Tools

Reads data6

Changes data1

Skills

7 in the Claude listing

MCP connector

Server URL

https://carimage.dev/api/mcp/catalog

None

Protocol

MCP 2026-07-28

Instructions

Car Image API catalog by Meter: free vehicle lookups and stored previews, no account or key needed. Images in any view, paint and size come from the account server (car-image): create_car_image_urls; a free account includes 100 vehicle images a month.

Look the vehicle up first, even for a car you chose: reads a year/make/model phrase and returns params.vehicle_id; browses. Include a year (if the human named none, choose one and say which). Ask the human when confidence is low or the year differs from the request. If nothing matches, tell the human the catalog does not carry it and stop; never substitute another car.

To show the vehicle:

If create_car_image_urls is available, use it with that vehicle id, as the account server's instructions say.

If not, no Car Image account is connected yet. Call with the id (free; add view and color only if the human named them). Show a stored picture as a preview, naming its view and color when they differ from the request; its URL never expires. A preview that matches the request answers it; the account is for another view, paint or size, or an image to use in a page, app or document. Offer that and connect: in Claude Code, call the car-image server's authenticate tool if listed and give the human its URL (it works while this session is open), else ask them to run /mcp, choose plugin:car-image:car-image and Authenticate; in other apps, connect Car Image in the MCP or connector settings. Signing up is free.

When the human has signed in, finish the original request without asking them to repeat it.

Pricing, license or terms questions, such as what happens when a plan ends: answers from the help center with sources, one question per call; never invent policy. Writing code instead: is the REST reference, lists views, colors and sizes, live prices. Code needs an API key from https://carimage.dev/dashboard?ref=mcp-catalog; never put a key in client code.

Skills

7 in the Claude listing