API & MCP

Everything a person can do on Tilemap Converter (TMX, Tiled JSON, PNG, collisions), a program or AI agent can do with the same inputs and get the identical result.

HTTP API

Tilemap Converter (TMX, Tiled JSON, PNG, collisions)

Convert tile maps between Tiled TMX (CSV, base64, zlib or gzip layers), Tiled JSON, engine-neutral JSON and Flipline Tilemap Desk projects. Render a flattened PNG with flip flags and export solid tiles as merged collision rectangles for physics engines.

Inputs of Tilemap Converter (TMX, Tiled JSON, PNG, collisions)
FieldTypeDefaultDescription
maptextarea—Map text (TMX, Tiled JSON, engine-neutral JSON or Flipline tilemap project)
filefile—Or: map file
imagesfile—Tileset and image-layer PNGs (one PNG or a ZIP of PNGs, matched by file name)
targetselect (tmx, tiled-json, neutral-json, flipline, collision-json, png, zip)"tiled-json"Convert to
encodingselect (csv, base64, base64-zlib, base64-gzip)"csv"Tile layer encoding (TMX and Tiled JSON)
renderbooleantrueAlso render a PNG preview
scaleinteger2PNG scale

Every result contains

inputs (normalised, defaults applied), summary, result (validated against the published schema), units, assumptions, sources, warnings, computedAt and links.

MCP (Model Context Protocol)

{
  "mcpServers": {
    "flipline-tilemap-converter": { "type": "http", "url": "https://fliplinetilemapconverter.usefulweb.site/mcp" }
  }
}