Skip to main content
Glama
ArkSentinel

SuperMCP

by ArkSentinel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to SuperMCP

No user-submitted related servers found.

    Related Servers

    • BlenderMCP

      clanker25
      A
      license
      A
      quality
      C
      maintenance
      Enables connecting Blender 3D to AI assistants via MCP, allowing prompt-driven 3D modeling, scene editing, and real-time manipulation. Supports object/material control, scene inspection, viewport screenshots, and integrations with Poly Haven, Sketchfab, and AI model generators.
      22
      MIT

    • blender-mcp

      ceeyang
      A
      license
      C
      quality
      B
      maintenance
      Enables controlling local Blender 5.2 through natural language, providing 159 tools for modeling, materials, shaders, lighting, animation, cameras, rendering, import/export, UV, geometry, rigging, assets, and more via an MCP server.
      159
      1
      MIT

    • blender-studio-pro-mcp

      cristoferarango
      A
      license
      C
      quality
      B
      maintenance
      This MCP server enables complete control of Blender from any MCP client, offering 221 dedicated tools and a universal bridge for 1,500–2,500+ bpy.ops operators across 33 modules for modeling, VFX, rendering, simulation, animation, compositing, VSE, and Grease Pencil.
      223
      2
      Apache 2.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

    D1.9/5.0

    Scored across 107 tools

    Disambiguation3/5

    Most tools are grouped by clear prefixes (anim_, rig_, uv_, shader_), so a knowledgeable agent can often infer intent, but several blur together: export_godot_glb duplicates godot_export_glb, diag_check_rig_health/diag_validate_armature/diag_get_rig_report overlap, and anim_clear vs anim_delete_keyframe is misleading. With many tools having no description, selection becomes harder than it should be.

    Naming Consistency3/5

    The dominant pattern is snake_case category prefixes with verb_noun names, but it is not applied uniformly: get_scene_info vs scene_get_stats, export_godot_glb vs godot_export_glb, add_modifier/validate_mesh without category prefixes, and reset_scene_clean all break the pattern. It remains readable but is inconsistent enough to be a real friction point.

    Tool Count1/5

    107 tools is an extreme mismatch for a coherent MCP surface, far exceeding the calibration threshold of 50+ tools. Even for a complex Blender/Godot pipeline, this forces agents to navigate a massive namespace and suggests micro-tool sprawl rather than careful scoping.

    Completeness3/5

    The toolset covers an unusually wide range: import/export, animation, rigging, materials, UVs, lighting, rendering, Godot validation, and batch operations. However, there are notable lifecycle gaps like no object create/transform/delete, no selection API, no material listing/deletion, and no deletion for several entity types, forcing agents to fall back to execute_blender_code.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources