Imagior
Imagior is an AI-powered automated image generation software that enables businesses and creators to create and customize images using templates via no-code or API solutions.
Verdict
Common use cases
- Audit all design templates before a sprint
- Retrieve template IDs for API integration
- Inventory assets for a client handoff
- Check which templates exist in production
Integration
- Vendor
- Imagior
- Category
- developer-tools
- Auth
- API_KEY
- Tools
- 1
- Composio slug
imagior
Tools
- List design templates
Tool to list all design templates. Use when you need to retrieve every template associated with your account.
Setup
Setup guide
- 11. Open your Switchy workspace and navigate to Settings > Integrations. 2. Find Imagior in the developer tools section and click Connect. 3. You'll be prompted to paste an API key — log into your Imagior dashboard, go to API Settings, and generate a new key with read access to templates. 4. Copy the key and paste it into Switchy, then click Authorize. 5. Return to any Space and type '@Imagior list all templates' to confirm the connection works. 6. If you see a JSON response with template names and IDs, setup is complete. 7. To invoke the tool in future conversations, @mention Imagior and ask it to list templates — the AI will call the tool and format results inline.
What teammates see: by default, memories from Imagior are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
List All Templates
@Imagior list all design templates in my account and show me the template names and IDs in a table.Open in a Space →
Find Template by Keyword
@Imagior list all templates, then filter the results to show only those with 'hero' or 'banner' in the name.Open in a Space →
Count Active Templates
@Imagior retrieve all templates and tell me how many are currently in my account.Open in a Space →
Export Template Metadata
@Imagior list all templates and format the output as a CSV with columns for template ID, name, and creation date.Open in a Space →
Identify Unused Templates
@Imagior list all templates, then cross-reference them with the project brief in this Space and flag any templates we haven't mentioned.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Imagior list all design templates in my account and show me which ones were created in the last 30 days
Retrieved 47 design templates from your Imagior account. 8 templates were created in the last 30 days: 'Product Launch Banner v3' (created 5 days ago), 'Email Header - Q1 Campaign' (12 days ago), 'Social Media Grid Template' (18 days ago), 'Landing Page Hero Section' (22 days ago), and 4 others. The remaining 39 templates range from 2 months to 2 years old. Most recent templates use the 1200x628 dimension standard.
This example shows the MCP's single tool in action — listing templates — paired with the AI's filtering logic. The MCP returns raw template metadata; the AI handles date math and sorting. Requires valid API_KEY with read access to your Imagior account.
@Imagior which templates use the 'modern-gradient' style tag, and what dimensions do they support?
Found 12 templates tagged 'modern-gradient' in your account. Dimensions supported: 6 templates at 1920x1080 (landscape), 4 at 1080x1080 (square), and 2 at 1080x1920 (portrait). Template names include 'Gradient Hero Banner', 'Product Showcase Card', and 'App Store Feature Graphic'. All 12 were last modified between March and October 2024.
Demonstrates filtering template metadata by custom tags and extracting dimension specs. The MCP provides the full template list; the AI performs the tag-matching and dimension grouping. Useful for auditing design system consistency across your template library.
@Imagior show me all templates and identify any duplicates or near-duplicates based on their names and dimensions
Analyzed 47 templates. Potential duplicates detected: 'Email Header v2' and 'Email Header v2 Final' (both 600x200), 'Product Card Template' and 'Product Card - Updated' (both 800x600), 'Social Post Square' and 'Social Post 1:1' (both 1080x1080). These 6 templates share identical dimensions and similar naming patterns, suggesting they may be redundant versions. Consider consolidating to reduce clutter.
Shows the AI reasoning over the full template list to surface organizational issues. The MCP retrieves all templates in one call; the AI detects patterns humans might miss. Helpful for template library cleanup, but the MCP itself has no update or delete capability — you'll need to act on findings manually in Imagior's UI.
Use-case deep-dives
When a single-tool MCP makes sense for template inventory
A 3-person marketing team runs monthly audits of their design templates to prune outdated assets and track what's actually in use. Imagior's MCP gives them one tool—list all templates—which is exactly what they need for this workflow. The API key auth is straightforward, and the single scope means there's no permission sprawl to manage. This works if your audit is purely inventory: you're counting, categorizing, or exporting template metadata. If you need to preview thumbnails, edit templates, or pull usage analytics, you'll hit the wall fast—this MCP doesn't expose those operations. For a quarterly cleanup task where you just need the list, this is a clean fit. If your workflow touches templates daily or needs richer data, look for a more complete integration.
Why this MCP falls short for onboarding automation
A 6-person product team wants to auto-generate onboarding docs by pulling design templates into a Notion workspace during new hire setup. Imagior's MCP can list the templates, but it can't fetch the actual files, render previews, or trigger template duplication—all of which this workflow requires. You'd get a list of template names and IDs, then hit a dead end. The single-tool limitation means you're stuck writing custom API calls for the rest of the pipeline, which defeats the point of using an MCP. This scenario needs at least three tools: list, fetch, and duplicate. If your use case is just checking whether a template exists before kicking off a manual step, the MCP works. If you're building end-to-end automation, skip this and use Imagior's REST API directly.
When read-only template access speeds up customer support
A 2-person support team fields questions about which design templates customers have access to. They use Switchy to query Imagior during live chat sessions, pulling the template list to confirm what's available under a given account. The MCP's single tool—list templates—covers this narrow use case cleanly. Auth is API key, so there's no OAuth dance to maintain, and the read-only scope means the support team can't accidentally modify templates while troubleshooting. This works because the workflow is lookup-only and happens a few times per day. If your support team needs to preview templates, share links, or update metadata, you'll need more tools than this MCP provides. For a simple 'what templates does this account have' query, this is the right tool at the right size.
Frequently asked
What does the Imagior MCP do in Switchy?
It lets your AI agents list and retrieve design templates from your Imagior account. This is useful when you're building workflows that need to reference or select from your library of image templates — for example, generating social media graphics or marketing assets programmatically. The MCP currently exposes one tool focused on template discovery.
Do I need special permissions to connect Imagior?
You need an Imagior API key, which typically requires account owner or admin access to generate. The key grants read access to your template library. If you're on a team plan, check with whoever manages your Imagior account before connecting it to Switchy.
Can the Imagior MCP create or edit templates?
No. It only lists existing templates from your account. If you need to create new designs or modify templates, you'll still use Imagior's web interface or their full API directly. The MCP is read-only and focused on template discovery for now.
Why use this instead of Imagior's API directly?
The MCP wraps Imagior's API in a format AI agents understand natively. Instead of writing code to authenticate and parse responses, your agents can just ask for templates in plain language. It's faster for prototyping workflows, but if you need fine-grained control or write operations, stick with the API.
Does connecting Imagior count against my Switchy plan limits?
The connection itself doesn't count, but every time an agent calls the list-templates tool, it uses tokens from your Switchy plan. If you're querying large template libraries frequently, monitor your usage dashboard. Imagior's own API rate limits still apply regardless of your Switchy plan tier.