Resources · Claude connector

Claude Frontify connectorWhat Claude can do in your Frontify account.

The Claude Frontify connector exposes 53 tools. 27 read, 22 write, 4 are undocumented. Claude reads your guidelines, assets and templates, and with the right pack it uploads, tags, organises and routes them. Here: what each group does, which pack unlocks what, and who decides.

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What changes for brand and marketing teams

Your brand lives in Frontify: guidelines, logos, fonts, colours, templates. The connector brings it into Claude, so a marketer can ask for the tone-of-voice rules or the right logo while drafting, and a brand manager can have files uploaded, tagged and sent for review without opening the Frontify interface.

On-brand answers while you write. Drafting a launch email, you ask how the brand talks about pricing. frontify_list_guidelines finds the guideline and frontify_get_guideline_page reads the page, so Claude quotes your own rules back.

Creative from approved templates. A regional team needs a social visual in the house style. frontify_export_creative starts an export from a brand template with your text, and frontify_get_creative_export returns the download link when it is ready.

Tidy a messy library. After a photo shoot, frontify_upload_file and frontify_create_asset bring the files in, and frontify_move_assets puts them in the right folder.

What it will not do on its own: Frontify groups tools into packs, and the default one, discovery, only reads. Writing needs a write-capable pack chosen by an administrator, and only one pack is active at a time for the whole account. Nothing runs by itself either: no asset is tagged automatically when it lands. For hands-off routines, an automation tool is the right fit, a different job listed on our Integrations page. To track review work next to it, the Claude asana connector can join the same chat.

Vocabulary

The vocabulary in one minute

Five words you will meet while connecting Frontify.

Connector
The link you set up once between Claude and an account you already own, so Claude can work in it while it answers you.
Tool
One named thing a connector lets Claude do. Claude picks the tools it needs on its own; the directory lists them by name.
Authorization
The service's own sign-in screen, where you grant the access Claude will use afterwards. Given once per person and revocable.
Approval
The confirmation Claude waits for before doing something that changes your account, shown in the chat at the moment it matters.
MCP
The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service such as Frontify.
Connect

Plug Frontify into Claude in three steps

  1. 01

    Find Frontify in Claude

    In Claude's settings, open Customize, then Connectors, and look for Frontify in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable the connector first; members then sign in one by one.

  2. 02

    Start the connection

    Click Connect on its row; you are then sent to your own Frontify login page to authenticate. If the link breaks later, use Disconnect and connect again.

  3. 03

    Read the authorization screen

    Read Frontify's authorization screen before you accept. It belongs to Frontify, not to Claude, and it sets what the access covers. You can withdraw that access later from the Frontify side.

Tools

The 53 tools, sorted by what they do

Frontify gives Claude 53 tools: 27 that read your account, 22 that change something in it, and 4 no official source describes.

Twenty-seven tools read, twenty-two change your Frontify content, and four are named on the directory sheet without any description. Which ones Claude actually sees depends on the active pack. Names stay in English, exactly as Claude shows them.

  • 27 read
  • 22 write
  • 4 not documented

What Claude reads (27)

27 tools

Twenty-seven read-only tools: brands, guidelines, libraries, assets, templates and workflow settings.

frontify_display_assets

Displays Frontify assets in a visual widget inside the conversation. Frontify calls it the only path to download an asset or open it in Frontify.

When it helps
a salesperson needs the current logo pack for a proposal and wants to grab it straight from the chat.

Sourcemcp.frontify-integrations.com · September 30, 2026 ↗

frontify_display_templates

Presents creative templates in a widget, as a detailed card for one template or a grid for several, so you can pick visually.

When it helps
the events team wants to see every approved banner template before choosing one for a trade show.

Sourcemcp.frontify-integrations.com · September 30, 2026 ↗

frontify_generate_url

Generates a Frontify web address that leads to a specific resource, so Claude can hand you a link rather than directions.

When it helps
a colleague is lost in the brand portal and you want to point them straight at the right guideline page.

Sourcemcp.frontify-integrations.com · September 30, 2026 ↗

frontify_get_asset_comments

Retrieves the comments and annotations left on an asset, optionally filtered by status, so Claude can summarise the feedback in a few lines.

