# Imagine.io MCP MCP

> Imagine.io MCP connects your AI client directly to 3D visualization and automated content pipelines. It lets you programmatically manage entire product portfolios, trigger complex rendering jobs for AR or 360° views, and instantly monitor asset status without logging into a dashboard.

## Overview
- **Category:** ecommerce
- **Price:** Free
- **Tags:** 3d-visualization, product-rendering, augmented-reality, content-automation, sku-management

## Description

Running an e-commerce site with physical products means managing constant visual assets: product shots, room renders, viewer links. Doing this manually—checking job statuses, compiling metadata, verifying credits—is slow and error-prone. This MCP lets your agent coordinate the entire process through natural conversation. You'll list and manage all 3D assets in one place, triggering a render for a new view simply by asking your AI client to do it. It keeps track of complex jobs like Viewer or AR spins until they finish processing. When you connect this resource via Vinkius, your agent acts as the dedicated asset architect, providing real-time status checks and listing generated outputs so you can report on content volume instantly.

## Tools

### check_imagine_status
Verifies the API connection and operational status of your Imagine.io account.

### create_render_job
Starts a new 3D render job (Viewer, AR, or 360° Spin). The job runs in the background.

### get_account
Retrieves your account details and current rendering credit balance.

### get_job_status
Checks the current status of any previously started render job.

### get_product
Gets detailed metadata for a specific product ID within your account.

### get_scene
Retrieves details about a specific virtual scene, including lighting and camera angles.

### list_materials
Lists all available materials that can be applied to your 3D models during rendering.

### list_products
Returns a list of all 3D products in your portfolio, including their metadata and render status.

### list_renders
Provides a list of past or current product renders, detailing output URLs and job IDs.

### list_scenes
Lists every available scene template for placing products in virtual environments.

## Prompt Examples

**Prompt:** 
```
List all my 3D products in Imagine.
```

**Response:** 
```
You have 12 products in your account. The most recent is 'White Sneaker v2' with 3 completed renders. Would you like to start a new render or view details?
```

**Prompt:** 
```
Start a render for product 'PROD-4821'.
```

**Response:** 
```
Render job submitted for PROD-4821. Job ID: JOB-9173. Estimated time: 4 minutes. I'll check the status for you — would you like me to notify you when it's done?
```

**Prompt:** 
```
Show me all scenes available for product placement.
```

**Response:** 
```
You have 8 scenes available: 'Studio White', 'Kitchen Modern', 'Living Room Warm', and 5 more. Each scene includes customizable lighting and camera angles. Want to see details for any of them?
```

## Capabilities

### Monitor account health
Check API connectivity and verify render credits before starting any job.

### Manage product inventory
Retrieve a full list of all 3D products, getting key metadata like SKU IDs.

### Define assets and context
List available scenes, materials, or specific products to set up the rendering parameters.

### Initiate renders
Start a complex 3D render job (Viewer, AR, 360° Spin) asynchronously.

### Track job status
Get the real-time completion or error status for any running rendering job.

## Use Cases

### Launching a new product line
The Product Manager needs 360° views for five SKUs in the 'Modern Kitchen' scene. They ask their agent, which triggers `create_render_job` five times (using context from `list_scenes`). The agent tracks all jobs via `get_job_status` and compiles a single report with Viewer URLs.

### Auditing asset compliance
The Ops Lead needs to know which products are missing AR renders. They use the agent to run `list_products`, filtering for items where the render status is 'pending' or 'missing', providing a clear list of necessary actions.

### Debugging rendering failures
A developer suspects an asset failure related to lighting. They ask the agent to retrieve details for the scene using `get_scene` and check required materials via `list_materials`, isolating the variable causing the render error.

### Pre-flight API checks
A teammate needs to confirm connectivity before a major batch run. They simply ask the agent to verify status using `check_imagine_status` and check credits with `get_account`, ensuring the pipeline won't fail mid-job.

## Benefits

- Avoid manual status checks. Instead of logging in to see if a render finished, ask your agent for the job status using `get_job_status` and get an immediate answer.
- Manage your entire asset portfolio from one place. Use `list_products` to instantly inventory all SKUs and check their associated 3D metadata without running separate reports.
- Set up complex renders in conversation. Simply ask the agent to start a new job using `create_render_job`, eliminating the need to fill out forms or use multiple API endpoints.
- Streamline content discovery. Your agent can list all finished outputs via `list_renders` and provide direct links, saving you time compiling asset reports.
- Verify prerequisites instantly. Before any render job, check your usage limits with `get_account` to prevent unexpected failures due to expired credits.

## How It Works

The bottom line is that your AI client handles the state machine—you just ask it what to do.

1. First, authenticate your agent using your Imagine.io API Key and Registered Domain.
2. Next, use natural language to tell the MCP what you need: 'Start a render for product X in scene Y.'
3. Your agent executes the job, tracks its status via subsequent calls, and provides you with the final asset URLs.

## Frequently Asked Questions

**How do I check if my Imagine.io API key is valid using check_imagine_status?**
Run `check_imagine_status` to verify your account connectivity and credentials. This tool confirms that the MCP can communicate with the Imagine.io platform before you start any complex, credit-consuming jobs.

**What is the difference between list_products and get_product?**
`list_products` gives you a high-level inventory of all products in your portfolio and their general render status. `get_product` pulls deep, specific metadata for just one product ID.

**Can I list scenes using list_scenes to know what contexts are available?**
Yes. Use `list_scenes` first. This gives you the full catalog of scene templates (e.g., 'Studio White') that your agent can then reference when starting a render job.

**How do I start rendering assets for multiple products?**
Use `create_render_job` and feed it the necessary product ID and scene context. You should run this in batches, monitoring progress with `get_job_status` until all jobs complete.

**How do I use the get_account tool to check my remaining render credits or usage limits?**
It returns your account details and current credit balance. This is essential for managing costs; before running a job, always call get_account to confirm you have enough available credits for rendering.

**If my 3D render fails, what can I use the get_job_status tool for?**
The status check provides detailed failure reasons and error codes. If a job doesn't complete, running get_job_status helps you diagnose if it was due to missing assets or resource limits.

**After using list_renders, how do I find the final hosted asset URL for an image?**
The result from list_renders provides metadata and a direct link identifier. You must use this unique ID in subsequent calls to retrieve the actual downloadable viewer or image file URL.

**Before starting a complex render job, can I check available materials using list_materials?**
Yes, list_materials pulls a comprehensive catalog of all usable assets. This prevents workflow errors by confirming that the necessary textures and components are properly loaded into your project context.

**How do I start a 3D render job?**
Use the `create_render_job` tool with a product identifier. The render runs asynchronously — check progress with `get_job_status`.

**Can I browse available 3D scenes and materials?**
Yes. Use `list_scenes` to browse environments and `list_materials` to see all available textures and finishes for your products.

**How do I download the final rendered images?**
Use `list_renders` with the product identifier to retrieve all completed render URLs including resolution details and download links.