Account and credit context
Read the authenticated dealership and its current image-credit balance.
CarPixAI MCP
Listing-ready vehicle photos through your AI assistant
CarPixAI MCP lets Professional and Business dealerships connect an MCP-compatible assistant to a secure inventory-photo workflow: check credits, choose an approved background, process one photo or a batch of up to 10, verify status, and retrieve protected results.
A narrow, usable tool set
From source photo to protected result
Dealer-safe backgrounds
List enabled CarPixAI styles and background templates assigned to that dealership.
Single or bulk processing
Process one HTTPS source or queue up to 10 with explicit credit confirmation, bounded concurrency, and retry-safe item identities.
Status and protected results
Poll safe job state, then retrieve an authorized listing-ready result without exposing storage URLs.
Separate credentials
MCP keys are hashed, expiring, revocable, rate-limited, and cannot authenticate to the REST transport.
Dealership isolation
Every account, status, and result lookup derives ownership from the authenticated key—not from a tool argument.
Retry-safe credits
One accepted processing identity reserves one credit. Matching replays reuse the job; changed inputs conflict; failed dispatch compensates.
Included with Professional and Business
Use the credits you already have
There is no separate MCP credit pool. Professional includes 200 images for $69/month; Business includes 500 images for $149/month. MCP, REST, and dashboard jobs draw from the same balance.
Compare plansMCP questions
Which CarPixAI plans include MCP?
Active Professional and Business plans include self-service MCP access. MCP photo processing uses the same monthly image-credit balance as dashboard and REST API processing.
Can an MCP key also call the REST API?
No. CarPixAI issues separate transport-limited keys for MCP and REST so a credential cannot silently gain access to another integration surface.
Can MCP process a folder of inventory photos?
Yes. The MCP batch tool accepts up to 10 HTTPS vehicle-photo sources per call, queues them with bounded concurrency, and returns an ordered result for every item. Each accepted new item uses one image credit; webhooks, DMS publishing, arbitrary prompts, and model controls are not included.
How are vehicle identity and results protected?
MCP jobs use CarPixAI's production-default processing workflow, source-preserving settings, dealership ownership checks, and the same Vehicle Integrity and protected-export authorization used by the product.