Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Beschreibung vom Entwickler (englisches Original)
Create and verify pixel-art assets with atomic Aseprite edits and Phaser export.
Diese drei werden nie zu einer Punktzahl zusammengefasst: Meinungen, Messungen und Beliebtheit sind verschiedene Dinge.
Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.
Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.
ASEPRITE_PATH, ASEPRITE_MCP_WORKSPACE, ASEPRITE_MCP_TOOLS, ASEPRITE_MCP_LOCK_WAITDu brauchst
Welche App nutzt du?
Wähle oben deine App. Wir merken sie uns, damit der Button beim nächsten Mal „In … installieren“ anzeigt.
Öffne Claude Desktop → Settings → Developer → Edit Config und füge dies in claude_desktop_config.json ein
{
"mcpServers": {
"aseprite-agent": {
"command": "uvx",
"args": [
"aseprite-agent-mcp"
],
"env": {
"ASEPRITE_PATH": "your-value",
"ASEPRITE_MCP_WORKSPACE": "your-value",
"ASEPRITE_MCP_TOOLS": "your-value",
"ASEPRITE_MCP_LOCK_WAIT": "your-value"
}
}
}
}Führe das in deinem Terminal aus
claude mcp add aseprite-agent --env ASEPRITE_PATH=your-value --env ASEPRITE_MCP_WORKSPACE=your-value --env ASEPRITE_MCP_TOOLS=your-value --env ASEPRITE_MCP_LOCK_WAIT=your-value -- uvx aseprite-agent-mcpTrag die leeren Werte ein, bevor du ihn startest.
In .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen
{
"mcpServers": {
"aseprite-agent": {
"command": "uvx",
"args": [
"aseprite-agent-mcp"
],
"env": {
"ASEPRITE_PATH": "your-value",
"ASEPRITE_MCP_WORKSPACE": "your-value",
"ASEPRITE_MCP_TOOLS": "your-value",
"ASEPRITE_MCP_LOCK_WAIT": "your-value"
}
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
In .vscode/mcp.json in deinem Projekt einfügen
{
"servers": {
"aseprite-agent": {
"type": "stdio",
"command": "uvx",
"args": [
"aseprite-agent-mcp"
],
"env": {
"ASEPRITE_PATH": "your-value",
"ASEPRITE_MCP_WORKSPACE": "your-value",
"ASEPRITE_MCP_TOOLS": "your-value",
"ASEPRITE_MCP_LOCK_WAIT": "your-value"
}
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
Dieser Server läuft auf deinem Computer, und ChatGPT kann sich nur mit Servern im Internet verbinden. Wähle eine andere App.
Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.
ASEPRITE_MCP_WORKSPACE envASEPRITE_MCP_TOOLS envASEPRITE_MCP_LOCK_WAIT envDiese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.
Läuft auf deinem Computer; die Tool-Liste erscheint nach der Installation in deiner KI-App.
Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 8. Nov. 2026
Der Registry-Name wurde mit dem GitHub-Konto SarutobiSasuke8 bestätigt, dem das Repo gehört
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieser Server läuft auf deinem Computer; es gibt keinen Endpunkt im Internet
Läuft auf deinem Computer und nutzt stattdessen lokale Einstellungen
Läuft auf deinem Computer; Tool-Listen können wir nur von Endpunkten im Internet lesen
Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.
Er hat 1 von 1 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.
Das musst du eintragen: ASEPRITE_PATH
Er läuft auf deinem Computer. Deine KI-App startet ihn bei Bedarf, und die Daten laufen nicht über die Server des Entwicklers (außer der Server ruft selbst einen Onlinedienst auf).
Das GitHub-Repo wurde zuletzt – geändert, und die neueste Version (0.3.0) kam vor 22 Tagen in die Registry.
Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Außerdem brauchst du Python (uv) auf deinem Computer.
In derselben Kategorie: Spec Driven Development, Remote Desktop Commander, Egovframe Scaffold MCP
Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.
So liest du eine Karte:↓ Downloads pro Wochei★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
eGovFrame (전자정부 표준프레임워크) projects: templates, components, CRUD, build, 5.x migration, dependencies
Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.
Local-first pixel-art authoring and verified game-asset export over MCP stdio.
Status: 0.2.0 alpha. Built on aseprite-mcp by Brendan Malloy (MIT), pinned to 8caabf9ce240a040ca2c94d3d7366c9d8dd63653. The added production layer provides atomic edits with previews, strict asset contracts, verified Phaser export, tool profiles, cast tools, workspace locking and crash-safe saves. See NOTICE, LICENSE and UPSTREAM_INVENTORY.json. The inherited Python namespace remains aseprite_mcp; the package and command are aseprite-agent-mcp.
114 tools cover native documents, pixel drawing, layers, cels, frames, palettes, tags, slices, transforms, tilemaps, inspection and exports. The production path adds atomic edits with image feedback, strict typed asset contracts, labelled all-frame previews, character-cast tools and Phaser bundles verified against reopened native masters. By default the server exposes a 42-tool core profile (see Tool profiles). See the generated tool reference for exact schemas.
Install Python 3.10+, uv or pipx, and your own licensed Aseprite with Lua scripting support. You may also build Aseprite yourself under its EULA. This package only invokes your installed executable via ASEPRITE_PATH; it does not bundle Aseprite, its installer, Lua runtime or art assets.
For the published package:
uvx aseprite-agent-mcp
Set ASEPRITE_PATH before running. Example MCP client commands (replace the paths):
# Windows (PowerShell)
claude mcp add aseprite --env ASEPRITE_PATH=C:\\path\\to\\Aseprite.exe -- uvx aseprite-agent-mcp
claude mcp add aseprite --env ASEPRITE_PATH=/Applications/Aseprite.app/Contents/MacOS/aseprite -- uvx aseprite-agent-mcp
claude mcp add aseprite --env ASEPRITE_PATH=/path/to/aseprite -- uvx aseprite-agent-mcp
For clients that take JSON (including Codex MCP configuration), use this shape:
{
"mcpServers": { "aseprite": { "command": "uvx", "args": ["aseprite-agent-mcp"], "env": { "ASEPRITE_PATH": "/path/to/aseprite", "ASEPRITE_MCP_WORKSPACE": "/path/to/assets" } } } }
Grok clients that support local stdio MCP servers can use the same executable, arguments and environment fields. Client-specific configuration keys may vary.
For a source checkout and development:
uv sync --locked --group dev
$env:ASEPRITE_PATH = 'C:\path\to\aseprite.exe' $env:ASEPRITE_MCP_WORKSPACE = 'C:\path\to\assets' uv run --no-sync aseprite-agent-mcp
The command speaks MCP on stdin/stdout and waits for a client. Diagnostic logs go to stderr. Use mcp-config.example.json in a client after replacing its placeholder paths. This project does not modify client settings.
The small GIF is procedural example art, generated by uv run python scripts/generate_demo.py. It demonstrates the intended pixel-art output; it is not a screenshot of a live Aseprite session. A full Aseprite MCP round-trip proof is described under Verification.
Every tool description and schema costs the agent context, so the server exposes a profile chosen by ASEPRITE_MCP_TOOLS, a comma-separated list of names:
| Value | Exposes |
|---|---|
core (default) | 42 tools: generate/import, create, draw, animate, preview, validate, export and the cast tools |
all | Every supported tool (114) |
| a group | One tool module, e.g. tilemap, effects, slices, palette, workflow |
| a tool name | One extra tool, e.g. core,add_outline |
Unknown names stop the server at startup. The groups are listed at the top of the tool reference.
| Variable | Default | Meaning |
|---|---|---|
ASEPRITE_PATH | auto-detect | Aseprite executable |
ASEPRITE_MCP_WORKSPACE | workspace/ in the project | Root for relative paths |
ASEPRITE_MCP_TOOLS | core | Tool profile, as above |
ASEPRITE_MCP_LOCK_WAIT | 15 | Seconds a call waits for a busy workspace (0 fails at once) |
ASEPRITE_MCP_TIMEOUT | 90 | Seconds per Aseprite process |
ASEPRITE_MCP_ALLOW_ABSOLUTE | off | Allow absolute path syntax inside allowed roots |
ASEPRITE_AGENT_ALLOWED_ROOTS | [] | JSON list of extra roots |
Let an image model draw the character and key poses, then use import_generated_image to turn one PNG into a pixel grid and assemble_animation to clean and align an ordered pose list. Both tools are in the default core profile.
import_generated_image(filename="base.png", output_directory="base-clean",
width=32, height=32, colours=16) assemble_animation(filenames=["idle-1.png", "idle-2.png", "idle-3.png", "idle-4.png"], output_directory="idle-clean", width=32, height=48, tag="idle", colours=16, alignment="bounding-box", durations_ms=[180, 140, 180, 140], outline="#152b32")
method="nearest" samples a grid; "majority" chooses the most frequent RGBA value in each source cell, with deterministic ties. Majority only downsamples.width and height accept grids up to 256px per edge. For detailed sprites, use height=128, colours=32 to 48, method="majority" and palette_first=True. Palette-first mode snaps one shared source palette before voting, so near-identical generated shades count together. It is opt-in; existing calls keep their previous behaviour.palette=["#RRGGBB", ...] snaps to explicit colours. Otherwise colours builds one shared automatic palette across the animation. Alpha is binary after alpha_threshold (default 128). Transparency is excluded from the colour count; an optional 1px outline can add one colour and is clipped at the cell boundary.background="#RRGGBB" removes only border-connected matching pixels, with an optional background_tolerance. It preserves enclosed details and is a colour key, not semantic segmentation. Existing transparency needs no background key.alignment="anchor" accepts one source [x,y] per same-size input and places it at (width//2,height-2), rejecting clipping. "none" keeps each canvas. Keep pose scale and padding consistent and inspect the returned preview.Each new output directory contains master.aseprite, cleaned frame PNGs, sheet.png, sheet.json and qa.json. The native master is reopened through Aseprite's Lua API; every rendered frame, the tag range, durations and sheet pixels are checked before an atomic, no-overwrite directory publication. Source PNGs are preserved. Inputs are bounded to 4 million pixels each, 16 million total, 128 frames and 1 million output pixels.
The generated courier demo includes the original model output, a cleaned base, a 4-frame idle, editable masters and a reproducible local script. Pixel verification proves file integrity. It does not approve art quality or make a coherent animation out of inconsistent key poses.
The walk demo uses an 8-pose generation pass, 128px-high cells, a shared 48-colour palette and explicit feet anchors. It includes a looping GIF and a 64px/128px comparison from the same source and palette.
health_check proves the local CLI and Lua path can create and export.create_sprite creates an editable .aseprite master.ase_apply_and_preview applies a typed batch in one transaction and returns a rendered PNG. A failed operation leaves the file unchanged. A later preview failure explicitly reports that the edit was saved.ase_preview_animation shows every frame without smoothing.ase_validate_asset_contract checks geometry, frame count, exact tag ranges, tag playback, palette membership, binary alpha, empty frames and optional per-row foot/centre drift. Unknown fields are errors.ase_export_phaser creates a bundle directory with sheet PNG, hash atlas JSON, animation timing, loader JS, contract and QA. It reopens the master and exported PNG and compares every frame's RGBA pixels before publishing. An existing directory is rejected unless replace=true, which swaps a previous bundle by rename. The native master remains.draw_pixel_rows paints a whole frame from text rows and a colour key, e.g. rows=["..oo..", ".oxxo."], key={"o": "#203040", "x": "#f0c060"}. Unknown characters are errors; . and space are skipped.copy_cel and offset_cel batch ops (bobs and steps without redrawing) and tag each animation.derive_mirrored_tag creates walk_left from walk_right.save_sprite_as a template, then recolor_sprite it into each character, or start characters from a shared base with copy_frames_from.ase_preview_animation shows one labelled row per tag over a checkerboard.ase_export_cast_atlas validates every master against its own contract and writes one Phaser atlas: frames / _ , animations : .Edits save through a sibling temporary file and a rename, so a killed Aseprite process cannot leave a half-written master. Frame numbers must exist: an out-of-range frame is an error, never clamped to the nearest frame. All frames are 1-based. A contract row names an exact contiguous animation tag. Palette entries are inline hex colours, not arbitrary file paths. Hide reference layers before final validation/export: locked layers are still visible pixels.
{
"name": "robot", "cell": {"width": 16, "height": 16}, "rows": [ {"tag": "walk_down", "frames": 4}, {"tag": "idle", "frames": 2, "playback": "pingpong"}, {"tag": "sleep", "frames": 2, "repeat": 0, "check_anchor": false} ], "alpha": "binary", "palette": ["#315c88", "#8bd5ed", "#223344"], "anchor": {"max_foot_drift": 0.0, "max_center_drift": 0.0} }
uv run pytest
uv run pytest --run-aseprite uv run python scripts/proof_stdio.py --output ./workspace/proof-final
Use a fresh output directory for each proof run. The proof talks to the server through a real MCP stdio client, creates 16 distinct synthetic frames, compares a saved/reopened master, exports a sheet and GIF, tests rollback and overwrite/path rejection, and confirms that a deliberately damaged asset cannot pass export QA. It writes proof.json and visual artifacts. See verification.
To play that output in Phaser 3.90.0:
npm ci --prefix examples/phaser --ignore-scripts
uv run python -m http.server 8795 --bind 127.0.0.1
Open http://127.0.0.1:8795/examples/phaser/. The page reports success only after all four frames in all four animations have played. It uses a local npm dev dependency; the MCP itself has no network dependency after installation. For a fresh run under workspace/my-proof, use `http://127.0.0.1:8795/examples/phaser/?pr
Nur der Anfang wird gezeigt; den Rest findest du im Repo