Monotype
Monotype v1.0.0
Access Licensed Brand Fonts
From the developer
Declared capabilities
- Read
- Write
Cost & access
This plugin does not sell products or process payments.
Declared limitations
- Generating New AI Fonts
- Downloading Font Files
- Retrieve or download license agreement
Onboarding example
Identify Gazpacho Regular and Bold in approved marketing cover and create a web project in Monotype library
Sources & dates
Developer declarations; not independently tested. Listing last checked Nov 6, 2026. Package observed Nov 5, 2026.
Description
From the marketplace listing
Connect ChatGPT to your Monotype Fonts library to discover and access licensed fonts. Match fonts from brand guidelines, verify production status, create Web Projects, Digital Ads, and font lists, generate CSS/CDN links for web use, and sync fonts to the Monotype Fonts desktop app.
Language: English · Automatically detected from descriptions.
Changes
No changes recorded yet. Follow this plugin to keep track of future changes.
First seen Nov 5, 2026. Last seen Nov 6, 2026.
Similar plugins
Find competitors to follow as you develop your plugin.
-
Identify fonts from images and find visually similar free font alternatives.
Shared terms: font, licensed, match, design
-
A creative suite for brand context, asset libraries, editable designs, media production, and advertising insights.
Shared terms: brand, ads, guideline, library
-
Access Linearity brand resources, manage Curve files, and create editable designs and image or SVG assets.
Shared terms: brand, font, guideline, design
-
Find free Korean fonts and check whether each one is allowed for web, print, video, logo, packaging, app or PDF use.
Shared terms: font, css, web, design
-
Make a brand's adapts with eonik: every size of a creative, on-brand, checked, approved and delivered, made in the eonik app on the perso...
Shared terms: brand, ads, approved, font
Keywords
Files & skills
File archives
Skill instructions
monotype-fonts17.7 KB
--- name: monotype-fonts description: Process uploaded brand guidelines or typed font specifications with the Monotype Fonts connector, extract font names only from document text or reliable metadata, match fonts in Monotype inventory, show production status, and then guide the user to either reuse an existing library asset or create a new Web Project, Digital Ad, or FontSet. Use when a user uploads a brand guideline/style guide/brand book/type spec or asks to apply its fonts to Monotype library assets. Also use when the user asks for a site, page, ad, or other web output for a named brand or project without supplying a guideline or font names - look up an existing Web Project or Digital Ad by that name and use its fonts and CSS. Always require explicit user consent immediately before creating any new asset. --- # Monotype Fonts ## Core rule Use only the **Monotype Fonts** connector for font matching, production status, existing-asset lookup, asset creation, and any CDN/CSS output. Support exactly these user-facing asset types: - **Web Project** (`WebProject`) - **Digital Ad** (`DigitalAd`) - **FontSet** (`FontSet`; aliases: font list, fontlist, font set, fontset, list, font collection) Never create a new asset without explicit user consent in the immediately preceding user turn. Font identity must come from written font names or reliable file metadata, never from visual similarity. ## Brand-guideline entry flow When a user uploads a supported brand guideline, style guide, brand book, or type specification, first extract and resolve the fonts as described below. Then present the asset action choice before any asset operation unless the user's prompt already unambiguously chooses both the action and asset type. When action or type is not explicit, present these two paths compactly: 1. **Use an existing asset** — choose **Web Project**, **Digital Ad**, or **FontSet**, then provide the existing asset name. 2. **Create a new asset** — choose **Web Project**, **Digital Ad**, or **FontSet**. Collect or suggest the asset name, check for duplicates, show the creation summary, and ask for explicit consent before creation. If the user's prompt already says, for example, “use existing Web Project Acme Site” or “create a new FontSet called Acme Brand Fonts,” do not ask them to choose again. Continue with the selected path while still enforcing every required approval below. Do not infer **Digital Ad** unless the user explicitly selects or requests it. If the user chooses an action but not an asset type, ask them to select one of the three types rather than silently defaulting. ## Project-name fallback flow Use this flow when the request needs brand fonts (for example a website, landing page, HTML ad, or other web output) but **no brand guideline is uploaded and no font names are written in the prompt**. Check the conversation's uploads first; an upload that is not a guideline for this brand does not count. 1. **Derive the lookup name.** Take the project, brand, campaign, or site name from the user's prompt (for example `VEXTOR` from "a launch page for VEXTOR"). If the prompt contains no usable name, ask for the guideline, the font names, or the existing project name in one question and stop. 2. **Look up existing assets.** Call `get_web_projects_by_name` with that name and `assetTypes` set to `["WebProject", "DigitalAd"]`, leaving `accessTypes` unset so owner and shared assets are both covered. Do not search FontSets in this flow: a FontSet has no CSS and cannot serve web output. 3. **Resolve the match.** - **One exact match** (ignoring case and punctuation) -> use it without asking. - **Several plausible matches** -> list only names, asset type, and created date (newest first), and ask the user to choose one. Never pick among them silently, and never merge fonts from several projects. - **No match** -> say no Web Project or Digital Ad with that name was found, show any close names the connector returned, and ask
Preview of the first 4,000 characters. Read full instructions →
Release notes
Initial Release: Access approved brand fonts from your Monotype Fonts Inventory, so campaign assets, prototypes, and web pages use licensed brand type instead of default fonts, check production status of fonts, create and update web projects and font lists, sync fonts to your desktop, and retrieve published CSS/CDN URL. Requires a Monotype Fonts enterprise account; desktop sync also needs the Monotype Fonts desktop app.
Declared in the saved package. Remote tools may change independently.
Package details
Publisher declarations from the archived package. These are separate from our research and the live service's terms.
- Package author
- Monotype
- Keywords
- See keywords
- Getting started skill
- ./skills/monotype-fonts/SKILL.md
- Commerce declaration
- Does not support commerceThis does not establish whether access is free or paid.
- Review scenarios
- 5 positive · 3 negativeScenario counts, not test results.
Declared capabilities
- Read
- Write
Package observed Nov 5, 2026.
Technical details
- First seen
- Nov 5, 2026 · 18:00 UTC
- Last seen
- Nov 6, 2026 · 12:00 UTC
- Collection status
- Collected
plugin_asdk_app_6aeb436040d88191b8b731e024012a8c
Download plugin data (JSON)Plugin details: served from cache. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.