Skip to main content
Glama
jeonghwanko

ai-fighter

by jeonghwanko
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to ai-fighter

No user-submitted related servers found.

    Related Servers

    • Aseprite Agent MCP

      SarutobiSasuke8
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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.
      72 PyPI
      MIT

    • pixelbolt

      skulitom
      A
      license
      A
      quality
      A
      maintenance
      Enables 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.
      8
      437 npm
      14
      MIT

    • GPT Spine MCP

      kumikilongyeyo
      F
      license
      A
      quality
      A
      maintenance
      Enables 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
      -

    • repo-verifier

      stsepelin
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides 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.
      173 npm
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.9/5.0

    Scored across 2 tools

    Disambiguation5/5

    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).

    Naming Consistency5/5

    Both names follow a clean verb_noun snake_case pattern (get_fighter_spec, validate_fighter_manifest). The convention is fully predictable and self-describing.

    Tool Count3/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources