# Style3D MCP

> Style3D connects your AI agent directly to a full digital fashion pipeline. You manage 3D assets, browse entire garment libraries, check material properties (like fabric simulation data), and trigger high-quality cloud renders—all through natural conversation. It handles every step from project planning to visualization without you leaving the chat.

## Overview
- **Category:** design-creative
- **Price:** Free
- **Tags:** 3d-fashion, digital-fashion, garment-design, fabric-simulation, cloud-rendering

## Description

Style3D connects your AI agent directly to a full digital fashion pipeline. You manage 3D assets, check material properties, browse entire garment libraries, and trigger high-quality cloud renders—all through natural conversation with your client.

You're not juggling PLM software, asset trackers, and rendering engines anymore. Your agent uses specific tools like `list_projects` or `get_fabric` to pull up all the necessary data (metadata, material specs, 3D file info) and execute complex tasks. It handles everything from planning a collection to generating final visualizations without you leaving the chat.

**Managing Projects and Scope**

You start by getting an overview of every design project using `list_projects`, which shows all maintained 3D designs in the system. You can then pull specific metadata for any single project with `get_project`. These tools let you audit project status, track asset ownership, and understand what's associated with a given ID.

**Inventorying Materials and Styles**

Need to check the fabrics? Use `list_fabrics` to get an inventory of every textile in the database. For deep details on any single material, call `get_fabric`; this returns detailed specifications and physical simulation properties for that fabric ID.

The server also keeps track of design presets. You can use `list_styles` to reference available saved style configurations, ensuring consistency across your lines.

**Browsing Garments and Assets**

You can list every garment within a specific project or collection using `list_garments`. To get all the nuts and bolts on one piece, call `get_garment`; this pulls up details including its assigned fabrics, size runs, and current status within your active projects. The system knows exactly which 3D asset files are tied to a given job; you can review them using `list_assets` with a specific project ID.

**Generating Visualizations**

When the design is locked down, it's time for renders. You trigger the cloud rendering service to generate high-quality final images of selected garments by running the `render_garment` tool. This sends the request and delivers the completed visualization directly through your agent chat.

## Tools

### get_fabric
Retrieves detailed specifications for a single fabric ID.

### get_garment
Pulls specific details about one garment, including its current project association.

### get_project
Gets all metadata for a single 3D design project by ID.

### list_assets
Lists every available 3D asset file associated with a given project.

### list_fabrics
Retrieves an inventory of all fabrics currently in the system's database.

### list_garments
Lists every garment within a specific project or collection.

### list_projects
Retrieves an overview of all 3D design projects maintained in the system.

### list_styles
Lists available saved style presets and configuration groups for designers to reference.

### render_garment
Sends a request to generate a final, high-resolution visualization of a specific garment.

## Prompt Examples

**Prompt:** 
```
Show me all garments in the Spring Collection project.
```

**Response:** 
```
Found 12 garments in 'Spring Collection'. Notable items: 'Silk Blouse v3' (ready for render), 'Linen Trouser' (fabric assigned), 'Cotton Dress' (in review). Want me to render any of these?
```

## Capabilities

### Project Tracking
Retrieves metadata for all 3D design projects, letting you audit project status and asset ownership.

### Material Library Lookup
Accesses the fabric database to get detailed specifications and physical simulation properties of any textile.

### Garment Asset Browsing
Retrieves specific details about a garment, including its assigned fabrics, size runs, and status within a project.

### Asset Management
Lists all 3D asset files associated with a given project ID for review or retrieval.

### Visualization Generation
Triggers the cloud rendering service to generate high-quality, final images of selected garments.

## Use Cases

### Checking Material Compatibility
A technical designer needs to see if a new, heavy-weight fabric works with an existing garment silhouette. They ask the agent: 'What are the properties of Fabric X, and does it work for the Autumn Blazer?' The agent runs `get_fabric` first, then cross-references that data against the blazer's profile using `get_garment`, giving a single pass/fail answer.

### Audit an Entire Collection
A production manager needs to verify if all 12 garments in the 'Spring Collection' are ready for final photography. They prompt: 'List all assets and check the render status for Spring Collection.' The agent runs `list_garments` then `list_assets`, compiling a comprehensive readiness report.

### Drafting a New Style Line
A designer has finished Project Beta and needs to visualize the final pieces. They prompt: 'Render the silk blouse using the linen fabric.' The agent uses `get_garment` to confirm the asset ID, then calls `render_garment`, delivering the final visual output directly.

### Finding Design Limitations
A new designer is stuck on a style choice. They ask: 'What are our established design constraints?' The agent runs `list_styles` and provides access to saved, pre-vetted configuration presets, stopping them from wasting time on non-approved designs.

## Benefits

- Centralized Project Status: Use `list_projects` to get a high-level overview of every active design project. You don't need to log into multiple PLM dashboards just to see if all assets are finalized.
- Deep Material Inspection: Instead of guessing, run `get_fabric` to check precise physical simulation properties. This is crucial for technical designers who know that fabric weight matters as much as color.
- One-Shot Visualization: Trigger renders with `render_garment`. You don't have to export a model and upload it elsewhere; you just ask the agent, and it handles the cloud processing.
- Guided Asset Discovery: If you're unsure which assets belong where, use `list_assets` after specifying the project ID. It pulls up every 3D file associated with that collection.
- Comprehensive Lookups: You can list all available items (`list_garments`, `list_fabrics`) and then drill down on one specific item using its unique ID (`get_garment`).

## How It Works

The bottom line is that you use conversation to run complex design tasks that usually require multiple apps and manual data entry.

1. Subscribe to the Style3D server and get your Enterprise API key from Style3D.
2. Input the API credentials into your preferred AI client (Claude, Cursor, etc.).
3. Ask a natural language question, like "What fabrics are available for Project Zenith?" The agent selects and runs `list_fabrics`.

## Frequently Asked Questions

**How do I find out what fabrics are available using list_fabrics?**
You ask the agent to run `list_fabrics`. This gives you a full inventory, including unique fabric IDs and basic details. You then use `get_fabric` with a specific ID if you need deep specs like weave count or simulation properties.

**Can I check project status using get_project?**
Yes. Use `get_project` by providing the unique Project ID. This returns all metadata—asset counts, owner IDs, and last modification dates—allowing you to audit its current state in one go.

**How do I see every garment in a project? list_garments?**
Simply ask the agent to run `list_garments` and provide the Project ID. It returns a clean list of all garments, letting you quickly identify items that might need rendering or updates.

**Do I have to switch tools to render an item? render_garment?**
No. You ask the agent to run `render_garment` and specify the garment. The server handles the API call, cloud queue management, and status updates for you—all within your chat interface.

**What if I only know the style name? list_styles?**
Use `list_styles` to see all saved presets. You can then reference a Style ID when asking the agent to check assets or render, ensuring consistency across your collection.

**How do I use list_assets to see all 3D files and metadata within a specific project?**
It returns a comprehensive list of every file associated with the project. This includes asset names, their current revision number, and whether they are ready for rendering.

**What happens if I use get_fabric but provide an inactive or non-existent fabric ID?**
The tool returns a specific error code detailing the invalid request. You must verify that the Fabric ID is active and properly linked to your project before querying.

**When I call get_garment, what key technical specifications should I expect in the output?**
You receive detailed metadata for the garment, including assigned fabric IDs, fit notes, construction measurements, and its current status within the design pipeline.

**Can I trigger garment renders directly?**
Yes! The `render_garment` tool lets you trigger high-quality cloud renders for any garment in your library. Results are returned as downloadable image URLs.