Integration

MineSkin integration

MineSkin turns a PNG skin image into a Minecraft skin texture signed by Mojang (a value and a signature), the data a server or plugin needs to show custom skins on player heads, NPCs and player profiles. Generate a skin from an image URL, an uploaded PNG file or an existing player's UUID and get the signed texture back, queue up to 24 skins at once and follow their jobs, read any skin by its UUID, browse recent public skins and list the capes that can be applied. The deprecated delay route and the synchronous generate route the vendor no longer recommends are not exposed: the generate tools queue the job and wait for it themselves. Authentication is an API key from account.mineskin.org sent as a Bearer token; requests without a key are tightly rate limited.

Connect MineSkin How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in MineSkin.Built from the 12 MineSkin tools below, on the connection you add once.

What you can do with MineSkin

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Queue, 3 operations

generate_skinGenerate skinPOSTTurns a PNG image URL (or data URL), or a player's UUID, into a Minecraft skin signed by Mojang: the skin's uuid, texture value and signature, and texture URL. Waits for the job and returns the finished result; gives up after 3 minutes.
get_job_statusGet job statusGETReturns a generation job's status (waiting, active, completed or failed) and, once completed, the generated skin with its signed texture. Check a job at most once per second.
list_queue_jobsList queue jobsGETLists the recent generation jobs submitted with your API key, each with its id, status, result (the skin UUID once completed) and timestamps. Use it to follow many jobs without hitting the per-job rate limit.

Skin, 3 operations

generate_skin_from_fileGenerate skin from filePOSTTurns an uploaded PNG skin file (64x64 or 64x32 pixels, 1 to 20 KB) into a Minecraft skin signed by Mojang: the skin's uuid, texture value and signature, and texture URL. Waits for the job and returns the finished result; gives up after 3 minutes.
get_skinGet skinGETReturns a MineSkin skin by its UUID: name, visibility, variant (classic or slim), the signed texture (value and signature), texture hash and URL, generator details and view count.
list_skinsList skinsGETLists recently generated skins on MineSkin, most recent first, 16 per page, each with uuid, short id, name, texture hash and creation time. Pass pagination.next.after back as after for the next page.

Cape, 2 operations

list_capesList capesGETLists the capes MineSkin knows (uuid, name, texture hash and URL) and whether each can be applied: public (anyone with the capes grant), owner (only a user whose linked Minecraft account owns it) or none.
list_my_capesList my capesGETLists the known capes with, for your account, whether one of your linked Minecraft accounts owns each cape (owned) and whether a generate request with it would be accepted (usable).

Apikey, 1 operation

get_api_key_infoGet api key infoGETReturns information about the API key used for the call (not the key itself): id, name, owner, creation date, the origins, IPs and user agents it is restricted to, and whether it uses paid credits.

Batch, 1 operation

queue_skin_batchQueue skin batchPOSTQueues between 1 and 24 skins in one call (url or player UUID each) and returns one result per item, in request order, each with success, its job (id, status) or errors. Needs a Pro plan or higher (batch_generation grant).

Client, 1 operation

get_client_infoGet client infoGETReturns how MineSkin sees the caller: user agent, API key id, user id, client IP address and whether the client is billable (on a paid plan).

Me, 1 operation

get_current_userGet current userGETReturns the MineSkin user behind the API key: user id and the grants of their plan (per-minute and per-hour limits, concurrency, private skins, capes, plan name).

Use MineSkin from Claude Code, Cursor or Codex

Connect MineSkin in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its MineSkin operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect MineSkin

Create your workspace
Sign up free. Nothing to install.
Connect MineSkin once
Add your MineSkin connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.