Skip to main content
Glama
gprethesh

ArmorPaint MCP

by gprethesh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to ArmorPaint MCP

No user-submitted related servers found.

    Related Servers

    • armorpaint-mcp

      baktubak
      F
      license
      A
      quality
      C
      maintenance
      Enables MCP clients to drive ArmorPaint 1.0 through a file-based bridge plugin, letting agents open projects, inspect and edit materials and node graphs, paint, and export textures on an unmodified ArmorPaint installation.
      58
      2
      -

    • Open Brush MCP Server

      moz411
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables control of Open Brush 3D painting software through natural language commands, allowing LLMs to create drawings, manipulate brushes, import 3D models, manage colors, layers, and camera settings via the Open Brush HTTP API.
      1
      MIT

    • krita6-mcp

      fanzhuyifan
      A
      license
      A
      quality
      C
      maintenance
      Enables an AI assistant to inspect and edit a live Krita 6 desktop session, create and modify documents and layers, paint with native brushes, and receive inline PNG previews.
      56
      1
      MIT

    • Blender-Mind-MCP

      xiaohai-uid
      A
      license
      A
      quality
      C
      maintenance
      Enables AI-driven 3D modeling in Blender by providing tools to create primitives, apply modifiers and materials, set up lighting and cameras, capture viewport snapshots, export assets, inspect scenes, and execute Python commands via natural language.
      10
      MIT

    • Tool-ArmorPaintMCP

      graysonchalmers
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables an AI assistant to batch-drive ArmorPaint headlessly via its native CLI and scripting engine, re-exporting projects at different presets and building procedural materials without opening the GUI.
      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

    B3.3/5.0

    Scored across 41 tools

    Disambiguation4/5

    Most tools target a distinct resource-action pair, and the detailed descriptions help separate overlapping operations like set_layer vs layer_action and fill_layer vs paint_stroke. A few close neighbors exist—export_layer vs export_textures and set_node_value vs set_material_pbr—but they are still distinguishable from their names and descriptions.

    Naming Consistency4/5

    The armorpaint_ prefix plus verb_noun pattern is consistent overall, e.g. create_material, delete_material, connect_nodes, export_mesh. Minor deviations exist such as new_project instead of create_project, bake as a bare verb, and layer_action as a generic suffix, but the naming is still predictable and readable.

    Tool Count2/5

    With 41 tools, this exceeds the 25-tool threshold that typically indicates an overgrown surface. The tools are organized by subsystem and each has a real purpose, but the count is heavy enough that an agent must manage a large selection set.

    Completeness4/5

    The tool set covers the full ArmorPaint workflow: project handling, mesh/material/node graph editing, layer management, painting, baking, viewport inspection, and multiple export paths. Minor gaps exist—such as no object deletion or duplicate, and no explicit material rename—but they are workaroundable and do not block core workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources