MCP Integration Guide for Game Art Workflows

SpriteArk includes an MCP helper that lets compatible AI coding tools call its game-art tools. This guide covers the supported connection, a safe first test, and the file-access rules that matter in real projects.

Before you start

You need:

SpriteArk installed in /Applications
an active Pro subscription, introductory trial, or Lifetime purchase
an MCP-compatible client such as Cursor or Claude Desktop
for AI generation or semantic image analysis: a downloaded, enabled compatible on-device model on Apple silicon, or an enabled remote Provider configured with your own API key
for inpainting: a compatible enabled remote Provider; on-device models do not support inpainting

Many editing tasks run locally. For example, you can inspect an image, crop it, slice a spritesheet, resize it, or remove a background with Apple Vision without configuring a remote Provider.

How the connection works

Your AI client launches the helper bundled inside SpriteArk. The helper communicates with the client over stdio, starts SpriteArk when necessary, and connects to the App’s MCP service over 127.0.0.1. The service is not exposed to your local network.

MCP client → bundled spriteark-mcp helper → SpriteArk on your Mac

The current integration does not require a separate server package or the retired art-tools project.

Add SpriteArk to your MCP client

Add this server entry to your client’s MCP configuration:

{
  "mcpServers": {
    "spriteark": {
      "command": "/Applications/SpriteArk.app/Contents/MacOS/spriteark-mcp"
    }
  }
}

Restart or reload the client after saving the configuration. If the client reports that the command is missing, confirm that SpriteArk is installed in /Applications and that the helper exists inside the App bundle.

Verify the setup with local tools

Start with operations that do not depend on a remote Provider:

Ask the client to call get_asset_info for one image.
Resize a copy with resize_image, or use upscale_image with mode=local.
Try remove_background with mode=vision for on-device Apple Vision processing.
Confirm that the output location and image are what you expected before trying a batch.

Once those calls work, test AI tools with a compatible route configured in SpriteArk:

generate_image and prompted analyze_image can use downloaded on-device models on Apple silicon without a remote API key, or remote Providers with your own key.
inpaint_image requires a compatible remote Provider. Remote usage fees are separate from Pro.

Use list_models with capability=imageGeneration, imageAnalysis, or imageEditing to discover available models. To select one explicitly, pass its returned Provider ID as provider_id together with its model ID as model. Otherwise, omit both and SpriteArk uses the first available compatible route in your configured priority order; it does not automatically prefer local execution.

What you can automate

Workflow	Example tools
Inspect and organize	`get_asset_info`, `analyze_image`
Crop and transform	`crop_image`, `trim_image`, `rotate_image`, `flip_image`
Resize and upscale	`resize_image`, `upscale_image`
Prepare sprites	`slice_spritesheet`, `add_outline`, `add_padding`, `extrude_edges`
Adjust color	`adjust_image`, `replace_color`, `extract_palette`, `swap_palette`
Generate and edit with AI	`generate_image`, `inpaint_image`, `remove_background`

See the full SpriteArk feature overview for the corresponding workflows in the Mac App.

File access and output behavior

SpriteArk tools accept either file data or an absolute file path. Use one input mode per file, not both.

Data input works across clients and returns image output through MCP when no output path is provided.
Path input is convenient for project files, but the helper must have permission to read the input and write the destination.
A path-based operation without an explicit output location normally writes beside the source file.
Multi-file output directories must not already exist; SpriteArk does not overwrite or merge an existing directory.
Sandboxed clients may need you to approve file access. If path access is unavailable, use file data instead.

Start with a single copy of an asset and an explicit destination. Expand to a folder only after the result is correct.

Example workflow

Give your AI assistant a specific input, transformation, and destination:

Inspect hero.png, remove its background with Apple Vision, upscale the result 2× with nearest-neighbor scaling, and save a new file in the processed folder. Do not overwrite the source.

This makes the intended route and output boundary clear. For a batch, ask the client to test one representative asset first.

Troubleshooting

The MCP server does not appear

Confirm the command path, then reload the MCP client. If SpriteArk does not open automatically, launch the App once and retry.

A local tool cannot read or write a file

Use an absolute path and verify the destination is writable. If the client is sandboxed, approve access when prompted or switch to data input and inline MCP output.

A Provider-backed tool fails

Open SpriteArk’s AI Provider settings and verify the API key, selected model, capability, and network connection. SpriteArk does not automatically retry a started request with another Provider, which avoids duplicate charges and inconsistent results.

The default port is already in use

SpriteArk uses local port 9426 by default. Advanced setups can assign the same SPRITEARK_MCP_PORT value to both the App and helper.

Ready to use the workflow? Compare Free, Pro, and Lifetime plans or download SpriteArk for Mac.

Automate Your Art Pipeline with SpriteArk's MCP Tools