Frontify Integrations

Marketplace / app directory

• Frontify Marketplace (in-product, opened from the Power Bar): central distribution hub for Content Blocks (guideline components), Apps (React single-page apps on asset/guideline surfaces), Themes (guideline look and feel) and also lists Integrations S132 S49. Viewers, editors and admins can browse; only account admins install; admins can hide it from viewers S132. Public showcase: frontify.com/en/marketplace S166.
• Size: number of listed extensions Not public. Built-in guidelines ship ~40 pre-installed content blocks S48 S55; the public integrations directory lists about 75 integrations (incl. "light" embed integrations) S163.
• How extensions are built: Brand SDK (TypeScript/React, @frontify/app-bridge*, @frontify/frontify-cli, Fondue design system) → frontify-cli create → local dev server connected in "developer mode" → deploy to a draft Marketplace entry (App ID in manifest.json) → publish → install S48 S51 S52. App surfaces: asset action, bulk asset actions, asset creation, asset viewer (alpha), theme action (alpha); App Bridge methods include executeGraphql, createAsset, executeSecureRequest S53.
• Private vs public: extensions can stay private to one account, be shared to another account with a share code, or be published to the community after a 5-stage Frontify review (metadata, automated pre-screening for dangerous code/deployability/tampering/manifest, …); community extensions reach the "1200+ Enterprise customers" S49 S133.
• Apps vs integrations (Frontify's definition): apps run inside Frontify; integrations run inside the external tool S134.

Native connectors

Availability ("Free", "Paid", "3rd party", "Light") is shown per card on the integrations directory; paid status below is only stated where a help article confirms it S163.

AI & agent ecosystem

• Frontify MCP Server (official, hosted by Frontify): base endpoint https://mcp.frontify-integrations.com/mcp, plus one endpoint per tool pack (/mcp/packs/{pack}) S67 S66.

  Pack	Tools	Scopes	Purpose
  discovery (default, read-only)	24	basic:read, blocks:read	Brands, libraries, projects, assets, guidelines, templates
  admin	47 (all)	basic:read/write, account:read, blocks:read	Full access
  collaboration	20	basic:read/write	Comments, replies, workflow tasks
  asset-organization	18	basic:read/write	Tags, targets, metadata, collections, folders
  asset-creation	19	basic:read/write	Upload/update assets, tags, metadata, targets
  creative-automation	19	basic:read/write	List templates, export creatives, upload results
  workflow-automation	18	basic:read/write	Statuses, tasks, comments
  brand-admin	18	basic:read/write	Projects, folders, collections, metadata properties
  brand-portal	12	basic:read, blocks:read	Guidelines and library-page assets
  bulk-operations	15	basic:read/write	Multi-asset moves, updates, metadata, targets

  Source of the table: live landing page S66. Unverified The Help Center says 52 tools and a 25-tool discovery pack S75; the live page shows 47 / 24.

• Auth: MCP authorization spec with OAuth 2.1 metadata (/.well-known/oauth-protected-resource, authorization server with /oauth/authorize, /oauth/token, /oauth/register), PKCE S256, public clients, Client ID Metadata Documents and Dynamic Client Registration; scope mcp:tools; users then log in with their Frontify account, and the MCP respects their Frontify permissions S67 S66 S150.

• Clients documented: official Claude connector (Claude, Claude Desktop, Cowork; Free/Pro/Max/Team/Enterprise), ChatGPT connector, Microsoft Copilot Studio (MCP onboarding wizard), Figma Make (custom connector), Cursor, Windsurf and other config-file clients S75 S155 S67.

• Enablement & status: account admins activate it under Applications → Public Apps; no extra charge S75; beta for all interested customers in June 2026 S150; MCP usage counts towards MAU from 2026-09-01 S108.

• Limits: the connection is not scoped to one brand/library — the agent sees everything the user can see; retrieval goes through Frontify's Content API, which lacks semantic search and navigation hierarchy, so prompts must name brand/library explicitly S76. Data sent to the AI tool is processed under that provider's policies S75 S155.

• Microsoft Copilot (API-based, legacy path): two custom Copilot Studio configurations using the Guideline content API and DAM asset search API; not plug-and-play; no native Microsoft 365 Copilot integration; MCP now recommended S77 S60.

• In-product AI: Brand assistant (RAG over guidelines), Agentic hub, Automations with OpenAI actions, Enhanced image search (Azure OpenAI) — see Features S115 S116 S112 S85.

• llms.txt: published at https://www.frontify.com/llms.txt (product map, MCP guidance, API links) S155 and for the GraphQL reference at https://frontify.github.io/graphql-api-reference/llms.txt (agent-oriented .md / .sdl files) S62. The developer portal itself has no llms.txt (SPA) S1.

Integration platforms

Partners

• Partnership program for agencies: sales commissions, expert support, partner qualification to deliver Frontify to clients; public partner directory and "get matched" service S156 S167 S172.
• Technology/ecosystem partners visible through integrations: CI HUB, LinkrUI, Storyteq, Templafy, Canva, Ciloo, Codetribe (FLUX Kontext image editing app), Jung von Matt (Scenar.io app) S138 S153 S163 (Help Center Apps / Developer Platform collections).
• Extension builders cited by Frontify: Liip (Maps block), NFQ (content blocks, integrations) S166 S167.
• Developer community: "Frontify Friends" Slack (API change announcements, direct contact with Frontify engineers), developer newsletter, bug-report form S6 S34.