We’ve packed this sprint with enhancements designed to improve your team’s productivity. We just launched the Public Beta of our MCP Server. Editorial teams gain external gallery collaboration with star ratings & color flags, plus Sequence Tokens for cleaner deliverable filenames. Followed along with native TGA file support, new Shopify Metafields.
We're always eager to hear your thoughts, so don't hesitate to share your feedback.
Public Beta for Our MCP Server
The Official MCP Server is now available in Public Beta, letting you bring your Creative Force data into AI assistants such as Claude and ChatGPT.
In this first release you can query your studio data in natural language, pulling live answers about Planning, Talent & Crew, Ecom & Editorial Production, Products, Samples and more without leaving your assistant. This makes it easier to get a quick read on your operations and surface what needs attention.
As this is a Public Beta, the current release provides limited read-only access. The range of accessible data will continue to be broadened in future releases, with editing capabilities also planned as the MCP Server develops.
Support for Targa (TGA) File Format
Targa (.tga) files are now supported natively across the platform in Ecom, removing the need to convert them outside the system and keeping your assets in a single, consistent workflow. You can ingest .tga files alongside JPEG, TIFF, and PNG, with each original stored losslessly and a web preview generated automatically.
Once ingested, TGA assets move through the same workflow as your other formats. Presets accept .tga as an output. You can deliver assets as .tga, send and receive them from external post-production partners, use in Internal Post and preview them easily in Assets view.
Preview of transparency in QC steps and ingestion of metadata are not supported for Targa files.
Editorial presets currently do not support TGA files, this will be changed in upcoming sprints.
Extended Collaboration in Editorial Galleries
External stakeholders can now apply star ratings and color flags during gallery review, alongside their existing comments and markups. All feedback is attributed by avatar and visible across every review surface, giving internal teams a complete, consolidated picture of where every reviewer stands — without chasing input across separate tools or threads.
Building on this, teams can now create a Gallery Collection directly from the Collections menu by picking an existing Gallery as the source, making it easier to move from aligned selects to a shared collection in fewer steps. Studio Admins control exactly what external reviewers can see and do through studio-level policy and per-collection Experience Settings, so each share is configured to match the needs of that review.
Sequence Tokens for Editorial Deliverables
Editorial deliverable naming conventions now support sequence tokens, so each asset in a multi-asset deliverable automatically receives a unique, sequential filename at delivery time. Studio Managers can configure the token's start value and digit padding to match exactly how downstream systems expect files to be structured — no more duplicate filenames or manual workarounds.
Sequence tokens are available at both the preset level and per individual specs, giving teams precise control over how files are named across different deliverable types.
New Shopify Metafields Support
We now support list and reference metafields with the Shopify Connector, increasing the amount of data shared from Creative Force to Shopify. The new metafields supported include all List metafields and the Reference type metafields of Product, Metaobject and Collection. These can be mapped to Creative Force property values in the Shopify Connector configuration.
Questions, Ideas or Feedback?
We’re always striving to create the best product for you and your team! Feel free to drop us a line via email/chat, or submit your ideas and feedback directly to our product team via product@creativeforce.io.