When it helps
a designer returns from leave and wants to know what reviewers said about the new packaging.

Sourcemcp.frontify-integrations.com · September 30, 2026 ↗

frontify_get_assets_data

Fetches the metadata of assets without a widget, choosing which groups of properties to return, which suits questions about licences, tags or dimensions.

When it helps
legal asks whether a campaign photo is cleared for print before it goes out.

Sourcemcp.frontify-integrations.com · September 30, 2026 ↗

frontify_get_brand

Returns detailed information about a brand, including its libraries and projects, the natural first step before Claude digs into one specific area of your content.

When it helps
an agency just joined and wants to know how your brand's content is organised.

Sourcemcp.frontify-integrations.com · September 30, 2026 ↗

frontify_get_brand_color_palette

Retrieves a single brand palette with its colours and the values of each one in several formats, ready to quote in a brief or a style sheet.

When it helps
a developer needs the exact hex and RGB values of the secondary palette.

Sourcemcp.frontify-integrations.com · September 30, 2026 ↗

frontify_get_brand_font_families

Returns the brand's font families and the styles available from each font provider, exactly as they are defined in the brand essentials.

When it helps
a freelancer asks which typeface and weights to use for headings in a slide deck for a client pitch.

Sourcemcp.frontify-integrations.com · September 30, 2026 ↗

frontify_get_collaborators

Lists the people who can access a library or project, with their names, emails and roles.

When it helps
before sharing a confidential launch folder, you want to check who can already see it.
Watch out
the answer contains colleagues' email addresses, so mind where you paste it.

Sourcemcp.frontify-integrations.com · September 30, 2026 ↗

frontify_get_collection_assets

Returns a light list of the assets in a collection, IDs and titles only, without a widget, which is enough for Claude to count or compare.

When it helps
you want to know whether the spring campaign collection already includes the product shots.

Sourcemcp.frontify-integrations.com · September 30, 2026 ↗

frontify_get_creative_export

Checks where a creative export job stands and, once it has finished, returns the download links for the result.

When it helps
you launched a batch of social visuals a few minutes ago and want to know if they are ready.

Sourcemcp.frontify-integrations.com · September 30, 2026 ↗

frontify_get_current_user

Retrieves the profile of the Frontify user currently signed in, so Claude knows whose permissions frame every answer it gives.

When it helps
several people share one Claude workspace and you want to confirm which Frontify account is actually connected.

Sourcemcp.frontify-integrations.com · September 30, 2026 ↗

frontify_get_folder_contents

Lists the subfolders of a folder and a light list of its assets, IDs and titles only, so Claude can describe what is stored where.

When it helps
you inherited a library and want to know what sits in an old campaign folder before deciding what to keep.

Sourcemcp.frontify-integrations.com · September 30, 2026 ↗

frontify_get_guideline

Retrieves a specific guideline with its page structure, the table of contents Claude needs before reading any page in it.

When it helps
you want an overview of what the brand book covers before a workshop with a new agency.

Sourcemcp.frontify-integrations.com · September 30, 2026 ↗

frontify_get_guideline_page

Reads a guideline page as text with its headings, blocks and image addresses; Frontify adds that visually capable AI can also interpret the images on the page.

When it helps
a copywriter wants the exact tone-of-voice rules while drafting a newsletter.

Sourcemcp.frontify-integrations.com · September 30, 2026 ↗

frontify_get_library

Returns a library's structure: its folders, assets, collections, licences and the custom metadata fields it uses, in one overview.

When it helps
you are auditing the image library and want to see which licences and metadata fields exist before planning a clean-up.

Sourcemcp.frontify-integrations.com · September 30, 2026 ↗

frontify_get_library_page_assets

For one page of a library, gives the assets placed on it as a light list, IDs and titles only, without a widget.

When it helps
you want to check that the icon page of the brand portal lists every icon the design team delivered last month.

Sourcemcp.frontify-integrations.com · September 30, 2026 ↗

frontify_get_project

Retrieves a project's structure with its folders and assets, the working space where a team collaborates on files for a given job.

When it helps
a project lead wants a quick inventory of what the agency has already dropped into the rebrand project.

