Open-source Glyphs 3 and 4 plug-in and MCP server
Connect Glyphs 3 or 4 to Codex, Claude, and other AI agents.
Glyphs 3 and 4 compatible
Compatible with Glyphs 3 and the latest Glyphs 4 beta. The macOS installer detects both versions and lets you install either one or both. Read the installer documentation.
Keep the font open in Glyphs and work with an AI assistant that understands the editor, its documentation, and the structure of type design. Spend less time translating your intent into scripts or hunting through menus, and more time designing, checking, and shipping.
Explore a font, compare masters, investigate spacing, or find the right Glyphs API without breaking your train of thought.
Use Codex or Claude to draft, test, and refine Glyphs scripts and production workflows while you work.
Give the agent structured access to glyphs, layers, paths, components, anchors, kerning, and selections.
Start read-only, preview suggestions, use dry runs and confirmations, then verify the result in Glyphs.
Glyphs MCP is an open-source Model Context Protocol server and plug-in for Glyphs 3 and Glyphs 4. It creates a local bridge between the font open in Glyphs and MCP-compatible AI clients such as Codex and Claude.
Instead of relying on loose prompts or screen automation, an agent can call structured, font-aware tools, receive precise data, and report what it inspected or changed. That makes AI font editing and type design automation easier to understand, review, and repeat.
Glyphs MCP includes searchable Glyphs SDK and ObjectWrapper documentation through docs_search and docs_get. Your agent can look up the relevant API while it works instead of guessing from general programming knowledge.
Use it to answer Glyphs scripting questions, find properties and methods, write or debug Python, and iterate on tools inside the editor. It turns Codex, Claude, or another capable MCP client into a practical partner for vibe coding in Glyphs as well as everyday font production.
Inspection and review workflows can stay read-only. Editing tools use dry runs or explicit confirmation where supported, so you can inspect the proposed work before committing broader changes.
Choose the signed macOS installer for the shortest path, ask your coding agent to handle a custom setup, or use the terminal installer when you want a developer-friendly, reproducible installation.
The installer detects Glyphs 3 and Glyphs 4 independently, lets you install or update either version or both, installs the required Python dependencies, and can connect Glyphs MCP to Codex and Claude. It can also install the bundled agent skills.
Edit → Glyphs MCP Server.Clone the Glyphs 4 branch and run the installer from the repository. The terminal installer defaults to Glyphs 4; pass --glyphs-version 3 when targeting Glyphs 3. This route is useful for development, automation, and reproducible local setups.
Install from the Glyphs 4 branch
git clone --branch glyphs4 https://github.com/thierryc/Glyphs-mcp.git
cd Glyphs-mcp
python3 install.pyPaste the prompt below into Codex or Claude and let the agent inspect the repository and install Glyphs MCP for you. This option is experimental, but many users have used it successfully—especially when Glyphs has a custom name, is installed outside /Applications, or when several Glyphs versions are installed.
Prompt for Codex or Claude
Install Glyphs MCP on this Mac from the `glyphs4` branch of https://github.com/thierryc/Glyphs-mcp.
Before changing anything, read the repository README, `install.py`, and the relevant installation documentation. Inspect the Glyphs applications installed on this Mac, including custom app names, beta builds, multiple versions, and copies outside `/Applications`. Determine whether the intended target is Glyphs 4 or Glyphs 3, and check the supported Python requirements and current Glyphs plug-in locations.
Briefly tell me what you found and the installation approach you will use, then proceed unless the target version or location is ambiguous. If it is ambiguous, stop and ask me before installing. Use the repository's supported installer instead of inventing installation steps. Do not modify system Python, overwrite unrelated files, remove an existing installation, or change MCP client configuration without confirmation.
Install the plug-in and its required dependencies for the detected Glyphs version. Verify the installed files and report exactly what changed. Then tell me how to restart Glyphs, open `Edit → Glyphs MCP Server`, start the local server, and verify that it responds at `http://127.0.0.1:9680/mcp/`. Also explain how to undo the installation. If any step cannot be verified safely, stop and explain what remains instead of guessing.The installer can configure the supported Codex and Claude clients. For manual setup—or any other MCP-compatible client—connect to the local server endpoint below.
Local MCP URL
http://127.0.0.1:9680/mcp/Add Glyphs MCP manually
codex mcp add glyphs-mcp-server --url http://127.0.0.1:9680/mcp/
claude mcp add --scope user --transport http glyphs-mcp http://127.0.0.1:9680/mcp/The macOS installer supports Glyphs 3 and the latest Glyphs 4 beta. It detects both applications independently and lets you install or update either version or both.
Terminal installer: target Glyphs 3 explicitly
python3 install.py --glyphs-version 3Glyphs MCP is open-source software released under the Apache 2.0 license. Bug reports, documentation feedback, workflow ideas, feature requests, and code contributions are welcome.
Glyphs MCP is an experimental project in the early stages of development. Features, installation steps, and agent behavior may change. Back up important font files, review proposed commands and edits, and verify results before relying on it in production workflows.