FacetCue MCP Server
Related Servers
Alternatives to FacetCue MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceBuild Blender scenes through 4 tools and 338 tokens of fixed context: on-demand operation schemas, batches of up to 100 edits, preview captures and permission-gated Python for full bpy access.458 PyPI15MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to fully control Blender through 50+ tools for 3D modeling, animation, materials, and scene management via HTTP endpoints.-
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to drive a live Blender session over stdio, inspecting the scene graph, searching and calling operators, reading and writing RNA properties, rendering viewable images, and checkpointing or restoring the file across a multi-turn conversation. It also exposes gallery and scene-reset helpers so the agent can check its own work and start over cleanly.17GPL 3.0
- AlicenseAqualityAmaintenanceEnables an AI agent to drive a live Blender session, building, sculpting, measuring, checking, rigging, lighting, rendering and exporting 3D models through safe operations in world units. Every geometry-changing call reports achieved dimensions, open edges and failures as numbers and review images, so modelling mistakes become visible instead of silent.113MIT
- AlicenseAqualityDmaintenanceEnables remote control of Blender via the Model Context Protocol, allowing users to execute Python scripts, query scene data, and generate 3D models from images. It provides a bridge for AI clients to interact directly with Blender's internal environment and automate 3D content creation.36MIT
- FlicenseAqualityCmaintenanceEnables AI agents to inspect and drive Blender scenes directly, either through a live editor bridge on port 8190 or automatically via headless background CLI when Blender is closed. Provides token-efficient tools for scene outlining, object creation and modification, modifiers, materials, rendering, asset export, and arbitrary bpy script execution.11-
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one reads annotations, the other submits changes. There is no overlap in functionality, and their descriptions make the read vs. write separation obvious.
Both tools follow a consistent verb_noun pattern in snake_case (get_surface_annotations, submit_annotation_changes). The naming is predictable and easy to parse.
With only 2 tools, the count is slightly below the typical 3–15 range, but it fits the narrow read-and-update workflow. No additional tools are needed for the stated purpose, so the count is reasonable.
The server covers reading all annotations and marking affected ones as MODIFIED after edits, which closes the core loop. It intentionally omits creating or deleting annotations (done in Blender) and only supports the MODIFIED status, a minor gap for broader annotation management.