Sourcemcp.frontify-integrations.com · September 30, 2026 ↗

frontify_get_targets

Retrieves the targets configured in the Frontify account, the categories used to mark which channel or use an asset is meant for, such as print or social.

When it helps
you want to know which channels exist before asking Claude to categorise new visuals.

Sourcemcp.frontify-integrations.com · September 30, 2026 ↗

frontify_get_templates_data

Fetches full data on creative templates without a widget, including their variables and export options, so Claude knows what can be filled in.

When it helps
you want to know which text fields a poster template accepts before briefing Claude.

Sourcemcp.frontify-integrations.com · September 30, 2026 ↗

frontify_get_workflow_statuses

Retrieves the workflow statuses set up for a given library, the successive stages an asset goes through during review before approval.

When it helps
you want to know which stage follows the legal check in your review pipeline before routing a file.

Sourcemcp.frontify-integrations.com · September 30, 2026 ↗

frontify_list_brand_color_palettes

Lists summaries of a brand's colour palettes from its essentials, the overview Claude reads before opening any single palette in detail.

When it helps
a web agency asks how many palettes the brand defines and what each one is called.

Sourcemcp.frontify-integrations.com · September 30, 2026 ↗

frontify_list_brands

Lists every brand available in the Frontify account with IDs, names and visual identities, the starting point on multi-brand accounts.

When it helps
a group with several labels wants Claude to work on the right brand from the first question.

Sourcemcp.frontify-integrations.com · September 30, 2026 ↗

frontify_list_creative_templates

Lists the creative templates available in a brand, a quick catalogue of ready-made formats before anything gets exported from one of them.

When it helps
a franchise owner wants to know which approved formats exist for local promotions in their town.

Sourcemcp.frontify-integrations.com · September 30, 2026 ↗

frontify_list_guidelines

Lists all guidelines available for a brand with names, IDs and web addresses, so Claude picks the right one to read.

When it helps
you are unsure whether social media rules sit in the main brand book or a separate guide.

Sourcemcp.frontify-integrations.com · September 30, 2026 ↗

frontify_read_asset

Fetches Frontify-hosted images as inline content so Claude can analyse them visually, not just read their titles and metadata.

When it helps
you want Claude to describe a set of product photos in order to draft accurate alt text for each of them.

Sourcemcp.frontify-integrations.com · September 30, 2026 ↗

frontify_search_assets

Searches assets in a library, project or brand with advanced filters and returns light matches, IDs and titles, without a widget.

When it helps
you need every approved photo of the Paris store taken this year.
Watch out
to view or download results, Claude goes through the asset display tool.

Sourcemcp.frontify-integrations.com · September 30, 2026 ↗

What Claude changes (22)

22 tools

Twenty-two tools that add, organise, route or cancel things in Frontify. No source gives them their own confirmation: the general rule below applies.

frontify_add_asset_revision

Approval: see the rule

Adds a new revision to an existing asset from a file already uploaded, the last step of a three-step upload.

What Claude asks for
no source documents a prompt of its own before a revision is added; the general approval rule governs it.
When it helps
the updated product sheet should replace last year's version without breaking links.

Sourcemcp.frontify-integrations.com · September 30, 2026 ↗

frontify_add_asset_revision_from_url

Approval: see the rule

Downloads a file from a public web address and sets it as the current revision of an existing asset in one go.

What Claude asks for
replacing a revision from a link has no documented prompt of its own, so the default rule decides.
When it helps
the agency shared the final logo through a public link and it should become the current version.

Sourcemcp.frontify-integrations.com · September 30, 2026 ↗

frontify_add_asset_tags

Approval: see the rule

Adds tags to assets. Frontify's help centre only describes it in general terms, as part of organising and tagging assets.

What Claude asks for
tagging carries no documented confirmation of its own; it follows the general rule.
When it helps
fifty event photos need the tag of the conference they came from.

Sourcehelp.frontify.com · September 11, 2026 ↗

frontify_add_asset_targets

Approval: see the rule

Adds targets to one or more assets to categorise them for a channel or a use case.

What Claude asks for
assigning targets comes with no specific confirmation in any source; approvals work as described below.
When it helps
the new banners should be marked for paid social so the ads team finds them.

