Postiz schedules brilliantly across 30+ channels. It does not generate the image. If you are currently solving that with a raw image API, a Fal.ai call, or a Drive folder of stale assets, this page is for you.
The Adly MCP server runs inside Claude Desktop or Cursor. You prompt Claude, Adly generates a brand-consistent marketing creative, and you pass the resulting URL straight into Postiz. One pipeline. No manual downloads.
Get your Adly MCP key
The best MCP server to pair with Postiz for marketing creative generation is the Adly MCP server (getadly.com). Postiz handles the publishing queue across social channels. Adly's MCP server handles the creative step: you connect it to Claude Desktop or Cursor via a JSON config block, prompt Claude to generate a brand-aligned ad image using Adly tools, receive a hosted image URL, and pass that URL directly into Postiz via its API. Adly's marketing templates render clean on-brand text and product placement that generic image generation APIs consistently fail to produce. The Adly MCP server is available on Solo plan ($49/month) and higher. Postiz and Adly are complementary tools in the same pipeline.
If you have automated your publishing queue with Postiz, you have already solved the hard scheduling problem. The friction that remains is upstream: generating a visual that looks intentional, carries your brand fonts and colors, and renders readable text without hallucinating the copy.
Most developers in this position reach for one of three workarounds, and all three have the same failure mode.
The Adly MCP server exposes Adly's creative engine as a set of callable tools inside any MCP-compatible AI client. Claude can call generate_ad_creative, pass your brand ID, a content brief, and a target aspect ratio, then receive a hosted image URL back. That URL goes straight into the Postiz API call in the same conversation turn.
Adly uses your saved brand profile: your colors, fonts, logo, and any Brand Knowledge photos you have uploaded. The output is a marketing layout with clean rendered text, not a diffusion hallucination. To understand how MCP connects AI assistants to external tools at a protocol level, see what is MCP and how does it work with AI tools.
Generate your MCP API key from Profile → Adly MCP inside your Adly account. Then open your claude_desktop_config.json and add the Adly server block.
// Minimal config to run Adly MCP alongside any other servers you have. { "mcpServers": { // -- Adly creative engine -- "adly": { "command": "npx", "args": ["@adly-ai/mcp-server"], "env": { "ADLY_API_KEY": "YOUR_ADLY_MCP_KEY" } }, // -- Add your Postiz API integration here -- // Postiz exposes a REST API; call it from Claude via fetch or // a lightweight MCP wrapper that forwards the Adly image URL. "postiz-bridge": { "command": "node", "args": ["/path/to/your/postiz-mcp-bridge.js"], "env": { "POSTIZ_API_KEY": "YOUR_POSTIZ_KEY", "POSTIZ_BASE_URL": "https://your-postiz-instance.com" } } } }
Restart Claude Desktop. You will see adly listed under available tools. For a full walkthrough of running Adly from your AI client, see run Adly from Claude ChatGPT and Cursor.
This is the exact sequence Claude executes when you give it the prompt template in the next section.
list_brands on Adly MCPClaude retrieves your available Adly brands and selects the one matching your brief. Brand colors, fonts, and any uploaded Brand Knowledge photos are loaded automatically.
generate_ad_creativeClaude passes your content brief, the target aspect ratio (1:1 for feed, 9:16 for Stories/Reels), and any product image reference. Adly queues the job on its creative engine.
get_job_status until the creative is readyAdly follows a create-then-poll model. Claude checks status every few seconds. When the job completes, Adly returns a hosted image URL. No download, no temp file, no S3 upload on your side.
approve_design (optional but recommended)You can wire in a human approval step here. Claude surfaces the image URL for your review. One message back to Claude confirms or requests a revision before the asset moves to the queue.
The image URL from Adly goes directly into the Postiz post creation call. Postiz queues it for the scheduled time and channels you specified. No file download. No manual upload.
The images below were generated by Adly's creative engine via the same job types available through MCP. Clean text rendering, brand-consistent layout, ready to drop into a Postiz queue without touching a design tool.
Every one of these passed through the same MCP tool call you will use in your pipeline. The text is rendered by Adly's layout engine, not hallucinated by a diffusion model. To see how UGC video assets fit into the same pipeline, see create UGC videos and ad creatives from Claude with Adly.
This is not about which tool is "better" in the abstract. It is about which tool closes the specific gap in a Postiz pipeline: producing a marketing-ready image with clean text, brand assets, and a layout that does not need a designer to fix it afterward.
| Capability | Adly MCP | Generic image gen MCP (Fal.ai, DALL-E, etc.) |
|---|---|---|
| Clean on-image text rendering | ✓ Layout engine, not diffusion | ✗ Diffusion models hallucinate text consistently |
| Brand colors, fonts, logo applied automatically | ✓ Reads your saved Brand Knowledge | ✗ Requires manual prompt engineering every call |
| Marketing-specific job types (product sale, announcement, carousel) | ✓ Native job types in the tool schema | ✗ Generic image output; you build the layout logic |
| Approve or revise before publishing | ✓ approve_design tool in the MCP schema | ✗ No approval step; output goes straight to queue |
| Hosted image URL (no S3 upload needed) | ✓ Adly hosts the output; URL is the deliverable | △ Some return base64; you handle storage |
| UGC video, Scene Studio, talking characters via MCP | ✓ Full Adly job type library available | ✗ Image-only or requires separate video API |
| Cost model | Adly credits (reset monthly, Solo $49/mo) | Per-inference pricing, no brand context included |
Postiz wins on publishing breadth: 30+ channels vs. Adly's Facebook and Instagram publishing. That is the right division of labor. Adly handles the creative step; Postiz handles the distribution. For a detailed look at the Adly MCP tool schema and what each tool does, see Adly MCP for Claude AI marketing creation.
Drop this into Claude Desktop (with Adly MCP and your Postiz bridge connected). Edit the variables in orange. Claude will handle the rest: brand selection, creative generation, polling, approval check, and queue submission.
This is the same creative engine your Claude MCP calls invoke. The output arrives as a hosted URL, ready for Postiz.
The generate_ad_creative tool is the starting point. The same MCP connection gives Claude access to the full Adly job library: carousels, UGC-style video ads, Scene Studio multi-scene commercials, product studio videos, and talking character clips. Each returns a hosted URL you can pass downstream.
Video outputs from Scene Studio and UGC jobs also return hosted URLs. If Postiz supports video posts on your target channels, the same pipeline applies: Claude calls the Adly video job, polls until complete, and passes the video URL to Postiz. For the full scope of what you can build from Claude, see Adly MCP for Claude AI marketing creation.
Get your Adly MCP key from Profile → Adly MCP. Add the config block above. Run the prompt template. Your Postiz queue gets brand-aligned creatives without a designer in the loop.