Picnie

@Picnie compress all product images in /assets/hero-banners to WebP at 80% quality and show me the size savings

I've compressed 12 images from your hero-banners folder. Original total: 8.4 MB. Compressed total: 2.1 MB (75% reduction). All files converted to WebP at 80% quality. Processed URLs are now available in Picnie's output bucket. This operation consumed 12 credits from your Picnie account. The largest savings came from hero-product-3.jpg (1.2 MB → 280 KB).

This example shows batch image optimization — a common workflow for developers preparing assets for production. Each compression consumes one Picnie credit, so bulk operations can add up quickly. You'll need your API key configured and sufficient credit balance before running large batches.

@Picnie add our logo watermark to the latest screenshot in /screenshots, bottom-right corner, 15% opacity

Watermark applied to screenshot-2024-01-15.png. I've overlaid your logo (logo-white.png from your Picnie assets) at the bottom-right with 15% opacity. The output image maintains the original 1920×1080 resolution and is now available at the processed URL. This operation consumed 1 Picnie credit. The watermark positioning used Picnie's 'southeast' anchor with 20px padding.

This demonstrates a single-image write operation with styling parameters. Picnie's watermark tool requires both images to be publicly accessible URLs. The positioning vocabulary ('southeast', padding values) follows Picnie's conventions, which aren't exhaustively documented — trial-and-error may be needed for precise placement.

@Picnie generate social media preview images from our 'product-launch' template for the three features we discussed earlier, then summarize which layouts worked best

I've generated 3 images from your product-launch template, substituting feature names and descriptions into the dynamic text fields. All three rendered successfully at 1200×630 (Open Graph standard). Template used: 'product-launch-v2'. Credits consumed: 3. Looking at the outputs, the 'AI Assistant' card has the most balanced text density — the headline and body copy both fit without truncation. The 'Real-time Sync' card's description overflowed slightly, suggesting you may want to shorten that copy or adjust the template's text-box height.

This pairs Picnie's template rendering with the AI's visual reasoning. The MCP returns processed image URLs; the AI can't see the pixels but can reason about text-length fit based on your template's known constraints. Template setup happens in Picnie's dashboard beforehand — the MCP can't create templates, only populate them.

When Picnie wins for small-team social campaigns

A 3-person marketing team running weekly social posts across Instagram, LinkedIn, and Twitter needs 15-20 branded images every Monday morning. Picnie's template and batch tools let one person feed a CSV of headlines and CTAs into Create Image Collection, then watermark and compress the outputs in two more calls. The API-key auth means the whole flow runs in a single Switchy chat without OAuth handshakes. This works until your brand guidelines get complex—Picnie's font and filter catalogs aren't fully documented, so if you need exact Pantone matches or custom typefaces, you'll hit a wall. If your templates stay simple and your volume stays under 100 images a week, Picnie keeps asset production inside the AI workspace instead of bouncing to Canva.

Picnie handles high-volume product photography workflows

A 6-person e-commerce team uploading 200 new SKUs a month needs every product shot compressed to under 150KB, converted to WebP for the site, and stamped with a corner logo. Picnie's Compress Image and Add Image Watermark tools let a junior ops person paste a Dropbox share link into Switchy and get back optimized URLs in 30 seconds per batch. The metadata tool can embed SKU numbers into EXIF fields for DAM hygiene. This breaks down if your images aren't already public URLs—Picnie requires web-accessible inputs, so you'll need a staging bucket. It also burns credits fast at scale; confirm your Picnie plan covers your monthly image count before committing. For teams shipping dozens of products weekly and already using cloud storage, Picnie turns image prep into a chat command.

When Picnie is overkill for support ticket visuals

A 4-person support team wants to annotate user-submitted screenshots with arrows and callouts before replying to tickets. Picnie's Add Text Watermark can overlay labels, but it's designed for branding, not precise annotation—you can't draw shapes or position text by pixel coordinates. The filter and metadata tools don't help here. For this scenario, a dedicated screenshot tool like Markup or even Slack's built-in editor is faster and cheaper than burning Picnie credits on workaround hacks. Picnie shines when you need repeatable, template-driven image ops at scale; one-off annotations in a support queue don't justify the API overhead. If your team is already paying for Picnie for marketing work, you can use it in a pinch, but don't buy it for support tickets alone.