Skip to content
MCPBytes

Describe a character.See them move.

Turn a character idea into a sprite sheet, individual frames and walking previews. Review the result, then bring it into your game.

From 20 credits300 free credits to start

Available
  • API
  • MCP
MCP tool: create_pixel_sprite
A green-clad ranger in sixteen pixel-art poses
B2Create a pixel sprite“A forest ranger with a green hood and a brown satchel.”

A small character. A whole set of moves.

Describe one character, or add a reference image, and get a sheet of sixteen 32 × 32 frames. Four walking previews let you check each direction. Download the frames, shared palette and animation metadata together, then review the character before using it.

Choose a direction, then play the four-frame loop. Reduced-motion settings keep it paused.

Direction

Paused. Play the four-frame loop when ready.

Each direction reuses three generated poses: the fourth frame returns to the middle pose for a smooth loop.

Input
A description; optional PNG or JPEG reference
Sprite sheet
128 × 128 pixels, arranged in a 4 × 4 grid
Frames
Sixteen fixed 32 × 32 PNG frames
Walking
Down, left, right and up; three generated poses per direction
Export
PNG sheets, JSON metadata, GIF previews, Godot scenes and Unity import setup

One idea. Up to four takes.

Each variant is another complete character sheet to choose from. All variants include a 128 × 128 sheet, sixteen frame PNGs and four walking previews. Choose more variants for more alternatives.

Check every direction.

Preview walking down, left, right and up. Each loop reuses three generated poses in a four-frame sequence.

Ready for your engine.

Each ZIP includes a Godot scene and animation resource, plus a Unity importer that creates frames, looping clips and a prefab. Follow the included setup guide, then bring your character into your game.

Download the example.

Inspect the files before running your own job. No sign-in required.

  • Ranger sprite sheet

    Original API output: sixteen 32 × 32 cells.

    PNG · 128 × 128 · 8 KB

  • Ranger frames and imports

    Original API export with frames, four walk previews, metadata and engine setup.

    ZIP · 282 KB

  • Ranger animation metadata

    Original API output with frame rectangles, pivots and loop timing.

    JSON · 11 KB

  • Walk down preview

    Original API preview: three generated poses reused in a four-frame loop.

    GIF · 5 KB

  • Walk left preview

    Original API preview: three generated poses reused in a four-frame loop.

    GIF · 4 KB

  • Walk right preview

    Original API preview: three generated poses reused in a four-frame loop.

    GIF · 4 KB

  • Walk up preview

    Original API preview: three generated poses reused in a four-frame loop.

    GIF · 4 KB

Pay by the job.

From 20 credits. A variant is one complete candidate sheet. Choose 1, 2, 3 or 4 variants to get that many different takes on the same request. Every candidate has the same 128 × 128 size, sixteen frames and four walking previews; the price increases with the number of candidates. A failed job is refunded.

Pricing details

Start free

Available now

300free credits when you sign up

  • Every MCPBytes tool, one credit balance
  • Sign in with GitHub or email, no card required
  • Each tool states its price before you run it
  • Failed API jobs cost nothing

Price per job

Create a pixel sprite

1 variant
20 credits
2 variants
40 credits
3 variants
60 credits
4 variants
80 credits

Limits

Largest input
20 MB
Description
Up to 4,000 characters
Candidates
1–4 sheets per request
Reference
PNG or JPEG

Limits by account

Jobs at once
Free3 jobs
Pay as you go5 jobs
Monthly bundle8 jobs
Results kept
Free1 day
Pay as you go7 days
Monthly bundle30 days
Largest upload
Free50 MB
Pay as you go100 MB
Monthly bundle100 MB

Free until your first purchase; any credit pack moves you to Pay as you go; a monthly bundle while it lasts. GPU tools like this one run up to 5 of your jobs at a time; the rest wait their turn. Compare accounts

Your agent or your code.

Connect your agent and it can use this tool right away, or call it from your own code. One key works for both.

