Car Background AI
Replace car photo backgrounds, hide license plates and add dealer logos for vehicle listings.
Should I use this
Quality & Safety
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"carbackground": {
"url": "https://api.carbackground.ai/mcp"
}
}
}Remote endpoints
https://api.carbackground.ai/mcpstreamable-httpWhat it can do
Tool inventory
Tools (13)
🟢list_backgrounds
List the background scenes available for car photos: built-in studios, showrooms and outdoor settings, plus the workspace's own custom backgrounds (`custom: true`, made with create_background or in the app). Call this first to pick a scene: each entry has a preview image, an example with a car, and the `id` that generate_background takes as `background_id` (custom ones also go to refine_background and delete_background). Read-only and free; takes no parameters and returns every scene in one response. For logos use list_logos instead.
Input Schema
{
"type": "object",
"properties": {}
}🟡create_background(description, reference_image_urls, base_background_id, name)
Create a new reusable background scene for the workspace, such as the dealer's own showroom, a branded studio or a specific outdoor setting. Use it when none of the scenes in list_backgrounds fits; it does not edit a car photo (that is generate_background), and to adjust a custom background that already exists use refine_background instead of creating another. Give a `description`, `reference_image_urls`, or both; add `base_background_id` to start from a built-in scene and describe only what to change. Renders a preview with a demo car and returns it as an image plus the new background's `id`, ready to pass to generate_background. Costs one credit; a rejected or failed request is not charged.
Input Schema
{
"type": "object",
"properties": {
"description": {
"description": "The scene: walls, floor, lighting, setting. E.g. 'A bright showroom with light oak flooring and floor-to-ceiling windows'.",
"type": "string"
},
"reference_image_urls": {
"description": "Up to three public image URLs of the place or style to recreate.",
"maxItems": 3,
"type": "array",
"items": {
"type": "string",
"format": "uri"
}
},
"base_background_id": {
"description": "A built-in background `id` to start from; the description then says what to change.",
"type": "string"
},
"name": {
"description": "Display name. Suggested if omitted.",
"type": "string"
}
},
"$schema": "https://json-schema.org/draft/2020-12/schema"
}🔴refine_background(background_id, description, reference_image_urls)
Adjust a custom background that already exists and render a new preview, e.g. after create_background when the preview is close but not right. `description` is only the change to make ('make the floor darker and the lighting warmer'); everything else in the scene is kept, and `reference_image_urls` can show the look to move towards. The background is updated in place under the same `id` and name, so later generate_background calls use the refined scene; photos already generated are not changed. Works on custom backgrounds only, not built-in ones; to start a different scene use create_background. Returns the new preview image. Costs one credit; a rejected or failed request is not charged.
Input Schema
{
"type": "object",
"properties": {
"background_id": {
"type": "string",
"description": "The `id` of a custom background."
},
"description": {
"type": "string",
"description": "What to change."
},
"reference_image_urls": {
"maxItems": 3,
"type": "array",
"items": {
"type": "string",
"format": "uri"
}
}
},
"required": [
"background_id",
"description"
],
"$schema": "https://json-schema.org/draft/2020-12/schema"
}🔴delete_background(background_id)
Permanently delete one of the workspace's custom backgrounds, e.g. a scene the user no longer wants in their list. It cannot be undone through this server; a deleted scene has to be made again with create_background. Photos already generated with it are not affected, and no credits are charged or refunded. Only custom backgrounds (`custom: true` in list_backgrounds) can be deleted, never built-in ones. To change a scene instead of removing it, use refine_background. Returns the `id` with `deleted: true`, or `not_found` for an unknown id.
Input Schema
{
"type": "object",
"properties": {
"background_id": {
"type": "string",
"description": "The `id` of a custom background."
}
},
"required": [
"background_id"
],
"$schema": "https://json-schema.org/draft/2020-12/schema"
}🟡generate_background(image_url, background_id, hide_license_plate, license_plate_style, license_plate_logo, ...)
Replace the background of one car photo with a chosen scene: the main tool for turning a phone photo into a listing photo. The car is kept as photographed and gets shadows, lighting and reflections that match the scene. Works on exterior, interior and detail shots. Pick `background_id` with list_backgrounds first and use the same one for every photo of a car. In the same call it can hide the plate (`hide_license_plate`, with `license_plate_style` and, for `logo`, a `license_plate_logo` from list_logos), draw a dealer `logo`, reframe to an `aspect_ratio`, centre the car or show it washed. To hide the plate without changing the background use hide_license_plates; to make a new scene use create_background. One photo per call; the source photo is not modified. Costs one credit, and a failed generation is not charged. Can take up to a minute. Returns a signed `image_url` of the high-resolution result, valid for 7 days.
Input Schema
{
"type": "object",
"properties": {
"image_url": {
"type": "string",
"format": "uri",
"description": "Public HTTPS URL of the car photo (JPEG, PNG or WebP)."
},
"background_id": {
"type": "string",
"description": "A background `id` from list_backgrounds."
},
"hide_license_plate": {
"description": "Hide a legible license plate (exterior photos).",
"type": "boolean"
},
"license_plate_style": {
"description": "With hide_license_plate: `plain` (default) replaces it with a blank plate, `blur` blurs it, `logo` shows the dealer's plate logo (set license_plate_logo).",
"type": "string",
"enum": [
"plain",
"blur",
"logo"
]
},
"license_plate_logo": {
"description": "Required with license_plate_style `logo`.",
"type": "object",
"properties": {
"id": {
"type": "string",
"description": "A plate logo `id` from list_logos with type `plate`."
}
},
"required": [
"id"
]
},
"aspect_ratio": {
"description": "Output aspect ratio. Omit to keep the photo's own.",
"type": "string",
"enum": [
"1:1",
"16:9",
"9:16",
"4:3",
"3:4",
"3:2",
"2:3",
"4:5",
"5:4",
"21:9"
]
},
"center_car": {
"description": "Experimental: centre, enlarge and level the car like a listing photo.",
"type": "boolean"
},
"clean_car": {
"description": "Experimental: show the car freshly washed.",
"type": "boolean"
},
"logo": {
"description": "Draw one of the workspace's logos on the result.",
"type": "object",
"properties": {
"id": {
"type": "string",
"description": "A logo `id` from list_logos."
},
"position": {
"type": "string",
"enum": [
"top-left",
"top-right",
"bottom-left",
"bottom-right",
"top-center"
]
}
},
"required": [
"id"
]
}
},
"required": [
"image_url",
"background_id"
],
"$schema": "https://json-schema.org/draft/2020-12/schema"
}🟡hide_license_plates(image_url, style, block_color)
Hide the license plates in a car photo without changing anything else, for privacy before publishing a listing. Use this when the background should stay as it is; when the background is being replaced as well, set `hide_license_plate` on generate_background instead of calling both. `style` chooses a blur (default) or a solid `block`, and `block_color` sets the block's colour. Uses no credits: it is included with an active subscription, up to a fair-use monthly limit, and returns `subscription_required` for a workspace without one. The source photo is not modified; the result is returned as an image, with the areas that were hidden listed as `plates`.
Input Schema
{
"type": "object",
"properties": {
"image_url": {
"type": "string",
"format": "uri",
"description": "Public HTTPS URL of the car photo (JPEG, PNG or WebP)."
},
"style": {
"description": "Blur the plate (default) or cover it with a block.",
"type": "string",
"enum": [
"blur",
"block"
]
},
"block_color": {
"description": "Hex colour of the block, e.g. #FFFFFF. Default black.",
"type": "string"
}
},
"required": [
"image_url"
],
"$schema": "https://json-schema.org/draft/2020-12/schema"
}🟢get_credits
Read the workspace's current credit balance, returned as `balance`. One credit is one photo from generate_background or one preview from create_background or refine_background; hide_license_plates uses none. Call it before a batch to check there are enough credits, or after an insufficient-credits error. Read-only and free; takes no parameters. It does not show plans or prices: when the balance is too low, use list_plans, then create_checkout (no subscription yet) or change_plan (existing subscription).
Input Schema
{
"type": "object",
"properties": {}
}🟢list_logos(type)
List the logos stored for the workspace, to get the `id` that other tools need. `type` selects which set is returned: `logo` (default) for dealer logos drawn on finished photos, passed as `logo.id` to generate_background, or `plate` for designs shown on the license plate, passed as `license_plate_logo.id`. Each entry has `id`, `type`, `image_url` and `created_at`. Also call it before delete_logo, or before upload_logo to see whether the logo is already stored. Read-only and free. For background scenes use list_backgrounds instead.
Input Schema
{
"type": "object",
"properties": {
"type": {
"description": "`logo` (default): logos drawn on finished photos. `plate`: designs put on the license plate.",
"type": "string",
"enum": [
"logo",
"plate"
]
}
},
"$schema": "https://json-schema.org/draft/2020-12/schema"
}🔴upload_logo(image_url, type, background)
Store a logo for the workspace so it can be put on photos later. It does not change any photo by itself: pass the returned `id` to generate_background as `logo.id`, or as `license_plate_logo.id` for a `plate` logo. The file is fetched from `image_url` once and a copy is kept (PNG, WebP or JPEG up to 5 MB; a transparent background works best). `type` is `logo` (default) for dealer logos or `plate` for license plate designs, where `background` sets the plate colour behind a transparent logo. Up to seven per type: when full, remove one with delete_logo first. Check list_logos before uploading to avoid duplicates. Free. Returns the stored logo with its `id`.
Input Schema
{
"type": "object",
"properties": {
"image_url": {
"type": "string",
"format": "uri",
"description": "Public HTTPS URL of the logo."
},
"type": {
"description": "`logo` (default): logos drawn on finished photos. `plate`: designs put on the license plate.",
"type": "string",
"enum": [
"logo",
"plate"
]
},
"background": {
"description": "Plate logos only: hex colour behind a transparent logo. Default white.",
"type": "string"
}
},
"required": [
"image_url"
],
"$schema": "https://json-schema.org/draft/2020-12/schema"
}🔴delete_logo(id, type)
Permanently delete one of the workspace's stored logos, e.g. an outdated logo or to free one of the seven slots before upload_logo. It cannot be undone through this server; the logo has to be uploaded again to restore it. Photos already generated keep the logo they were made with, and later generate_background calls can no longer use this `id`. Get the `id` from list_logos, and pass the same `type` the logo was listed under (`logo` by default, or `plate`). Free. Returns the `id` with `deleted: true`, or `not_found` when the id is unknown for that type.
Input Schema
{
"type": "object",
"properties": {
"id": {
"type": "string",
"description": "A logo `id` from list_logos."
},
"type": {
"description": "`logo` (default): logos drawn on finished photos. `plate`: designs put on the license plate.",
"type": "string",
"enum": [
"logo",
"plate"
]
}
},
"required": [
"id"
],
"$schema": "https://json-schema.org/draft/2020-12/schema"
}🟢list_plans
List the subscription plans on offer, to quote prices or to get the `price_id` that create_checkout (workspace without a subscription) and change_plan (existing subscription) take. Each plan has its monthly photo allowance (`credits`), billing interval and price: `unit_amount` is in the smallest unit of `currency` (USD), and `currency_options` lists the fixed local prices whose keys create_checkout accepts as `currency`. Read-only and free; takes no parameters and is the same for every caller. It does not show the workspace's own balance: use get_credits for that.
Input Schema
{
"type": "object",
"properties": {}
}🟡create_checkout(price_id, currency, buyer)
Start a first subscription for a workspace that has none, e.g. when get_credits shows too few credits. Take `price_id` from list_plans; `currency` picks one of that plan's fixed local prices and `buyer` decides VAT handling for EU and UK buyers. This call charges nothing: it returns a Stripe checkout `url` for the user to open and pay, and the plan's photos are added once the payment completes. For a workspace that already subscribes it returns `already_subscribed`; use change_plan there instead. Needs an OAuth sign-in: with an API key it returns an error pointing to the app.
Input Schema
{
"type": "object",
"properties": {
"price_id": {
"type": "string",
"description": "A `price_id` from list_plans."
},
"currency": {
"description": "A key of the plan's `currency_options` (e.g. `eur`) to pay the fixed local price. Omit for USD.",
"type": "string"
},
"buyer": {
"description": "EU and UK buyers: `business` collects a VAT number (reverse charge), `personal` adds VAT.",
"type": "string",
"enum": [
"business",
"personal"
]
}
},
"required": [
"price_id"
],
"$schema": "https://json-schema.org/draft/2020-12/schema"
}🔴change_plan(price_id, confirm)
Change the plan of a workspace that already has a subscription, to a `price_id` from list_plans. Always call it first with `confirm: false`, which for an upgrade returns a preview of the prorated charge and charges nothing, and get the user's agreement to that amount. With `confirm: true` an upgrade charges the payment method on file immediately and adds the photos at once, while a smaller plan charges nothing now and is booked to start at the next renewal. For a workspace without a subscription it returns `no_active_subscription`; use create_checkout there instead. It cannot cancel a subscription; the user does that in the app. Needs an OAuth sign-in: with an API key it returns an error pointing to the app.
Input Schema
{
"type": "object",
"properties": {
"price_id": {
"type": "string",
"description": "A `price_id` from list_plans."
},
"confirm": {
"type": "boolean",
"description": "false previews an upgrade; true applies the change."
}
},
"required": [
"price_id",
"confirm"
],
"$schema": "https://json-schema.org/draft/2020-12/schema"
}Community
Evidence