Font Design MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| project_createC | Create a project in the launch workspace with Unicode UFO sources and technical glyphs. |
| project_openA | Reopen a server-created project by ID; verifies committed sources and returns its revision. |
| project_inspectB | Inspect a master with optional sections and glyph_ids focus. Full collections are paginated; pagination lists each continuation. Use sections=['design'] for the complete design contract without spacing/compositions. |
| project_updateB | Atomically update metadata, brief or decision journal. Requires expected_revision. UPM changes on nonempty fonts fail. |
| variable_configureC | Configure continuous axes and masters in this project. Master 'default' is the existing source at the default location. New IDs clone it; existing IDs keep their drawings; omitted IDs are removed in a new revision. Edit masters with master_id. Compatibility is checked at build/validation time. |
| glyph_getA | Read a master's glyph metrics in font units, Y upwards. master_id defaults to 'default'. Use detail=full for contour/point/component/anchor IDs and geometry. |
| glyph_editC | Apply typed vector operations or drawing primitives atomically to one glyph in master_id (default: 'default'). Use detail=full for added/removed/touched IDs. Replacements are explicit. |
| spacing_editA | Atomically set advances, side bearings, kerning groups or pairs in master_id (default: 'default'). Bearings move outlines; advances do not. |
| font_editB | Edit up to 128 glyphs atomically in master_id (default: 'default'), then apply spacing. Forward component references resolve at final validation; any failure rolls back the batch. |
| render_glyphC | Persist and return PNG image content from the selected UFO revision, with optional guides/handles. Comparison uses the same frame. |
| render_textB | Compile the revision, shape with HarfBuzz and return FreeType PNGs. For variable fonts, location maps axis tags to values; omitted axes use defaults. Missing Unicode is reported. Optional same-conditions revision comparison. |
| font_validateB | Run technical checks, compile a TTF, inspect tables and corpus coverage. Reports errors, warnings and observations; does not assess artistic merit. |
| font_buildB | Build real TTF and/or WOFF2 from a frozen revision, automatically variable when axes/masters are configured. Returns persistent relative paths and hashes. Does not alter sources. |
| font_analyzeC | Check visible ink, matching outlines and self crossings by default; measure declared design rules, normal stroke/counter profiles, smooth joins, digit spacing and required coverage. Rules accept master_id or a variable location; variation_profiles measure normal-width progression. interpolation=true adds timed source correspondence and compiled axis-grid checks. Returns regional coverage and localized candidates, not artistic approval. Full reports include measurements and evidence_plan. |
| proof_reviewA | Record an agent's visual review of immutable render report_uris from an exact revision. Use verdict=revise for defects; accepted intentional findings require their finding_id and a reason. Does not alter font sources or assert human approval. Inspect actual images before calling. |
| font_release_checkB | Evaluate all masters, structural measurements, glyph review coverage, localized findings, reference comparisons and shaped text reviews before release. Supply proof_review report_uris. Returns actionable missing requirements; never certifies aesthetic perfection. |
| reference_importA | Import a bounded single-frame PNG from workspace/inbox as an immutable drawing reference. image_to_font maps image pixels (top-left, Y down) to font units (baseline, Y up). Requires expected_revision. No tracing or automatic rescaling; use reference_id with render_glyph. |
| render_proofA | Render up to 32 glyphs at one common scale, optionally comparing revisions. Missing glyphs are explicit placeholders; use render_text separately for shaped words. |
| history_listB | List committed revisions and summaries with pagination; interrupted uncommitted stages are excluded. |
| history_restoreA | Restore a committed revision by creating a NEW revision; requires the current expected_revision and preserves history. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 20 tools
Most tools target distinct font-design resources and phases, such as project setup, glyph editing, rendering, validation, and history. Some boundaries blur between glyph_edit and font_edit, and among render_text, render_glyph, and render_proof, but descriptions and parameters clarify their scopes. Validation-related tools are also distinct enough across validate, analyze, and release_check phases.
The set mostly follows a consistent snake_case resource_action pattern, e.g. project_create, glyph_edit, font_validate, and history_restore. Minor deviations appear in render_text, render_glyph, and render_proof, which use verb-first ordering, and in the longer font_release_check. The convention is still predictable overall.
At 20 tools, the set is slightly above the ideal 3-15 range, but the domain is genuinely complex and spans project setup, variable configuration, editing, rendering, validation, proofing, release checks, import, build, and history. The tools do not appear redundantly padded, so the count is reasonable though heavy.
The surface covers the core font-design lifecycle: project create/open/update/inspect, variable configuration, glyph and font editing, spacing, rendering, validation/analysis, proof review, release checking, reference import, build, and history restore. Minor gaps exist, such as no explicit project listing/deletion or dedicated glyph deletion/export operation, but agents have workarounds and the critical paths are present.