Adobe Fonts

Adobe Fonts

Discovers, searches, and previews real, licensable fonts from the Adobe Fonts catalog via five Adobe for Creativity MCP tools: font_recommend (contextual suggestions), font_search (direct lookup by name or facets), font_details (metadata for known fonts), font_styles (every style variant in a family), and font_preview (a visual specimen of any font).

Surface note: This skill has no file uploads, so the flow is largely the same on Claude and Codex. Surfaces differ in two places: asking a clarifying question — use the AskUserQuestion widget where available (e.g. Claude), or plain text where it isn't (e.g. Codex) — and showing a font specimen — font_preview renders an inline card on MCP App hosts (e.g. Claude), or returns image_markdown to embed directly on hosts without that widget (e.g. Codex). Follow the default flow below; the fallback notes only apply when the relevant widget is unavailable.

Hard constraint: every font this skill surfaces — recommended, searched, or looked up — must be a real, licensable Adobe Fonts family that came back in a tool's own results. Never substitute a font from prior knowledge just because it seems "similar" or matches a name the user mentioned — fonts outside a tool's own results are not licensable here.

Tool Reference

Workflow

Step 0 — Initialize Adobe Tools

Call adobe_mandatory_init first. It returns the file-handling rules and tool routing guidance required for the rest of the workflow.

{ "skill_name": "adobe-fonts", "skill_version": "1.0.0" }

Step 1 — Choose the right tool

These aren't mutually exclusive — a request often chains two: font_search or font_recommend to find a font, then font_details / font_styles for more about it, or font_preview to see it. Don't use font_recommend for a direct/named lookup, or font_search for an open-ended design brief — each tool's own description defers to the other for that case.

Step 2 — Identify fonts correctly

font_preview, font_details, and font_styles take a font_identifier ({postscript_name, font_id}, font_id optional) or a list of them. Rules that apply everywhere a postscript_name or font_identifier is passed, including font_recommend's / font_search's selected_font:

• Always use a value already returned by a prior call — from font_identifier.postscript_name (or a bare postscript_name) in a font_recommend or font_search result, or from a font_styles styles[] entry — never guess or derive one from a display name.
• postscript_name matching is case-sensitive with no fuzzy matching — "myriadpro-regular" will not resolve "MyriadPro-Regular".
• If the user names a font casually (e.g. "something like Futura") and you don't yet have its PostScript name, resolve it first with font_search (user_query + font_query: true) before using it as selected_font or in any font_identifier.
• font_id is optional wherever postscript_name is given; supply it too when you already have it, but never fabricate one.

Step 3 — Call the tool

Step 2's identification rules and Step 4's response/error handling apply to every tool below; each subsection covers only what's specific to that tool.

font_recommend

Most briefs map straight to parameters — infer sensible values from what the user gave you and proceed. Only when the request is too sparse to map at all (e.g. a bare "recommend a font" with no document type, mood, or reference font) ask one quick clarifying question with AskUserQuestion — offer a few document-type / mood options — then continue.

No-widget fallback (only if AskUserQuestion is unavailable, e.g. Codex) — ask the same labeled options as a short plain-text message and wait for the typed reply.

Context parameters: doc_type, styles, moods, topics, user_query (max 150 chars), font_query (bool — set true when user_query is literally a font-name search), text_hierarchy ("heading" | "body"), selected_font.

Metadata parameters: library ("full" | "trial", default "full"), writing_systems (comma-separated ISO 15924 codes, default "latn"), font_technology ("vf" variable, "colr" color), font_group, locale (default "en"), per_page (1–100, default 10), debug.

writing_systems is passed straight through with no validation — an invalid or mismatched script code silently returns no results rather than erroring. Map the user's target language(s) to the correct code (e.g. Korean → hang, Chinese → hans/hant, Cyrillic → cyrl, Arabic → arab) rather than guessing.

If the request involves multiple intended uses (e.g. a poster needing both display and body text) or multiple documents, call once per text_hierarchy / doc rather than one call for everything.

font_search

Same context and metadata parameters as font_recommend, plus: foundry (comma-separated foundries to filter by), designers (comma-separated names), sort ("relevance" | "name" | "newest", default "relevance"), and page (in addition to per_page, for pagination beyond the first page).

font_details

font_identifiers: a list of font_identifier (each needs postscript_name; font_id optional). locale: optional language code for translated names (recognized codes and silent-fallback-to-English behavior same as font_recommend's locale).

Batch every font you need into one call rather than calling once per font.

font_styles

Same signature as font_details: font_identifiers (list), locale. Batch the same way. Returns every style (weight, width, italic) in each requested font's family.

font_preview

font_identifier: only postscript_name is required. One font per call — no batch mode.