OKZest
OKZest is a design automation platform for inspecting reusable designs and rendering personalized images through its REST API.
Verdict
Common use cases
- Generate Open Graph images for blog posts
- Create social cards for product launches
- Render A/B test variants of ad banners
- Preview email header images with live copy
- Automate thumbnail generation for video uploads
Integration
- Vendor
- OKZest
- Category
- developer-tools
- Auth
- API_KEY
- Tools
- 4
- Composio slug
okzest
Tools
- Get Design
Return one OKZest design, including its editable URL parameters and usage counters, by design ID.
- Get Design Fields
List the editable field descriptors, accepted types, and choices for an OKZest design before rendering it.
- List Designs
Return one page of designs available to the connected OKZest account. Use page_size and page_number to select the page.
- Render Image
Render an image from an OKZest design with optional temporary layer or background changes. WARNING: each successful call consumes OKZest usage credits or opens. The action sends exactly one render request and does not retry ambiguous failur
Setup
Setup guide
- 11. In Switchy, open Settings → Integrations → Developer Tools and click Connect next to OKZest. 2. You'll be prompted for an API key; grab it from your OKZest dashboard under Account → API Keys (create one if you don't have it yet). 3. Paste the key into Switchy and click Save. 4. Open any Project, type '@OKZest list my designs' and send — if you see a list of templates, the connection works. 5. To render an image, first run '@OKZest show me the fields for design [ID]' to see what you can customize, then '@OKZest render design [ID] with headline "Launch Day" and background #FF5733' to generate the asset. 6. Remember each render call uses one OKZest credit, so confirm your field values before invoking the render tool.
What teammates see: by default, memories from OKZest are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
List My Templates
@OKZest list my designs and show me the design IDs and names
Inspect Design Fields
@OKZest get the editable fields for design ID 12345 so I know what I can change
Render Social Card
@OKZest render design 12345 with headline 'New Feature Live' and background color #0066CC
Create Blog OG Image
@OKZest render design 67890 with title 'How We Scaled to 10M Users' and author 'Jamie Chen'
Generate Thumbnail Variants
@OKZest render design 54321 three times with taglines 'Watch Now', 'Learn More', and 'Get Started'
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@OKZest list the first 10 designs in my account and show me their names and IDs
Here are the first 10 designs from your OKZest account: 1. Product Launch Banner (ID: dzn_8x4k2m) — 1200×628px social template 2. Weekly Newsletter Header (ID: dzn_9p1n5q) — 600×200px email header 3. Team Headshot Frame (ID: dzn_3r7t8w) — 800×800px profile overlay 4. Sale Announcement Card (ID: dzn_6k2m9x) — 1080×1080px Instagram post 5. Event Ticket Template (ID: dzn_4h8j3n) — 1000×400px printable ticket 6. Blog Post Thumbnail (ID: dzn_7m5p2r) — 1200×675px featured image 7. Podcast Cover Art (ID: dzn_2q9k6t) — 3000×3000px square artwork 8. Webinar Promo Slide (ID: dzn_5n8r4m) — 1920×1080px presentation slide 9. Product Badge Sticker (ID: dzn_1k7m3p) — 500×500px circular badge 10. LinkedIn Post Template (ID: dzn_8r2n6k) — 1200×627px link preview Each design can be customized with dynamic fields before rendering.
This example shows OKZest's design catalog retrieval. Useful for discovering available templates before customization. Requires valid API key with read access. The list is paginated — accounts with many designs will need multiple queries with page_number increments to see everything.
@OKZest get the editable fields for design dzn_8x4k2m so I know what I can customize
Design dzn_8x4k2m (Product Launch Banner) has these editable fields: • **headline** (text) — Main announcement text, max 60 characters • **subheadline** (text) — Supporting copy, max 120 characters • **cta_text** (text, choices: "Learn More", "Shop Now", "Get Started", "Sign Up") — Button label • **product_image** (image_url) — Product photo, recommended 800×800px minimum • **brand_color** (color_hex) — Accent color for CTA button and borders • **logo** (image_url) — Company logo, transparent PNG recommended All fields are optional — omitted fields will use the design's default values.
This example demonstrates field introspection before rendering. Critical for understanding what parameters a design accepts and their constraints. Use this before calling Render Image to avoid errors. No usage credits consumed — this is a metadata-only read operation.
@OKZest render design dzn_8x4k2m with headline 'New Feature Live' and brand_color '#FF6B35' then give me the image URL
I've rendered your Product Launch Banner with the custom headline and brand color. Here's the result: **Image URL:** https://renders.okzest.com/img_9k2m5n8p.png **Render details:** • Design: dzn_8x4k2m (Product Launch Banner) • Custom fields applied: headline, brand_color • Dimensions: 1200×628px • Format: PNG with transparency preserved **Important:** This render consumed 1 usage credit from your OKZest account. The image URL is permanent and can be used in emails, social posts, or downloaded directly. Remaining credits in your account: 487.
This example shows the core render workflow with field overrides. WARNING: Each successful render consumes account credits or "opens" — treat this as a billable action. The returned URL is permanent and CDN-hosted. Failed renders (invalid field values, missing required fields) do not consume credits. Always check field requirements with Get Design Fields first to avoid wasted renders.
Use-case deep-dives
When OKZest wins for small-team social media batching
A 3-person marketing team running weekly LinkedIn and Twitter campaigns needs 15-20 branded graphics per week—hero images, quote cards, event announcements. OKZest is the right call here if the team already has design templates locked in and needs AI to swap copy, colors, or photos without opening Figma every time. The MCP's four tools let you list available designs, inspect which fields are editable (headline text, background color, logo placement), and render final images in one conversation. The trade-off: each render consumes account credits, so this works when you're batching 10+ variations in a session, not generating one-off assets all day. If your team is still iterating on brand guidelines or needs custom layouts per post, stick with a designer and skip the automation until templates stabilize.
OKZest for SaaS teams sending templated welcome graphics
A 6-person SaaS startup sends personalized onboarding emails with a welcome graphic showing the customer's company name and industry icon. OKZest handles this if the design template is already built and the team wants AI to render variations without manual Photoshop work for every new signup. The MCP's Get Design Fields tool shows which parameters accept text or image swaps, then Render Image generates the final asset with the customer's data injected. The boundary: this only makes sense if you're onboarding 5+ customers per week and the design stays consistent. If each customer needs a bespoke layout or you're onboarding one customer per month, the credit cost and setup overhead outweigh the time saved. For high-volume, low-variation graphics, OKZest turns a 10-minute Photoshop task into a 30-second AI prompt.
When OKZest isn't the right tool for help-center images
A 4-person support team maintains a knowledge base with 200+ articles, each with annotated screenshots showing UI steps. OKZest is the wrong call here because the MCP is built for rendering templated designs with variable text or images, not editing or annotating screenshots of your product. The tool set (List Designs, Get Design Fields, Render Image) assumes you're working from pre-built OKZest templates, not raw screenshots that need arrows, callouts, or red boxes added. If your help center needs frequent screenshot refreshes after UI changes, you want a tool like Snagit or Markup, not a design-rendering API. OKZest shines when the creative work is already done and you need to scale variations—support docs require the opposite workflow, where each image is a one-off edit tied to a specific product state.
Frequently asked
What does the OKZest MCP do in Switchy?
It lets your AI agents generate custom images from your OKZest design templates without leaving the conversation. Agents can list your templates, check which fields are editable, and render images with dynamic text or background changes. Each render consumes credits from your OKZest account, so the AI only calls it when you explicitly ask for an image.
Do I need admin access to connect OKZest?
You need an OKZest API key, which any account holder can generate from their OKZest dashboard. The key grants full access to your designs and usage credits, so only connect accounts you control. If you're on a team OKZest plan, confirm with your admin before connecting to avoid unexpected credit consumption.
Can the MCP edit my OKZest design templates?
No. It can only read template metadata and render images with temporary field overrides. The underlying design stays unchanged in OKZest. If you need to modify a template's layout or add new fields, do that in the OKZest editor first, then the MCP will see the updated version on the next list or render call.
Why use this instead of the OKZest API directly?
The MCP wraps the API so your AI can generate images conversationally without you writing code. If you're already automating OKZest via Zapier or custom scripts, keep doing that for high-volume workflows. Use the MCP when you want an agent to create one-off social cards, thumbnails, or reports during a chat session.
Who on the team should connect the OKZest account?
Whoever owns the OKZest subscription and understands the credit limits. Each render call consumes usage credits, so the connector needs to monitor spend. If multiple people need image generation, connect one shared OKZest account to Switchy rather than each person connecting their own key.