Sourcemcp.frontify-integrations.com · September 30, 2026 ↗

frontify_add_collection_assets

Approval: see the rule

Puts assets into a collection. Frontify's help centre covers it only as part of building collections, without a dedicated description.

What Claude asks for
filling a collection has no documented prompt; the default rule applies to it.
When it helps
you want a ready-to-share set of press images for a product launch.

Sourcehelp.frontify.com · September 11, 2026 ↗

frontify_add_custom_metadata

Approval: see the rule

Applies custom metadata values to assets. Frontify's help centre only mentions it within assigning metadata, with no finer detail.

What Claude asks for
writing metadata values has no confirmation described anywhere, beyond the general rule.
When it helps
every new photo needs its photographer's name and usage rights recorded.

Sourcehelp.frontify.com · September 11, 2026 ↗

frontify_add_workflow_checklist_item

Approval: see the rule

Adds an item to the checklist of an existing workflow task, so reviewers know what still has to be verified.

What Claude asks for
adding a checklist item is not tied to any documented prompt; the default rule covers it.
When it helps
legal wants "check trademark symbol" on every packaging review.

Sourcemcp.frontify-integrations.com · September 30, 2026 ↗

frontify_cancel_creative_exports

Approval: see the rule

Stops one or more creative export jobs that are still processing or rendering. Frontify files it among its destructive tools.

What Claude asks for
cancelling exports has no dedicated confirmation in the sources; the general approval rule is what applies.
When it helps
you launched a batch with the wrong headline and want to halt it before anyone downloads it.

Sourcemcp.frontify-integrations.com · September 30, 2026 ↗

frontify_create_asset

Approval: see the rule

Creates the asset record in Frontify from a file uploaded beforehand, the third and last step of the upload sequence.

What Claude asks for
creating the asset record has no prompt of its own on record; the default rule handles it.
When it helps
the shoot photos are uploaded and now need to appear as proper assets in the library.

Sourcemcp.frontify-integrations.com · September 30, 2026 ↗

frontify_create_asset_comment

Approval: see the rule

Adds a comment, an annotation or a reply to a Frontify asset, visible to the people reviewing it.

What Claude asks for
posting a comment has no documented confirmation specific to it; the general rule applies.
When it helps
you want Claude to post your feedback on a draft poster right where the designer will see it.

Sourcemcp.frontify-integrations.com · September 30, 2026 ↗

frontify_create_asset_from_url

Approval: see the rule

Creates an asset from a public web address: Frontify downloads the file, uploads it and creates the asset in one step.

What Claude asks for
creating an asset from a link has no specific confirmation described; the general approval rule covers it.
When it helps
a partner shared visuals through a public link and they belong in your library.

Sourcemcp.frontify-integrations.com · September 30, 2026 ↗

frontify_create_collection

Approval: see the rule

Creates a collection, a virtual grouping of assets in a library that does not move the files themselves.

What Claude asks for
opening a new collection has no documented prompt, so the default rule is the one in force.
When it helps
you want one place for everything related to the autumn campaign across several folders.

Sourcemcp.frontify-integrations.com · September 30, 2026 ↗

frontify_create_custom_metadata_property

Approval: see the rule

Defines a new custom metadata property on a library, without going through the admin interface.

What Claude asks for
defining a metadata field has no dedicated confirmation in the sources; the general rule governs it.
When it helps
the team decides to record a usage expiry date on every licensed image.
Watch out
the new field appears for everyone using that library.

Sourcemcp.frontify-integrations.com · September 30, 2026 ↗

frontify_create_folder

Approval: see the rule

Creates a folder inside a library, a project or another folder to organise assets.

What Claude asks for
no source attaches a confirmation to folder creation; the default rule covers it.
When it helps
each regional office needs its own folder in the event library before the season starts.

Sourcemcp.frontify-integrations.com · September 30, 2026 ↗

frontify_create_project

Approval: see the rule

Creates a project within a brand for collaborative file work, the space where a team gathers files for a given job.

What Claude asks for
setting up a project has nothing tool-specific documented; the general approval rule applies.
When it helps
a rebrand kicks off and the agency needs a shared workspace from day one.

Sourcemcp.frontify-integrations.com · September 30, 2026 ↗

