Bring 3d Visualization
to Cursor
Learn how to connect Imagine.io to Cursor and start using 10 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Imagine.io MCP Server?
Connect your Imagine.io account to any AI agent and take full control of your 3D product visualization and automated content generation workflows through natural conversation.
What you can do
- Project & Product Orchestration — List and manage your entire portfolio of 3D products programmatically, retrieving detailed technical metadata and SKU IDs
- Content Job Intelligence — Programmatically trigger and monitor 3D generation jobs (Viewer, AR, 360° Spin) to maintain a perfectly coordinated output pipeline
- Asset Architecture Monitoring — Access real-time statuses for 3D processing and retrieve hosted asset URLs (Viewer URLs, images) directly through your agent
- Shared Content Discovery — Access generated outputs and their metadata directly through your agent for instant operational reporting
- Operational Monitoring — Verify account-level API connectivity and monitor content generation volume directly through your agent for perfectly coordinated service scaling
How it works
1. Subscribe to this server
2. Retrieve your API Key and Registered Domain from your Imagine.io dashboard (Settings > API Access)
3. Start orchestrating your 3D assets from Claude, Cursor, or any MCP client
No more manual checking of individual job statuses or missing 3D viewer links. Your AI acts as your dedicated 3D coordinator and asset architect.
Who is this for?
- E-commerce Managers — instantly retrieve 3D viewer links and monitor content job status using natural language commands
- 3D Artists & Developers — verify asset metadata and track processing health without leaving your creative workspace
- Operations Leads — automate the management of 3D product portfolios through simple AI queries
Built-in capabilities (10)
Verify Imagine API connectivity
The job runs asynchronously; check status with get_job_status. Start a 3D render job
io account details and render credit balance. Get account info
Check render job status
Get product details
Get scene details
List available materials
io account with their render status and metadata. List all 3D products
List product renders
List all scenes
Why Cursor?
Cursor's Agent mode turns Imagine.io into an in-editor superpower. Ask Cursor to generate code using live data from Imagine.io and it fetches, processes, and writes. all in a single agentic loop. 10 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Imagine.io in Cursor
Imagine.io and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Imagine.io to Cursor through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Imagine.io in Cursor
The Imagine.io MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 10 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Cursor only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Imagine.io for Cursor
Every tool call from Cursor to the Imagine.io MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
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.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.