Private early access documentation

CarPixAI MCP

CarPixAI exposes a stateless Streamable HTTP MCP endpoint for approved dealership accounts. Phase 1 is deliberately read-only: it can discover account-scoped resources and retrieve existing processing results, but cannot create processing jobs, upload inventory, approve work, or spend credits.

Endpoint and authentication

https://carpixai.com/api/mcp
Authorization: Bearer YOUR_MCP_KEY

MCP keys are provisioned for approved dealership accounts during early access. CarPixAI stores the non-secret key prefix and only a SHA-256 hash of the secret in server-side credential records; the full plaintext token is returned once and cannot be retrieved later. Missing, malformed, unknown, revoked, non-dealership, or unapproved credentials receive 401 Unauthorized.

Available tools

get_account

Returns the authenticated dealership and current processing-credit balance.

list_background_templates

Lists uploaded background templates assigned to the authenticated dealership.

list_background_styles

Lists enabled CarPixAI automotive scene styles without exposing internal prompts.

photo_status_read

Returns a safe status DTO for an owned photo: status, timestamps, retryability, integrity-state availability, and whether a result can be retrieved. It never returns media URLs.

get_photo_job

Compatibility alias for the same safe status DTO; it does not return a download URL.

Client configuration

Use the URL and header fields supported by your MCP client:

{
  "mcpServers": {
    "carpixai": {
      "url": "https://carpixai.com/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_MCP_KEY"
      }
    }
  }
}

Status tools do not return media URLs. To retrieve a completed canonical presentation result, use the authenticated result-delivery route GET /api/mcp/results/:imageId with the same Authorization header. Treat the key as a secret, keep it out of browser code and source control, and rotate it if exposed.

Why processing writes are not in Phase 1

CarPixAI already has durable asynchronous dashboard jobs, but an external create-processing capability also needs a scoped approval receipt, immutable request manifest, atomic credit reservation, exact idempotent replay, abuse controls, and reconciliation. A create-job MCP tool will remain unavailable until those responsibilities are verified through one shared authority used by every transport.

Review the integration scope or request an early-access key by emailing CarPixAI.

Try Free — No Credit Card