Bring 3d Visualization
to VS Code Copilot
Learn how to connect Imagine.io to VS Code Copilot 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 VS Code Copilot?
GitHub Copilot Agent mode brings Imagine.io data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 10 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
- —
Project-scoped MCP configs (
.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access - —
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
- —
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
Imagine.io in VS Code Copilot
Imagine.io and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Imagine.io to VS Code Copilot 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 VS Code Copilot
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 VS Code Copilot 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 VS Code Copilot
Every tool call from VS Code Copilot 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.
Which VS Code version supports MCP?
MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
How do I switch to Agent mode?
Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
Can I restrict which MCP tools Copilot can access?
Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
Does MCP work in VS Code Remote or Codespaces?
Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.