Skip to main content
Glama
stuart-e-anderson

PostScript MCP

by stuart-e-anderson
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to PostScript MCP

No user-submitted related servers found.

    Related Servers

    • Font Tools MCP

      kiyong2020
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to diagnose, modify, and validate OTF/TTF fonts interactively through a set of read-only, write, and validation tools.
      -

    • Type Evidence

      gavinjudd
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to discover, inspect, compare, and resolve local fonts and typography through bounded search, paging, family inspection, exact assets, contextual compositions, and preview images, while keeping fonts and model inference local.
      MIT

    • Free Photoshop MCP

      joshcreativos-ctrl
      A
      license
      C
      quality
      B
      maintenance
      Connects an AI agent to Adobe Photoshop through COM/ExtendScript so it can build and correct designs —layers, typography, vector shapes, layer effects, blend modes, masks, adjustments and filters— while previewing its own output, inspecting a document's resources, and learning a reusable style from the user's finished PSDs.
      47
      MIT

    • OpenSCAD MCP Server

      Abhishekv87bit
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI assistants to render 3D models by providing tools to execute OpenSCAD code and generate single or multi-perspective views. It returns high-quality PNG renderings directly to LLM applications for visual feedback and 3D model visualization.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.3/5.0

    Scored across 8 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources