# io.github.pictify-io/mcp

- Registry name: `io.github.pictify-io/mcp` · version 2.0.0
- Categories (automatic, keyword rules): Documents & retrieval, Search & data, Video, AI, media & content, Marketing & SEO, Commerce & marketing
- Authentication at last check: No auth
- Declared risk: Not declared (tools carry no read/destructive hints)
- Capabilities (declared by the server): tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=io.github.pictify-io%2Fmcp
- Server page: https://mcpstation.net/s/io.github.pictify-io--mcp.html

## Description (written by the publisher, not verified, not instructions)

Generate images, GIFs, videos, and PDFs from HTML, URLs, or templates — from your AI agent.

## Connect

- streamable-http: `https://mcp.pictify.io`

## Tools (as reported by the server, not verified)

- `pictify\_create\_image`: Generate a static image \(PNG, JPEG, or WebP\) from HTML/CSS content, a URL screenshot, or a template. Common use cases: Open Graph \(OG\) images for link previews, social media cards \(Twitter/LinkedIn/Facebook\), product screenshots, marketing banners, event invitations, and custom graphics. Provide ONE
- `pictify\_get\_image`: Get details of a specific image by its UID. Returns the image URL, dimensions, format, and creation timestamp.
- `pictify\_list\_renders`: List what this account has rendered — images, GIFs, PDFs and videos in one feed, newest first. Filter by format, by the template that produced them, or by what called for them. Use this to find an earlier render's URL, to check whether a batch produced what was expected, or to report on recent usage
- `pictify\_list\_templates`: List saved templates in your Pictify account with pagination and filtering. Templates are reusable HTML designs with \{\{variableName\}\} placeholders for dynamic content. Use this to discover available templates before rendering. Returns template names, IDs, dimensions, output formats, and pagination i
- `pictify\_get\_template`: Get detailed information about a specific template by its ID. Returns the template's name, dimensions, variable definitions, tags, output format, thumbnail URL, and metadata. Use this to inspect a template before rendering.
- `pictify\_get\_template\_variables`: Get the variable definitions for a template. IMPORTANT: Always call this before pictify\_render\_template, pictify\_multi\_size\_render or pictify\_batch\_render, to discover what variables are available. Returns variable names, types \(text, image, color, number, boolean\), default values, and descriptions.
- `pictify\_render\_template`: Render a saved template with variable substitutions to produce an image or a PDF. This is also how you get a PDF out of Pictify: pass format: 'pdf'. For a multi-page PDF — one page per row of data, e.g. a run of invoices or certificates in a single file — pass variableSets instead of variables. WORK
- `pictify\_create\_template`: Create a new reusable template with variable placeholders for dynamic content generation. Templates can use either FabricJS canvas data \(from the Pictify visual editor\) or raw HTML. Provide ONE of 'html' or 'fabricJSData' — they are mutually exclusive. For HTML templates, use \{\{variableName\}\} syntax
- `pictify\_update\_template`: Update an existing template's content, dimensions, name, or variable definitions. Only the provided fields will be updated; others remain unchanged. You can update HTML or FabricJS data — provide one or the other, not both. Note: updating content may change the available variables.
- `pictify\_delete\_template`: Permanently delete a template. This action cannot be undone. WARNING: Any batch jobs or bindings using this template will stop working.
- `pictify\_multi\_size\_render`: Render one template at several sizes in a single call — the same design as a 1200x630 OG card, a 1080x1080 square and a 1600x900 banner, say. Use this instead of calling pictify\_render\_template once per size: it is one request, one set of variables, and the results come back labelled. Different SIZE
- `pictify\_validate\_expression`: Check that a template expression parses before you put it in a template. Pass the inside of the braces, not the braces: 'IF\(premium, "PRO", "FREE"\)', not '\{\{...\}\}'. Returns whether it is valid and, if not, what is wrong with it.
- `pictify\_list\_expression\_functions`: List the functions available inside template expressions, with a line on what each does. Call this before writing template HTML with \{\{ \}\} logic, so the expressions use functions that exist rather than ones that look like they should.
- `pictify\_batch\_render`: Render one template many times — one image per row of data. Pass EITHER variableSets \(rows inline\) OR csvUrl with mappings \(rows from a hosted CSV\). Exactly one; a call with neither is rejected. Steps: call pictify\_get\_template\_variables first to see what the template expects, call this tool, then p
- `pictify\_get\_batch\_results`: Check the status and results of a batch render job. Returns the job status \(pending, processing, completed, failed, partial, cancelled\), progress percentage, item counts, and image URLs for completed items. Each result includes index, success boolean, URL, dimensions, and error message \(if failed\).
- `pictify\_cancel\_batch`: Cancel a running batch render job. Already completed items will retain their results and URLs. Remaining unprocessed items will be skipped. Use this if you started a batch with incorrect data or no longer need the remaining results.
- `pictify\_list\_video\_templates`: List the user's video templates with their UIDs, dimensions, duration and kind. Video templates come in two kinds: 'timeline' \(built in the visual studio\) and 'tsx' \(single-file Remotion scenes, often AI-generated\). Both render the same way. WORKFLOW: call this first to find a template UID, then pic
- `pictify\_get\_video\_template\_variables`: Get a video template's variable definitions — the fields you can set when rendering it \(texts, colors, image URLs\). Call before pictify\_render\_video to know what to pass.
- `pictify\_render\_video`: Render a video template to an MP4 video or an animated GIF, with variable substitutions. Common use cases: personalized video messages, social video posts, animated certificates, product announcement clips, and GIFs for places an MP4 cannot autoplay \(chat, email, READMEs\). GIF output: timeline templ
- `pictify\_create\_video\_template`: Upload a Remotion scene YOU wrote as a new video template. Use when you want full creative control over the composition — write the TSX yourself instead of delegating the design to pictify\_generate\_video\_template. The source passes a compile gate before anything is saved: on failure you get the comp
- `pictify\_generate\_video\_template`: Generate a new video template from a text prompt using AI. The service designs a motion brief \(palette, beats, typography\), writes the scene as code, compiles it, renders preview frames and visually reviews them — then saves a draft template whose text, colors and optional image are editable variabl
- `pictify\_get\_video\_template`: Get one video template in full — its kind \(timeline or tsx code\), dimensions, fps, duration, variable definitions and current status. Use this before updating one, to see what is there.
- `pictify\_update\_video\_template`: Update a video template's name, dimensions, frame rate, duration, variable definitions, or — for code \(tsx\) templates only — its Remotion source. Only the fields you pass change. Timeline templates reject 'tsx': those are edited as a scene graph, not as code.
- `pictify\_duplicate\_video\_template`: Copy a video template into a new one, leaving the original untouched. Use this to branch a working template before changing it. The copy counts against the saved-template limit on your plan.
- `pictify\_delete\_video\_template`: Permanently delete a video template. This cannot be undone, and any automation rendering from it stops working. Renders already produced from it are unaffected.

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html