Particle effects for your coding agent

How it works

1. Connect your agent. Add the server https://mcp.particlefx.studio/mcp with an API key from your billing page, or sign in with your account in apps that support it. Claude Code, Codex and Devin take one command; the others a few lines of config. Setup for each is below.
2. Ask for the effect in plain words. Name the effect, the engine and the folder: "a looping fireball for Godot in res://fx".
3. It builds, checks and exports. The agent starts from the closest of the 610+ library effects or a blank canvas, edits it, looks at real renders of its own work, then exports a spritesheet with the data file your engine reads and puts it in your project.

A real example

This is the whole exchange in Claude Code for a Godot 4 project. The tool names are the real ones; every client on this page calls the same tools.

> Start from the Pixel Fireball library effect, name it fireball, make the trail a bit
  longer, check the render, then export Godot 4 SpriteFrames, transparent, 30 fps,
  into res://fx/ and fix the texture path.

  particlefx  list_presets      query "fireball"         -> pixel-arcade/fireball
  particlefx  create_effect     from_preset, name        -> new effect in your account
  particlefx  edit_effect       longer trail             -> applied, health check passes
  particlefx  render_preview    6 moments of the loop    -> contact sheet, checked
  particlefx  analyze_effect                             -> loop closes exactly
  particlefx  export_effect     sheet, godot, 30 fps     -> download link (1 hour)
  shell       curl + unzip into fx/, fix res:// path

  fx/fireball.png    atlas, full alpha
  fx/fireball.tres   SpriteFrames, animation "fireball", looping, 30 fps

const FIREBALL := preload("res://fx/fireball.tres")

var fx := AnimatedSprite2D.new()
fx.sprite_frames = FIREBALL
add_child(fx)
fx.play("fireball")

The effect is a real particle simulation, not a generated picture: the export is rendered by the same engine and renderer as the studio, loops close frame for frame, and the effect stays in your account, so you or your agent can change it later or open it in the studio and adjust it by hand.

Any other client that speaks MCP over Streamable HTTP and can send an Authorization header works the same way. The MCP quickstart has the raw details.

What it costs

Connecting is free, and so are library search, reading the reference, analysing an effect and every edit after the first. A new effect costs 1 build, each export 1 build, and previews are free for the first 20 of each UTC day, then 1 build per 4. A typical effect, made and exported once, is 2 builds. Over MCP a free account and Starter pay with pack builds ($4.99 for 150, never expire); Creator at +50%, Studio at +25%, Studio Max one for one can spend plan builds. Engine data files, hi-res, video and the live runtime need a plan, from $7.99 a month. Everything else: keys, limits and billing.