frontify_create_workflow_task

Approval: see the rule

Creates a workflow task. Frontify's help centre only describes it in general terms, as part of routing assets for review.

What Claude asks for
opening a review task has no documented confirmation of its own; the default rule applies.
When it helps
a new brochure is ready and the brand team should review it before print.

Sourcehelp.frontify.com · September 11, 2026 ↗

frontify_export_creative

Approval: see the rule

Starts an export job that generates a design from a creative template with the text and values you give, delivered once processing ends.

What Claude asks for
launching an export has no specific confirmation described; the general rule covers it.
When it helps
ten store managers each need the same poster with their own opening hours.

Sourcemcp.frontify-integrations.com · September 30, 2026 ↗

frontify_move_assets

Approval: see the rule

Moves one or more assets to another folder within the same library or workspace. Frontify labels it destructive.

What Claude asks for
moving assets has no documented prompt of its own; the general approval rule applies.
When it helps
last year's campaign files should leave the active folder for the archive.
Watch out
colleagues who knew the old location will look in the wrong place.

Sourcemcp.frontify-integrations.com · September 30, 2026 ↗

frontify_remove_asset_targets

Approval: see the rule

Removes specific targets from one or more assets while keeping the other targets assigned to them. Frontify's pack page tags it as destructive.

What Claude asks for
removing targets has nothing tool-specific on record; the default rule covers it.
When it helps
a visual is withdrawn from print but stays valid for social media.

Sourcemcp.frontify-integrations.com · September 30, 2026 ↗

frontify_remove_workflow_checklist_item

Approval: see the rule

Removes an item from a workflow task's checklist. Frontify puts it in its destructive category.

What Claude asks for
deleting a checklist item has no confirmation of its own in any source; the general approval rule applies.
When it helps
a check was added by mistake and blocks a task from being marked complete.

Sourcemcp.frontify-integrations.com · September 30, 2026 ↗

frontify_update_workflow_checklist_item

Approval: see the rule

Updates the content, the assignee or the completion state of a checklist item in a workflow. Despite the word update, Frontify marks it destructive.

What Claude asks for
editing a checklist item has no dedicated confirmation documented; the default rule governs it.
When it helps
the legal check moves from one reviewer to another during holidays.

Sourcemcp.frontify-integrations.com · September 30, 2026 ↗

frontify_upload_file

Approval: see the rule

Opens a file upload to Frontify and returns temporary addresses where the file content is sent, the first of three upload steps.

What Claude asks for
starting an upload has no documented confirmation for it; the general rule applies.
When it helps
you drop new product photos into the chat and want them in Frontify.

Sourcemcp.frontify-integrations.com · September 30, 2026 ↗

Undocumented (4)

4 tools

The directory publishes these four names and nothing more. No official text says what they do, and this page will not guess from the names.

frontify_delete_workflow_task

The directory sheet lists this name, and that is all anyone has published. Neither Frontify's help centre nor its pack page describes it, so this page adds nothing.

Watch out
whatever it does, the general approval rule below covers it.

frontify_move_workflow_task

Same situation here: the name appears in the tool list and no official source documents it. Guessing its purpose from the name would be a claim this page cannot back up.

Watch out
it falls under the same general approval rule as every other tool.

frontify_reply_to_comment

Listed on the directory sheet, missing from Frontify's help article and from its official pack page: there is simply no text to rely on for this tool.

Watch out
the default approval rule applies to it like to every other tool.

frontify_update_asset

Only its name is public. Neither Frontify's help article nor its pack page mentions it, so no official source says what it does, nor whether it reads your library or changes it. This page will not fill that gap with a guess.

Watch out
treat it as covered by the general approval rule, and nothing more.
Approvals

What Claude asks before acting

By default, Claude stops and asks for your confirmation before each action it takes on an account on your behalf. With Frontify that matters: twenty-two tools can add, organise, route or cancel things, and Frontify labels some of them destructive.

On Team and Enterprise, workspace owners decide whether members can let some actions pass without a prompt, and they can restrict what a connector does for the whole organisation, keeping reads and closing writes for instance. Nobody overrides that from their own account. Claude works with your Frontify rights only: what you cannot open there stays closed to it. On Frontify's side, the active pack decides which tools exist at all.

