Use in your AI tool (MCP)

SplashForge ships an MCP server, so you can turn icon/splash artwork into store-ready assets without leaving your editor or chat. It runs in any MCP-compatible tool and renders locally — nothing is uploaded.

Model-agnostic by design

SplashForge does not generate the artwork (so it never costs you AI tokens). Your AI tool’s own image model — or any image you have — produces the picture; SplashForge turns it into every platform size + native bundles.

Works in

Claude (Desktop & Code), Cursor, GitHub Copilot (VS Code & CLI), Gemini CLI, Windsurf, JetBrains, VS Code — anything that speaks MCP. (OpenAI Codex’s MCP support is limited/changing — check its current docs.)

Tools

Tool	What it does
icon_from_image	Any finished icon image (path / URL / data URL) → full icon set + optional native bundles
generate_app_icon	Compose an icon from a logo + background + text
generate_splash	Splash screens at every device size
generate_bundle	Native bundles (.xcassets, Android adaptive, .ico, .icns, SVG) — Pro

Add it

The command is the same everywhere; only the config location differs.

{
  "mcpServers": {
    "splashforge": {
      "command": "node",
      "args": ["/ABSOLUTE/PATH/TO/splashforge/packages/mcp/bin/splashforge-mcp.js"],
      "env": { "SPLASHFORGE_LICENSE": "" }
    }
  }
}

• Claude Desktop — Settings → Developer → Edit Config
• Cursor — ~/.cursor/mcp.json
• VS Code / Copilot — .vscode/mcp.json
• Gemini CLI — ~/.gemini/settings.json
• Windsurf — Settings → Cascade → MCP servers

Paths — use absolute paths

This is the one thing that trips people up. The MCP server runs as a background process started by your AI tool, so its working directory is whatever the tool sets — usually your home folder or the tool’s own directory, not the project you’re looking at. That means:

• A relative outDir like ./assets does not write into your project — it lands wherever the server happens to be running.
• The same applies to a relative image or logoPath.

Always pass absolute paths. The simplest way is to tell the assistant the full path:

Export the icon set into /Users/me/projects/my-app/assets.

How to get the absolute path

• macOS/Linux: run pwd in your project and append the subfolder → /Users/me/projects/my-app/assets.
• Or drag the folder/file into the chat — most tools paste its absolute path.
• Windows: use the full path, e.g. C:\Users\me\my-app\assets.

Every tool reports the absolute path it wrote to in its result (e.g. Generated 9 icon files in /Users/me/projects/my-app/assets) — check that line to find your files.

For an image a model just made in the chat: save it to disk first and pass its absolute path, or pass it as a data: URL. A bare filename won’t resolve.

The cross-tool flow

Generate an icon image with Gemini for my running app, then use SplashForge to export every app-icon size into /Users/me/projects/my-app/assets (absolute path).

Your tool produces (or you point at) an image, calls icon_from_image with an absolute outDir, and you get the full set — circle + rounded-square verified, foldered by platform, native bundles with a Pro key.

Why this is different

Most generators are a website you leave your editor for. SplashForge runs where you already are, with whatever model you already use, and renders on your machine — so it’s fast, private, and costs you nothing in AI tokens.