Skip to main content
Glama
ktheunlikedoll

graphite-editor-mcp

by ktheunlikedoll
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to graphite-editor-mcp

No user-submitted related servers found.

    Related Servers

    • atx-mcp

      gridhra
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to perform deterministic, non-generative image transformations—straightening, cropping, masking, layering, color adjustments, and encoding—as reproducible recipes while preserving immutable originals.
      12
      MIT

    • Material Maker MCP

      graysonchalmers
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to create Material Maker node graphs from natural language, validate them against the node catalog, and render them headlessly to PBR texture maps and editable .ptex files.
      5
      MIT

    • openmontage-mcp

      Eaterofsouls
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to run headless creative production workflows by turning declarative CreativeSpec documents into validated media deliverables through MCP tools, durable workers, and provider adapters.
      AGPL 3.0
    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.4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: single rendering, batch variant rendering, node introspection, and structural validation. render and render_variants are related but the descriptions make the batch/parametric purpose unambiguous.

    Naming Consistency5/5

    All tools follow the same snake_case graphite_ prefix and a clear verb_noun pattern: render, list_nodes, validate_doc, render_variants. The naming is uniform and predictable.

    Tool Count5/5

    Four tools fit the narrow rendering/validation scope well and each tool earns its place. The count is within the ideal 3-15 range and does not feel padded or insufficient.

    Completeness4/5

    The surface covers the main workflows: render, render variants, validate, and inspect known nodes. Minor gaps exist, such as no template-listing tool or document editing capability, but the stated domain appears rendering-focused.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources