PostScript MCP
Related Servers
Alternatives to PostScript MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceEnables AI models to convert LaTeX snippets into Typst, validate Typst syntax, browse the official Typst documentation, and render Typst code to PNG images. This lets models verify typeset output and check code correctness before delivering it to users.-
- FlicenseNot gradedqualityAmaintenanceEnables AI models to work with Typst by providing documentation lookup, LaTeX-to-Typst conversion, syntax validation, and rendering Typst code as PNG images.-
- FlicenseNot gradedqualityAmaintenanceEnables AI models to work with Typst by retrieving documentation, converting LaTeX snippets to Typst, validating Typst syntax, and rendering Typst code as PNG images.-
- FlicenseNot gradedqualityAmaintenanceEnables AI models to interact with Typst by converting LaTeX snippets to Typst, validating Typst syntax, reading Typst documentation, and rendering Typst code as PNG images.-
- FlicenseNot gradedqualityAmaintenanceEnables AI models to interact with the Typst typesetting system by converting LaTeX snippets, validating Typst syntax, and rendering Typst code to images.-
- FlicenseNot gradedqualityAmaintenanceEnables AI models to convert LaTeX snippets to Typst, validate Typst syntax, retrieve documentation chapters, and render Typst code as PNG images.-
TDQS
Scored across 8 tools
Each tool targets a distinct job: exact operator definitions vs operator search, validation vs rendering, PSlib retrieval vs searching, and reference/capability lookups. Even the paired search/get tools are clearly separated by role.
Most tools follow a consistent verb_noun pattern (lookup_operator, validate_postscript, search_operators). The only deviation is postscript_capabilities, which lacks a verb; otherwise the naming is uniform and predictable.
Eight tools is an appropriate size for a PostScript assistant: each one covers a necessary stage of authoring, checking, rendering, and reference lookup without redundancy. The count feels intentional rather than padded.
The surface covers a full workflow: discover operators, validate code, render output, reuse library procedures, and consult authoritative references. There are no dead ends or obvious missing operations for the stated domain.