New in the recently released cutting-edge version Glyphs 3.5 (3526) is an API for opening files in the Glyphs app and adding a tab with a specific list of glyph layers.
This is done by opening the URL glyphsapp://show/ with a set of query parameters. Have a look at the handbook for details:
You can use these URLs from other apps or from the web. For example, a font proofing report might include links to these URLs so that a designer can jump directly to the corresponding glyph layer in the correct file.
There is no such compression system in place yet. If you would find that useful in specific situations, let me know. I would want broader feedback before making such additions.
This is such a great addition. Thank you for the update and for implementing it!
I’ve just integrated the new glyphsapp://show/ URL scheme into my MCP server workflow, and it immediately makes the experience feel much more seamless and “alive”. Instead of returning long lists of glyph names, stylistic sets, or alternates, the MCP can now generate direct links that jump straight into Glyphs with the relevant file, glyphs, and layers already selected.
The result is a much smoother UX:
Ask the MCP for a list of stylistic alternates.
Get a nicely formatted report.
Click a link.
Instantly open the exact glyph set in Glyphs.
No more searching, filtering, or manually assembling tabs.
I especially like how this bridges AI-assisted workflows and the actual design environment. It feels less like reading a report and more like having a conversation that can directly guide you to the right place in your font source.
Here’s a screenshot of a prototype where the MCP lists stylistic sets and automatically generates “Open in Glyphs” links for each one.
For anyone building tools around Glyphs, proofing systems, QA reports, AI assistants, or custom scripts, this opens up many interesting possibilities. The ability to deep-link directly to glyph layers and tabs is a surprisingly powerful building block.
Thanks again to Florian, Georg, and the Glyphs team for continuing to make Glyphs such a scriptable and extensible platform. Looking forward to seeing what the community builds with this feature.
This is one of those small features that quietly removes friction and makes the whole experience feel more magical. Thanks for shipping it!
Very nice indeed. Is it possible to use it without a specific file and add the tab to whatever file is currently open and frontmost in Glyphs?
I just added a “Copy Strings” to a proofing html the same day you posted this, and a “open in Glyphs” would be amazing. However, the html does not know about the glyphs file per design.
So, that would then use the frontmost document window I assume. Would you need to insert glyphs by Unicode code point or do you have the glyph names in your case?
And by codepoint would be great. Its for example a generated string of Hangeul or Thai glyphs, that we currently copy as text and paste into Glyphs. So “normal” text copying would work.
Only if it makes sense for this API, though. I don’t want to pollute it with specific needs if it won’t make sense for others.
