ai-fighter
Related Servers
Alternatives to ai-fighter
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables local-first creation, editing, and animation of pixel-art Aseprite documents through MCP stdio, with atomic previews, canvas drawing, layers, frames, palettes, tags, slices, tilemaps, and cast tools. It also supports strict asset validation and verified Phaser/game-asset export from reopened native masters.47 PyPIMIT
- AlicenseAqualityBmaintenanceEnables agents to author, validate, inspect, patch, and render editable JSON pixel-art and animation recipes through local tools, producing PNG contact sheets, APNGs, sprite atlases, and related export bundles.281,356 npm125MIT
- FlicenseAqualityBmaintenanceEnables converting layered PSD or PhotoshopToSpine exports into validated Spine 2D rigs, animations, atlases, previews, runtime JSON, and optionally editable .spine projects. It provides MCP tools and an OpenAI/Codex workflow for rigging, animation generation, validation, preview auditing, and batch processing.14-
- AlicenseNot gradedqualityBmaintenanceProvides MCP tools for local code validation with execution evidence, enabling users to run planned checks on projects and receive JSON results that distinguish passing, failing, and incomplete outcomes.340 npmMIT
- AlicenseAqualityCmaintenanceEnables agents to build standard 64×64 Minecraft skins, validate technical texture properties, and generate inspection previews locally through MCP tools.4MIT
- AlicenseBqualityBmaintenanceLets MCP clients browse vanilla data, add or override table rows, edit asset properties, check Blueprint symbols, and validate mods before packaging.21MIT
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one reads the authoring contract/spec, the other validates a manifest. There is no overlap in intent or workflow, and the descriptions reinforce the boundary (validate explicitly does not read files or register).
Both names follow a clean verb_noun snake_case pattern (get_fighter_spec, validate_fighter_manifest). The convention is fully predictable and self-describing.
With only 2 tools, the surface is thin even for a narrow authoring/validation helper. The spec tool does multiplex several documents, but the set still feels minimal for the domain.
Reading and validating are covered, but there is no way to register, submit, or persist a fighter, and get_fighter_spec is the only read path. The tools acknowledge registration is out of scope, leaving a notable lifecycle gap.