Orshot

@Orshot list all Studio templates tagged 'product-launch' and show me which ones have been rendered in the last 30 days

Found 7 Studio templates tagged 'product-launch' in your workspace. Three have recent renders: 'Hero Banner v3' (rendered 12 times this month), 'Feature Callout Grid' (8 renders), and 'Launch Email Header' (3 renders). The remaining four templates—'Social Promo Square', 'Blog Header Wide', 'Press Kit Cover', and 'LinkedIn Carousel'—have not been rendered since early December. Each template ID and modification options are available if you'd like to render or inspect one.

This example combines List Studio Templates with metadata filtering. Orshot's API returns templates with cursor-based pagination; the MCP handles that internally. The 'recent render' detail is illustrative—actual metadata depends on your workspace's render history. No render credits are consumed by listing.

@Orshot render the 'Weekly Newsletter Header' template with headline text 'Q1 Product Roadmap' and export it as a PNG

Rendered 'Weekly Newsletter Header' (template ID tpl_8x3k) with your headline modification. The 1200×630 PNG is ready at https://cdn.orshot.com/renders/abc123.png (link expires in 24 hours). This render consumed 1 credit from your workspace balance of 487 remaining credits. If you need the same asset in PDF or a different resolution, let me know and I can trigger another render with those parameters.

Render Studio Template is a write operation that deducts credits from your Orshot account. The MCP returns a temporary CDN URL or base64-encoded image; it does not publish to social accounts. Always confirm the template ID and modification schema before rendering at scale to avoid burning credits on incorrect outputs.

@Orshot pull our workspace brand colors and draft a palette recommendation for a new 'trust and security' campaign, then save any new colors you suggest

Your workspace has 14 saved brand colors, anchored by primary blue (#2E5BFF) and neutral slate (#64748B). For a trust-and-security campaign, I recommend pairing your existing blue with a deeper navy (#1E3A8A) for authority and a soft green accent (#10B981) to convey safety. I've added those two new colors to your workspace: navy is now ID clr_9x2a, green is clr_9x2b. You can reference these IDs in future template renders or modify them via the Orshot dashboard.

This example chains List Brand Assets (read) with Add Brand Color (write). The AI synthesizes design reasoning, but the MCP performs the actual save operations. Brand colors are capped at the 200 most recent entries per workspace, so older colors may be pruned. Verify the new color IDs before using them in production renders.

When Orshot beats manual design for recurring posts

A three-person content team publishes 15 social posts every Monday morning across Instagram, LinkedIn, and Twitter. They used to open Canva for each variant; now they store brand colors and templates in Orshot, then render all 15 images in one Switchy conversation by looping through a spreadsheet of headlines and CTAs. The render tool returns URLs they paste straight into Buffer. This works because their templates are stable and their color palette lives in one workspace. If your posts need heavy per-image art direction or you're rendering fewer than five images a week, the setup overhead isn't worth it. But for teams shipping repetitive visual content at volume, Orshot turns a 90-minute design session into a 10-minute API call.

Using Orshot to inventory templates before a refresh

A five-person marketing team is rebranding and needs to know which Studio templates reference the old logo and color palette. They use Switchy to call List Studio Templates, then Get Studio Template for each result, scanning the returned metadata for deprecated asset IDs. The List Brand Assets tool confirms which colors are still in use. This scenario is borderline: Orshot's API doesn't expose deep template-layer details, so if your templates embed assets in complex ways, you'll still need to open the Studio UI. But for teams with under 50 templates and a clear asset-naming convention, this MCP surfaces the inventory in minutes instead of hours of manual clicking.

When render credits justify automated welcome graphics

A six-person SaaS onboarding team sends every new customer a personalized welcome PDF with their company name, logo placeholder, and brand colors pulled from signup forms. They store a single Studio template in Orshot, then render it on-demand during the onboarding Slack thread by passing the customer's hex codes and text into Render Studio Template. The PDF URL goes straight into the welcome email. This only makes sense if you're rendering at least 20 PDFs a month and your template structure is locked; below that threshold, the render-credit cost and API-key rotation overhead outweigh the time saved. For high-volume onboarding or lead-magnet funnels, though, Orshot turns a design task into a one-line function call.