Plans

Which plans include it

Of the 819 sheets in the official directory, none displays availability by plan. The connector-by-connector answer is published nowhere, a genuine gap in the catalogue.

The general rule is published: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner switches the connector on for the organisation before members can connect. Frontify's own help article says something more specific, set side by side in the limits section. The connector's sheet in the official directory shows its current state.

Limits

Where this connector stops

A connector is not an automation. Claude calls these tools while it answers you: nothing runs by itself when a file lands or a review stage changes.

The tool list is an observed floor, not a promise: an admin can open actions no public sheet shows, and on Frontify the active pack changes the set Claude sees. The partner badge is not a security audit, and Anthropic says on every sheet that it does not pick a publisher's tools. Everything here comes from Frontify's help centre and its official pack page; neither Claude's help centre nor Anthropic's developer docs cover this connector.

Two official sources disagree

Which Claude plans can use the Frontify connector?

What this page followsBoth pages are current and they do not contradict each other so much as speak from different places: Anthropic states the rule for every connector, Frontify names plans for its own. Neither is Anthropic confirming this connector on your account, so check the Frontify sheet in the directory while signed in to Claude.

Need help

Need help connecting Frontify to Claude?

A person reads every message.

FAQ

FAQ about the Claude Frontify connector

01What can Claude do with the Frontify connector?
Claude can read your brand in Frontify and, with a write-capable pack, act on it. Reading covers brands, guidelines and their pages, libraries, projects, assets and their metadata, colours, fonts, templates and workflow statuses. Writing covers uploading and importing files, revisions, tags, targets, metadata, folders, collections, projects, comments, review tasks and checklist items, plus exporting designs from templates. Four listed tools have no description. You ask in plain words, and Claude picks the matching tool.
02Can Claude upload, move or delete things in Frontify?
Yes, when a write-capable pack is active. Twenty-two tools can upload and import files, add revisions, tags, targets and metadata, create folders, collections, projects and review tasks, comment, export creatives and move assets. Frontify labels several as destructive, including moving assets, removing targets, cancelling exports and editing or removing checklist items. The default discovery pack is read-only, and Frontify advises starting there and backing up important data before enabling writes.
03Does Claude ask before it changes my Frontify content?
By default, yes: Claude stops and asks for confirmation before each action it takes on an account on your behalf. No source describes a confirmation specific to any Frontify tool, so that default rule covers the writing tools and the four undocumented ones. On Team and Enterprise, workspace owners decide which actions members may let pass without a prompt and can close writing for everyone. On Frontify's side, the active pack decides whether writing tools exist at all.
04Which Claude plans is the Frontify connector on?
No official source publishes plan availability connector by connector, and no directory sheet displays it. Anthropic's general rule is that remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, with an Owner or Primary Owner switching them on first on Team and Enterprise. Frontify's help article names specific plans for its connector, quoted in the limits section. The Frontify sheet in the official directory is the only place showing the current state for your account.
05Does Claude see our whole Frontify account?
Claude works with the rights of the Frontify user who connected, and only with the tools of the active pack. On the default discovery pack it can read brands, guidelines, libraries, projects, assets and templates, but not change them. Administrators can switch to another pack from inside the AI tool, and that choice applies to every user of the account. On the Claude side, a Team or Enterprise owner can restrict what the connector does for the organisation.
06What are Frontify tool packs and why do they matter?
Packs are bundles of Frontify tools matched to a use case and a risk level. Connecting through the main address starts on the default discovery pack, which is read-only, and lets administrators switch packs from inside the AI tool. Only one pack is active at a time and a switch affects everyone on the account. According to Frontify's help centre, the default pack makes no changes to Frontify data at all, which is why it is the recommended starting point before any write-capable pack.
07Claude or an automation tool for Frontify?
They do different jobs, so choose by use. Claude with this connector is for work you describe in a conversation: find the right guideline, fetch an asset, upload and tag a batch, export a design from a template. It never acts on its own, so it will not tag each new upload overnight or push assets somewhere when a review closes. Recurring routines belong to an automation platform, a different kind of tool rather than a better or worse one.