Start a job

Send the options as JSON. Include an upload ID or an owned job file when adding a reference. Options such as description go in the options object.

Requestcreate-sprite.sh
curl https://api.mcpbytes.com/v1/tools/create_pixel_sprite/jobs \
  -H "Authorization: Bearer $MCPBYTES_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "options": {"description": "A forest ranger with a green hood and a brown satchel", "seed": 42},
    "idempotency_key": "pixel-sprite-example-004"
  }'
Response202 Accepted · trimmed
{
  "tool": "create_pixel_sprite",
  "status": "queued",
  "input_kind": "parameters",
  "result": null
}

Get the result

Poll until the status is final. Download files only after success.

Requestread-sprite.sh
# JOB_ID is the id from the create response
curl "https://api.mcpbytes.com/v1/jobs/$JOB_ID" \
  -H "Authorization: Bearer $MCPBYTES_API_KEY"
Response200 OK · trimmed
{
  "tool": "create_pixel_sprite",
  "status": "succeeded",
  "result": {
    "variants": 1,
    "qa_status": "needs_review",
    "files": [
      {
        "name": "raw_1.png"
      },
      {
        "name": "sprite_1.png"
      },
      {
        "name": "sprite_1.json"
      },
      {
        "name": "sprite_1.zip"
      },
      {
        "name": "generation.json"
      }
    ]
  }
}

MCP

Connect once. Your agent calls create_pixel_sprite and gets the download URLs back. This endpoint has only this tool's family, which keeps your agent's tool list short; one endpoint has every tool.

Claude Code

The first form signs in through the browser when you run /mcp. In .mcp.json (project root), ${MCPBYTES_API_KEY} is read from the environment when Claude Code connects. Claude Code docs

claude mcp add --transport http mcpbytes \
  https://api.mcpbytes.com/mcp/image
Codex (CLI, IDE extension, ChatGPT desktop)

Codex reads the key from the environment variable each time it connects. The same table can go in ~/.codex/config.toml by hand; codex mcp add has no --header flag. Codex docs

codex mcp add mcpbytes --url https://api.mcpbytes.com/mcp/image \
  --bearer-token-env-var MCPBYTES_API_KEY
Cursor

~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project). Remote servers take no "type". Without the header, the client signs you in with GitHub or an email link (OAuth). Cursor docs

~/.cursor/mcp.json
{
  "mcpServers": {
    "mcpbytes": {
      "url": "https://api.mcpbytes.com/mcp/image",
      "headers": {
        "Authorization": "Bearer ${env:MCPBYTES_API_KEY}"
      }
    }
  }
}
11 more clients in the docs →
MCP tools
create_pixel_sprite
Generate 1–4 character sprite sheets from a description and an optional uploaded reference. Each 128×128 PNG contains sixteen 32×32 cells: three walk poses per direction and four extra still poses. ZIP exports contain fixed-size frames, looping previews, QA and animation metadata, a Godot scene and a Unity editor importer. Outputs require visual review; previews reuse three poses, not four distinct frames. No arbitrary actions or eight-direction animation. Follow the asynchronous job with get_job. variants: 1: 20 credits. variants: 2: 40 credits. variants: 3: 60 credits. variants: 4: 80 credits. Requires idempotency_key; retain it when retrying the same request.
create_upload
Returns a one-hour URL to PUT a local file to; then call the tool with the upload_id.
get_job
Status and results of a job; waits up to wait_seconds for it to finish.
cancel_job
Cancel a queued job or a workflow whose can_cancel is true; repeated calls never delete results.
list_jobs
Your most recent jobs, newest first.
read_job_file
Reads a text output (.txt .json .md .csv) of a succeeded job in chunks.
Full reference: inputs, options, outputs, limits and errors

Prefer to run it yourself? Source on GitHub (AGPL-3.0)

Your first jobs are on us.

Start with 300 free credits. Sign in with GitHub or email and try a tool in your browser. No card required.