Using fontpr and MCP

Use FontLab’s tool interfaces to inspect a font or repeat a defined operation from a script or external assistant. Configure AI separately when the workflow requires a model connection.

fontpr and the MCP Layer

Inside FontLab’s Python environment, fontpr, also available as mcp_tools, exposes the tool-oriented operations used by the assistant. The run_python and get_python_output tools are excluded from this Python module to avoid recursive execution.

Inspection tools read the current project; modifying tools change its data. run_actions invokes supported Actions, including autokerning workflows. These are the operations taught in Actions and Managing and Automating Kerning Pairs, accessed programmatically through the scripting environment in Python Scripting, The Python API and Libraries, and Running Startup and Init Scripts. Read the installed tool descriptions for their arguments and scope.

An external assistant connects through the supplied MCP bridge to the running FontLab application. External access is a separate opt-in from built-in Chat. Such clients can modify fonts outside Chat's confirmation interface, so use a deliberately configured client and inspect its changes. Bridge launch configuration, ports, tokens, and connection troubleshooting belong to Volume Two; they are not prerequisites for ordinary built-in Chat use.

The AI and scripting interfaces reach the same underlying tool operations. A successful natural-language request can therefore help identify a repeatable workflow, while a reviewed script or action set makes its exact scope and parameters easier to reuse. Keep human review of the design and the output in either route.

Inspect before Modifying Data

For repeatable agent workflows, inspect the available tool descriptions and validate a proposed glyph replacement before applying it. Native node-editing and PostScript-hint tools support bounded edits with dry-run inspection and Undo; the hint editor does not rewrite TrueType instructions.

Supported preference tools discover and change application settings while excluding credentials. Aidus file tools operate on UTF-8 text in the Aidus and Scripts/Aidus folders; overwriting requires an explicit choice, and saving a script does not run it. set_notepad_content can replace a plain or styled specimen with one Notepad Undo step. Verify the font result before saving or exporting it.

Open Fonts without Interactive Prompts

For an unattended script or MCP session, the Developer preference for suppressing startup and font-opening dialogs uses the configured import settings and sends problems to Output. It skips optional repairs and encoding conversion rather than inventing answers to interactive questions. The preference is off by default. Inspect the imported result before allowing subsequent modifying operations.

Inspect Layout and Components through Tools

The current MCP tools can edit components, feature code, and visual lookup rules, compile features, and inspect stored OpenType tables. Use validation before an edit and inspect the resulting font afterward; modifying operations support Undo. Read the returned errors and unfinished-work report before assuming a multi-step request completed.