Full disclosure: I build Picorn.
I kept hitting the same problem when an agent created social graphics: the first render looked close, but the result was a flat image. Cursor couldn’t move one product cut-out, fix one headline or change the stacking order. It had to generate the entire design again.
Picorn’s MCP is built around the opposite idea. Cursor creates a native document made of addressable text, image, SVG and shape layers. It can render a preview, inspect it, change one object, and return the same project in a browser editor for final art direction.
Add it to Cursor
Add this to your Cursor MCP configuration:
{
"mcpServers": {
"picorn": {
"url": "https://picorn.com/mcp"
}
}
}
It uses Streamable HTTP. There is no package or API key to install.
A useful first test
Create a 1080x1080 product post with four named layers:
background, transparent product PNG, headline and CTA.
Do not rasterize the text. Put the product behind the headline,
render a preview and return the editable project URL.
Do not publish anything.
That prompt checks whether the document loop works. A vague “make a nice Instagram post” mostly tests the first render.
What Cursor can control
The public MCP currently exposes 30 tools for:
- layered image projects
- text, image, SVG and shape objects
- grouping, alignment, distribution and stacking order
- video timelines, clips, audio and keyframes
- PNG, JPEG, MP4 and WebM rendering
- handing the same project to the browser editor
Publishing and scheduling stay behind an explicit approval step. The agent can prepare the work, but it shouldn’t silently post an unchecked design to a connected account.
The public endpoint is free to try. The tool list, setup and example prompts are here:
Current limitation: I still expect one manual layout pass for many product images, and Picorn isn’t yet aimed at enterprise approval chains. I’d especially value reports where Cursor creates the project successfully but then loses control of a layer during the edit loop.
Disclosure: I used AI assistance to edit this post. The workflow, implementation details and product claims come from my own work on Picorn and were checked before posting.