pictify_create_imageLABSCO SUMMARY
Templates plus batch is the combination worth having.
One-off renders are useful, but the shape that saves real work is a template with typed variables and a hundred-item batch behind it — event passes, team badges, a product catalogue — started as a job and collected when it finishes rather than looped one call at a time.
What it is
Pictify's rendering API as a server: images from HTML and CSS, from a URL screenshot or from a reusable template; animated GIFs from CSS animation or recorded off a live page; PDFs from templates; and batches of up to 100 personalised renders in one job.
What you get
- An image generated from HTML and CSS, a URL screenshot, or a template — OG images, social cards, banners, product shots
- Images from FabricJS canvas JSON, for anything authored on a canvas rather than in markup
- Animated GIFs two ways: rendered from CSS animation, or captured off a live web page over time
- PDFs from templates, single-page or multi-page, with the available page-size presets listable — invoices, certificates, reports, shipping labels
- A template system you can work from inside the conversation: templates listed with filters and paging, opened, created, updated and deleted, with their variable definitions and types readable before you render
- Templates rendered with variables and layout variants, backed by 50+ expression functions for conditionals, string handling and date formatting
- Batch renders of up to 100 items started asynchronously, polled for status and result URLs, and cancelled mid-run
- Everything generated stays listable and fetchable by ID afterwards, for images and GIFs alike
Requirements
A Pictify account and an API token from the dashboard. Two ways in: over stdio from npm as @pictify/mcp-server with PICTIFY_API_KEY set, or the hosted remote at https://mcp.pictify.io added as a custom connector, where the client ID is pictify and the client secret is your token. PICTIFY_BASE_URL moves the API base and PICTIFY_DEBUG turns on verbose logging to stderr.
Setup effort
One command plus a key — npx -y @pictify/mcp-server, then supply credentials
USE CASES
01
Making an OG image for a page you just wrote
Hand over the HTML and CSS, or point at the URL, and get an image back with a hosted link.
02
Producing a hundred personalised passes
Build the template with its variables, start the batch, then poll for the status and collect the result URLs.
03
Generating an invoice or a certificate as a PDF
Check which page-size presets exist, render the template with this month's values, and take the multi-page route when the document runs long.
04
Showing a feature moving rather than still
Render the animation from CSS, or record the real page over a few seconds, and get an animated GIF you can paste into a release note.
05
Reusing the design your team already made
Find the saved template, read what variables it expects and their types, then render it with this week's content.
06
Fixing a template that has drifted
Open it, update the markup or the variables, re-render to check, and remove the one it replaced.
21 tools
Listed in project docs. Your client may show a different list.
pictify_create_canvas_imagepictify_list_imagespictify_get_imagepictify_create_gifpictify_capture_gifpictify_list_gifspictify_get_gifpictify_render_pdfpictify_render_multi_page_pdfpictify_list_pdf_presetspictify_list_templatespictify_get_templatepictify_get_template_variablespictify_render_templatepictify_create_templatepictify_update_templatepictify_delete_templatepictify_batch_renderpictify_get_batch_resultspictify_cancel_batchBEFORE YOU INSTALL
What to know first
Tools you get
21 tools named in the project's documentation.
Requires
- npx on PATH
- PICTIFY_API_KEY in your environment
Where it runs
All 4 documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
npx
TERMINAL
npx -y @pictify/mcp-serverHosted endpoint
ENDPOINT URL
https://mcp.pictify.ioAdd this hosted endpoint to your MCP client using the credentials listed under Requirements.
MCP Clients
Claude Code
CLAUDE CODE · TERMINAL
claude mcp add pictify -e PICTIFY_API_KEY=<YOUR_PICTIFY_API_KEY> -- npx -y @pictify/mcp-serverClaude Desktop, Cursor, Windsurf
JSON
{
"mcpServers": {
"pictify": {
"command": "npx",
"args": [
"-y",
"@pictify/mcp-server"
],
"env": {
"PICTIFY_API_KEY": "<YOUR_PICTIFY_API_KEY>"
}
}
}
}
