WorldPainter MCP
Related Servers
Alternatives to WorldPainter MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables users to author buildable QuadSpinner Gaea 2 .terrain projects, turn real DEM or synthetic elevation into Gaea-ready heightmaps and 16-bit erosion masks, have Gaea itself validate and build the project, and read back the exported heightmap and colour-map outputs. It bakes in the file-format, licence, schema-version and mask-bit-depth constraints that otherwise make Gaea-produced projects fail to open, build, or apply correctly.MIT
- AlicenseNot gradedqualityBmaintenanceEnables local authoring and testing of Minecraft Java adventure maps through validated MCP tools, including structure building, snapshot/restore, and automated QA.MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to read, audit, and byte-faithfully edit Warcraft III .w3x and .w3m maps while preserving untouched file bytes, with tools for metadata, objects, terrain, sounds, cameras, triggers, and more.Apache 2.0
- AlicenseBqualityBmaintenanceEnables reading and editing CapCut desktop draft projects, including adding/moving/trimming/splitting clips, text, audio, images, filters, transitions, masks, keyframe animation, audio fades, stickers, setting transforms, validation, and saving with backups.28MIT
- AlicenseBqualityBmaintenanceMCP server that reads and writes RPG Maker XP project .rxdata files, enabling AI assistants to create and edit actors, items, skills, maps, events, and scripts, and render map previews, by describing what you want.6580 npm3MIT
- FlicenseAqualityCmaintenanceEnables 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.582-
TDQS
Scored across 8 tools
Each tool has a clearly distinct role in the terrain-editing workflow: inspection, export, analysis, planning, previewing, applying, and snapshot management. The plan/preview/apply trio is explicitly sequenced with non-overlapping outputs, so an agent can easily tell them apart.
All tool names follow a consistent wp_ + verb_noun snake_case pattern (wp_get_world_info, wp_export_heightmap, wp_apply_terrain_plan, etc.). The compound nouns like terrain_edit and terrain_plan remain predictable and readable.
Eight tools is well-scoped for a world-editing MCP with a plan-preview-apply safety pipeline and snapshot support. Each tool earns its place without redundancy or bloat.
The surface covers the core lifecycle: read world info, export/analyze terrain, plan/preview/apply edits, and list/rollback snapshots. Minor gaps exist, such as no tool to delete or prune snapshots, but agents can work around these limitations.