Already have a coding agent? Connect Blit to it.

Bootstrap block

Copy this into your coding agent. It is written for the agent to read and act on.

Connect me to Blit, a game-asset production tool (sprites, icons, VFX, motion,
backdrops) that runs as an MCP server, so you can create and iterate on assets
from this session.

Set it up:

1. Add Blit to this project's .mcp.json:
   {
     "mcpServers": {
       "blit": {
         "type": "http",
         "url": "https://api.blit.so/mcp/",
         "headers": { "Authorization": "Bearer ${BLIT_API_KEY}" }
       }
     }
   }

2. Ask me for a Blit API key (I mint it at https://blit.so, Settings then API
   keys; issuance is web-only, you cannot create one) and set it as the
   BLIT_API_KEY environment variable. When the Blit CLI is available you can
   instead run "blit login" to sign in from the browser with no key to paste,
   and "blit setup" to wire this config for you.

3. Reload MCP servers and call get_account to confirm the key works and read my
   credit balance. Do not run any generation call until this passes.

4. Create a first asset: call create_cutout with kind "character", chroma_key_id
   "green", and a brief describing one pose. Fetch the preview with get_asset and
   show it to me before iterating.

If the Blit skill is installed, read it first: it is the full contract for size,
format, identity, and style. Review every result visually before you report it
done.

Install by surface

Blit speaks MCP, so any tool-native agent connects over one HTTP endpoint. Mint an API key on the web (Settings, then API keys) and reference it from the environment as BLIT_API_KEY; the key value never goes into a config file.

{
  "mcpServers": {
    "blit": {
      "type": "http",
      "url": "https://api.blit.so/mcp/",
      "headers": { "Authorization": "Bearer ${BLIT_API_KEY}" }
    }
  }
}

[mcp_servers.blit]
url = "https://api.blit.so/mcp/"
bearer_token_env_var = "BLIT_API_KEY"

How your agent knows Blit

Your agent learns Blit in three layers, from the always-present to the workspace-specific.

1. 1. Schema prose

   Every Blit tool advertises its own name, purpose, and parameters in its schema. This is the layer your agent always sees the moment the tools are connected.

2. 2. The skill

   The blit skill is the full production contract: which tool to pick, how to anchor identity, when to animate, and how to verify a result before reporting it. Install it so your agent art-directs instead of guessing.

3. 3. BLIT.md

   BLIT.md is the per-workspace memory your agent reads before it creates, so results match what this workspace already settled on.

About BLIT.md

BLIT.md is one set of art rules that applies across the whole workspace: style canon, subject and world facts, your standing size and style preferences, and named recipes. You do not restate your style every time; it accumulates as you work. Because it records recipes per asset kind, you can mix looks in one workspace, pixel-art sprites alongside painterly backdrops.