Integration

Mercedes-Benz Vehicle Images integration

The Mercedes-Benz Vehicle Images API returns original Mercedes-Benz and smart images of one specific vehicle, identified by its VIN (FIN). Get the image ids, or image URLs, of up to 36 exterior, 6 interior and 6 360-degree interior perspectives with options for background, night view, open roof, cropping and file format, then download each image; list the images of the vehicle's equipment (paint, rims, trim, upholstery, engine and option codes); and read which perspectives, image types and backgrounds exist for it. How many perspectives come back depends on the subscribed package (Placeholder, Basic or 360). The image composing route, which takes your own background images in the request, is not covered. For images of a model rather than of one vehicle, use the Mercedes-Benz Car Configurator. Authentication is an API key from a Mercedes-Benz /developers console project subscribed to a Vehicle Images package, sent in the x-api-key header.

Connect Mercedes-Benz Vehicle Images How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Mercedes-Benz Vehicle Images.Built from the 5 Mercedes-Benz Vehicle Images tools below, on the connection you add once.

What you can do with Mercedes-Benz Vehicle Images

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Background, 1 operation

list_vehicle_backgroundsList vehicle backgroundsGETLists the image backgrounds available for a VIN, the default one and the others; their keys are the backgroundItem values get_vehicle_images accepts.

Equipment, 1 operation

get_equipment_imagesGet equipment imagesGETReturns image URLs of a VIN's equipment, grouped by paint, rim, trim, upholstery, engine and other option codes, each with its code and description in the requested locale; imageTypes picks formats and sizes.

Image, 1 operation

download_imageDownload imageGETDownloads one vehicle image by its imageId, as returned by get_vehicle_images, and stores it as a file (WEBP by default, or the PNG or JPEG format chosen there). An image id is valid for 24 hours.

Imagekey, 1 operation

get_vehicle_image_keysGet vehicle image keysGETLists the image metadata that exists for a VIN: for the exterior, the interior and the special (360-degree interior) groups, the available perspectives, image types, states (such as night or roofOpen) and image keys.

Vehicle, 1 operation

get_vehicle_imagesGet vehicle imagesGETReturns, for a VIN, the image id of each exterior (EXT000 to EXT350), interior (INT1 to INT5, BET1) and 360-degree interior (BIS1 to BIS6) perspective your package includes; download_image fetches each one.

Use Mercedes-Benz Vehicle Images from Claude Code, Cursor or Codex

Connect Mercedes-Benz Vehicle Images in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Mercedes-Benz Vehicle Images operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Mercedes-Benz Vehicle Images

Create your workspace
Sign up free. Nothing to install.
Connect Mercedes-Benz Vehicle Images once
Add your Mercedes-Benz Vehicle Images connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.