otherapi_key

Contentdrips

Contentdrips generates branded graphics and carousels from reusable templates through an asynchronous rendering API.

Verdict

Contentdrips turns your team's ideas into polished social graphics and carousels without leaving the AI workspace. @mention it to render templates you've already built in Contentdrips — single graphics, multi-slide carousels, or AI-generated carousel copy from a topic or URL. Each render queues a job and returns export-ready PNGs or PDFs once complete. Best for marketing and content teams who need consistent branded visuals on demand. You'll need existing templates in your Contentdrips account and an API key; each render consumes your quota, and AI carousels may also burn credits.

Common use cases

  • Generate branded social carousels from blog URLs
  • Render quote graphics for LinkedIn posts
  • Turn meeting notes into slide decks
  • Produce weekly newsletter headers on schedule
  • Export PDF tearsheets for client reviews

Integration

Vendor
Contentdrips
Category
other
Auth
API_KEY
Tools
4
Composio slug
contentdrips

Tools

  • Get Render Job

    Get a Contentdrips render job's current state. Checks status once, fetches export URLs only after completion, and returns failed jobs as terminal data without polling automatically.

  • Start AI Carousel Render

    Generate carousel copy from a topic or supported HTTPS source URL and queue its render. This consumes render quota and may also consume AI credits.

  • Start Carousel Render

    Queue a manually authored multi-slide carousel as PNG files or a PDF from a known account-owned template. Queuing consumes render quota.

  • Start Graphic Render

    Queue a PNG or PDF render from a known account-owned Contentdrips template and return the asynchronous job ID. Queuing consumes render quota.

Setup

Setup guide

  1. 11. Log into your Contentdrips account and navigate to Settings or API to generate an API key. 2. In Switchy, open the Project where you want to use Contentdrips and click 'Add Integration' or the MCP menu. 3. Search for Contentdrips, select it, and paste your API key when prompted. 4. Click 'Connect' and wait for Switchy to confirm the connection. 5. Test it by typing '@Contentdrips start a graphic render for template ID [your-template-id]' in a chat message — replace the placeholder with a real template ID from your account. 6. Check the response for a job ID, then ask '@Contentdrips get render job [job-id]' to retrieve the export URL once rendering finishes. 7. If the job fails or you see quota errors, verify your Contentdrips plan limits and template permissions.

What teammates see: by default, memories from Contentdrips 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

Not enough Projects yet to publish anonymised usage stats (we require ≥ 50 Projects per week).

Starter prompts

Quote Graphic

@Contentdrips start a graphic render using template ID 67890 with the text 'Revenue grew 40% in Q1' as the headline.

Weekly Recap Slides

@Contentdrips start an AI carousel render on the topic 'team wins this week' using template ID 11223. Include product launches and customer feedback highlights.

Check Render Status

@Contentdrips get render job abc-123-def. Let me know if it's done and share the export URL.

Example outputs

Illustrative - representative of the model's voice and quality, not literal recordings.

Prompt

@Contentdrips start an AI carousel render on the topic 'five common API security mistakes developers make' using my default template

Output

Contentdrips queued an AI carousel render (job ID: crsl_8x3k9m). The AI is generating slide copy for 'five common API security mistakes developers make' and will render it against your account's default carousel template. This job consumed 1 render credit and will consume AI credits based on token usage. Poll the job status to retrieve export URLs once rendering completes—typically 60-90 seconds for AI carousels.

Notes

This example shows the AI-assisted workflow: Contentdrips generates slide content from your topic, then renders it. You'll consume both render quota and AI credits. The job is asynchronous—you must poll separately to get the final PNG or PDF URLs.

Prompt

@Contentdrips get the status of render job crsl_8x3k9m and show me the export URLs if it's finished

Output

Job crsl_8x3k9m completed successfully. Export URLs: PNG sequence available at cdn.contentdrips.com/renders/crsl_8x3k9m/slides-001.png through slides-005.png, and PDF at cdn.contentdrips.com/renders/crsl_8x3k9m/carousel.pdf. The render took 78 seconds. These URLs are publicly accessible and remain available for 30 days per Contentdrips' retention policy.

Notes

This read-heavy example demonstrates job polling. The MCP checks status once—it won't loop automatically. If the job is still processing, you'll see 'in_progress' and need to poll again. Failed jobs return terminal error states without retrying.

