How to use PolyDrobe.

PolyDrobe is a game asset management platform for documenting, versioning and collaborating on apparel assets: skins, cosmetics and accessories across a game project. It gives you a structured, searchable database in place of the spreadsheets most teams start with.

PolyDrobe is designed for game apparel and cosmetic items: character skins, outfits, accessories, weapons, and any item that has multiple visual variants. Each asset can have multiple variants representing different colorways, quality tiers, or seasonal versions.

Yes. PolyDrobe includes a built-in 3D model viewer that renders .glb and .gltf files directly in the browser. You can attach mesh files to assets and texture files to variants and preview them without leaving the app.

Google Sheets has no structured data types, version tracking, role controls or media handling. PolyDrobe gives you dedicated fields for rarity, status, price, release version and tags, stores thumbnails and 3D models on the record, and enforces role-based access.

Notion and Airtable are general database tools, and you build the game-asset schema yourself. PolyDrobe ships that schema: asset-variant hierarchy, 3D model viewer, texture management, pipeline statuses, rarity levels and release versioning.

PolyDrobe is engine-agnostic. It documents and coordinates the catalogue while your engine runs the game, so teams on Unity, Unreal Engine, Godot or a custom engine all use it the same way. JSON and Excel export and the MCP server carry the data into your pipeline.

Yes. PolyDrobe has a Model Context Protocol (MCP) server at https://polydrobe.app/mcp. Every read, write, search and export operation is exposed as a tool. AI assistants such as Claude and ChatGPT can connect using a Bearer token, then list projects, manage assets, variants, bundles and collections, configure classifications, assign tags, bulk-update entries, and search the database using natural language. See the Developer Guides section for setup instructions.

Both reach the same data through the same service layer. The REST API uses standard HTTP methods (GET, POST, PATCH, DELETE) with JSON envelopes, which suits scripts, CI/CD pipelines and custom integrations. The MCP server speaks the Model Context Protocol, so AI assistants such as Claude and ChatGPT can work with your data in plain language. Both need a Pro plan and OAuth2 authentication.

Go to Workspace Settings > API Tokens and click Create token. Give it a name, select scopes (read, write) and choose an expiration period. Copy the token when it appears, because it is shown once. The same token works for the REST API and the MCP server, and both need a Pro plan.

Yes. Projects support multiple team members with three roles: Owner (full control including settings and billing), Editor (can create and update assets and variants), and Viewer (read-only access for QA or stakeholder review). Invite teammates by email from Project Settings.

Use one asset for the core item and variants for each skin or version. For example, a Hoodie asset might have variants named Hoodie Blue, Hoodie Red, and Hoodie Gold. The asset holds shared properties like mesh file and category; variants hold per-version properties like texture, price, and rarity.

Use clear naming conventions and rely on slug-based URLs for stable references. PolyDrobe auto-generates URL slugs from names, so a consistent naming convention produces consistent, human-readable URLs that remain stable even if the display name changes.

Yes, on plans that include Data Exchange. Use the Data Exchange page to export the full project to JSON or Excel, or to a ZIP package that carries the media files too, and share it with downstream tools, publishers, or external contractors.

The Free plan includes 1 owned project, up to 3 members, 1 GB of workspace storage, unlimited assets, 100 variants per project, and 30 days of activity retention.

No. Only Owner and Editor roles are billable seats. Viewers stay free regardless of how many you add.

Yes. PolyDrobe is a web-based SaaS application hosted at polydrobe.app. There is no software to install. Sign up, create a project, and start adding assets immediately.

Yes. PolyDrobe imports JSON, Excel (.xlsx), ZIP packages that carry media alongside the data file, and Google Sheets. Export your existing spreadsheet in the expected format and import it from the Data Exchange page. Every import is previewed first: you see the per-row create, update and error counts before committing changes.

Each worksheet uses specific columns. Categories need: slug, name, description, parent_slug. Tags need: slug, name, value. Rarities need: name, color (#RRGGBB hex), priority. Currencies need: code, name, symbol. Releases need: version, name, description, release_date (YYYY-MM-DD). Assets need: slug, name, description, category_slug, tags. Variants need: slug, name, asset_slug, rarity, release, currency, price, description, tags. Column headers are case-sensitive and must appear in the first row. The Google Sheets sync covers those seven entity types; Bundles and Collections are imported through Excel or JSON upload instead.

The file is probably an uploaded .xlsx opened in Google Sheets rather than a native Google Spreadsheet. A URL carrying 'rtpof=true' marks an uploaded file. To fix it, open the file in Google Sheets, choose File > Save as Google Sheets, then click Browse in your sync profile and pick the converted file. Check as well that the connected Google account can open the spreadsheet.

Yes. Each project requires its own Google connection for multi-tenancy isolation. Different projects may have different owners and access controls. The same Google account can be used across all projects.