Picorn: a registered MCP server for editable image and video projects

[cueqzapper]

Picorn is now active in the Official MCP Registry as io.github.cueqzapper/picorn (v2.2.0).

The problem it targets is the flat-output dead end in visual agent workflows. An agent can make an image, but if one crop, headline, or layer is wrong, the usual fallback is another full generation.

Picorn's MCP creates native image documents and video timelines instead:

• real text, image, SVG, and shape layers
• layer grouping, ordering, alignment, and updates
• real video clips, audio, keyframes, and effects
• PNG, JPEG, MP4, and WebM renders
• an editor link to the same project for human changes
• a deliberate human approval step before publishing or scheduling

It is a remote Streamable HTTP server at:

https://picorn.com/mcp

No API key or Picorn account is required for the fair-use MCP path. The endpoint currently exposes 30 tools.

Codex:

codex mcp add picorn --url https://picorn.com/mcp

Claude Code:

claude mcp add --transport http picorn https://picorn.com/mcp

Cursor:

{
  "mcpServers": {
    "picorn": {
      "url": "https://picorn.com/mcp"
    }
  }
}

A useful first test is:

Create a three-slide product launch campaign. Keep the background, product image, headline, and CTA as separate editable layers. Render the slides and give me the editor link.

Current boundaries: it will not reproduce every reference image pixel-perfectly, and I still expect one human art-direction pass. Publishing is kept behind explicit approval rather than being triggered silently by the agent.

Registry entry: https://registry.modelcontextprotocol.io/v0.1/servers/io.github.cueqzapper%2Fpicorn/versions/latest

Tool list, setup, and example workflow: https://picorn.com/mcp?utm_source=github_mcp_registry&utm_medium=showcase&utm_campaign=mcp_showcase_2026_08&utm_content=registered_server_showcase

Disclosure: I build Picorn. I would especially value feedback on the boundary between agent-side editing and the browser-editor handoff: which layer or timeline operations are still missing in real client workflows?