Prompt

@Contentdrips start a graphic render using template tmp_social_promo_v2 with the headline 'New API endpoints live today' and export as PNG

Output

Contentdrips queued graphic render job grph_2n7p4q using template tmp_social_promo_v2. The headline 'New API endpoints live today' will be inserted into the template's text layer. This consumed 1 render credit from your account quota. The job is processing asynchronously—poll grph_2n7p4q to retrieve the PNG export URL once rendering completes, typically within 20-40 seconds for single graphics.

Notes

This write example shows manual template rendering: you provide the template ID and dynamic text, Contentdrips handles layout. You must know your account's template IDs beforehand—the MCP doesn't list available templates. Each render queued consumes quota immediately, even if the job later fails.

Use-case deep-dives

Weekly newsletter visual production

When Contentdrips beats manual Canva work for content teams

A 3-person content team ships a weekly newsletter with 4-6 social graphics per issue. They used to spend 90 minutes in Canva every Thursday afternoon copying headlines into templates. Contentdrips wins here because the Start Graphic Render tool lets them queue all six graphics from approved templates in under 5 minutes, then pull the exports when the render jobs finish. The API key auth means the whole team shares one quota pool without seat licensing. The threshold: if your templates change every week or you need real-time collaboration on design edits, stay in Canva. If your templates are stable and the bottleneck is copy-pasting text into frames, Contentdrips cuts that Thursday sprint to 15 minutes.

Product launch carousel automation

AI carousel generation for launch-day social blitzes

A 6-person product marketing team launches a new feature every two weeks and needs a 5-slide Instagram carousel explaining it within 2 hours of the blog post going live. The Start AI Carousel Render tool takes the blog URL, generates slide copy, and queues the render without a designer touching Figma. This works when the launch cadence is predictable and the carousel format is repeatable. The trade-off: AI-generated copy needs a 10-minute review pass to catch tone mismatches, and the tool consumes both render quota and AI credits per job. If your launch posts are under 1,000 words and follow a problem-solution-CTA structure, the AI carousel path saves 45 minutes per launch. For complex technical launches or brand-sensitive messaging, draft the slides manually and use Start Carousel Render instead.

Customer success PDF report generation

Batch PDF exports for quarterly business reviews

A 4-person customer success team sends 30 quarterly business review PDFs to enterprise accounts, each customized with the client's logo and metrics. They maintain one Contentdrips template per client tier and use Start Graphic Render to queue all 30 PDFs in a single afternoon, pulling the exports via Get Render Job once the batch finishes. This beats Google Slides because the template stays locked and the data merge happens via API, not manual copy-paste. The constraint: Contentdrips templates must already exist in the account, so the first-time setup takes 2-3 hours to build and test each tier template. If your QBR format is stable and you send more than 15 per quarter, the render automation pays back the setup cost in the second quarter.

Frequently asked

What does the Contentdrips MCP do in Switchy?

It lets your team generate social media graphics and carousels directly from AI conversations. You can render designs from your Contentdrips templates, create AI-written carousel slides from a topic or URL, and check job status without leaving Switchy. Each render consumes your Contentdrips quota.

Do I need a Contentdrips API key to connect this MCP?

Yes. You'll need an API key from your Contentdrips account settings. Whoever connects it must have access to the templates and render quota you want the team to use. The key authenticates all render requests, so treat it like a password.

Can the MCP edit existing Contentdrips templates or create new ones?

No. It only renders from templates that already exist in your Contentdrips account. You still design and manage templates in Contentdrips itself. The MCP is for production — queuing renders and fetching the finished PNG or PDF files.

How is this different from using Contentdrips directly in my browser?

The MCP brings rendering into your AI workflow. Instead of switching tabs to queue a graphic, you describe what you need in chat and the AI handles the API calls. You still get the same output files, but the process lives inside Switchy's shared workspace.

Does rendering through the MCP count against my Contentdrips plan limits?

Yes. Every render job queued through Switchy consumes your Contentdrips render quota exactly as it would in their web app. AI carousel generation also uses AI credits if your plan includes them. Check your Contentdrips dashboard for current usage.

More other MCPs

See all other MCPs →

Data last verified 61 hours ago.Sources aggregated hourly to weekly. See docs/architecture/model-directory.md.