Head to head · Design templates · October 2026 research run

Contentdrips API and MCP vs Templated API + MCP

Templated API + MCP scores 58.8 (C) on agent readiness against Contentdrips API and MCP's 36.3 (F), and leads in every scored category. Both do design templates.

Best programmatic image and design asset APIs for AI agents · All 153 assets comparisons

Which one, for what

Contentdrips API and MCP F

Best for Branded LinkedIn and Instagram carousels and graphics from saved templates, with drafting and publishing in the same server.

Also in its favour

  • No incidents deducted, where Templated API + MCP loses 3 points for them

Watch for

No status page, SLA, numeric rate limit or 429 documentation found

Templated API + MCP C

Best for Agents and SaaS builders who render images, PDFs and short MP4s from templates and want a well-behaved MCP server they can fence per customer.

Ahead on

  • Reliability, 65 against 23
  • Schema & documentation, 74 against 48
  • Agent ergonomics, 70 against 54
  • Security & auth, 42 against 31
  • Payments & pricing, 35 against 25
  • Maintenance & community, 80 against 15
  • Transparency & trust, 76 against 60

Also in its favour

  • Runs on your own machine
  • Free to start without a card

Watch for

One API key with full account access, and the MCP docs document it as ?apiKey= in the URL

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Maintenance & community Templated API + MCP +65

Contentdrips API and MCP 15

The newest dated change to the agent surface is the MCP page, published 25 May 2026 and modified 27 May, 163 days before this check (10). No three dated changes since 8 August were found (0). No public changelog. Email support at hello@contentdrips.com, which we didn't test (5 of 15). Not in the official MCP registry and no official SDKs (0). No public package or repository (0). 10 + 0 + 5 + 0 + 0 = 15.

Templated API + MCP 80

mcp-server-templated v1.9.0 tagged on 2026-10-08, and the newest changelog entry is 27 October 2026 (30). Six MCP tags in the 90 days from 4 August (v1.4.0 and v1.4.1 on 5 August, v1.7.0 and v1.7.1 on 8 September, v1.8.0 on 6 October, v1.9.0 on 8 October) and changelog entries on 4 September, 14 October and 27 October (20). Dated public changelog and support by email. GitHub issue response wasn't checked (github.com refuses our requests) (10). Listed in the official MCP registry as io.github.templated-io/mcp-server-templated, with 1.9.0 published on 8 October by GitHub OIDC from CI (15). @modelcontextprotocol/sdk 1.32.1 and a node test suite, but the only workflow publishes to the registry and doesn't run the tests (5). 30 + 20 + 10 + 15 + 5 = 80.

Reliability Templated API + MCP +42

Contentdrips API and MCP 23

Hosted lines. No status page found on the site, the developer docs or the footers (0). No readable incident history (5). No rate limit is given in numbers, only monthly call allowances by plan (6,000 on Pro, 25,000 on Ultimate), which earn a little (5 of 15). The troubleshooting note says to check /queue/stats and retry after a short delay when rate limited, with no status code or Retry-After. Render jobs are asynchronous, so polling is safe (3 of 15). No SLA found (0). The MCP server is v1.0.0 and the render API is not labelled beta (10). 0 + 5 + 5 + 3 + 0 + 10 = 23.

Templated API + MCP 65

Better Stack status page with API, App and Website components over 30, 60 and 90 days (20). The incidents page lists no incident for September, October or November 2026 and the RSS feed holds no entry, so the page has never posted one. This run scores a page that has never posted an incident 20, not the 30 of a clean record, and the page's own figure for the API is 100 per cent over 90 days (20). Rate limits per plan in the Markdown price list, 60, 150 and 300 requests a minute (15). No 429 behaviour, Retry-After or retry advice in the API docs or llms-full.txt. MCP 1.9.0 tells the model to wait and retry after a 429, which isn't API documentation (0). The pricing page lists "SLA & dedicated support" on the custom plan from $500 a month, with no SLA document or figure found (0). The render API is GA. Video launched on 7 January 2026 as "now live" (10). 20 + 20 + 15 + 0 + 0 + 10 = 65.

Schema & documentation Templated API + MCP +26

Contentdrips API and MCP 48

No OpenAPI or other machine-readable contract for the REST API, and the MCP server is closed, so its schemas weren't read. The MCP page names every tool's parameters (10 of 25, on that partial evidence). The marketing site's llms.txt is generated by Yoast and lists blog posts, with no link to the API or MCP docs; the developer site has none (2 of 10). The MCP page labels each tool Read, Write or Destructive, says get_template_structure is needed before filling or editing, and gives confirmation rules for publishing and deleting (15 of 20). Enums for output, type, AI method and formats, but content_update and carousel_content are open structures keyed by template labels (9 of 15). Request examples and an error table (400, 401, 404, 500) with an error body, while the result section contradicts its own example and some examples omit a required value (9 of 15). Docs marked v1.0.0 and last updated January 2025, with no changelog (3 of 15). 10 + 2 + 15 + 9 + 9 + 3 = 48.

Templated API + MCP 74

No OpenAPI. All 25 MCP tools carry typed JSON Schema inputs, and server.json is published to the MCP registry, so partial credit (18). llms.txt, llms-small.txt, llms-full.txt, pricing.md and a Markdown version of every page (10). Some MCP descriptions guide the model well (update_template explains pages versus layers, create_render names get_template_layers first), others are one line (12). Format and layer type enums and a required template field, and MCP 1.9.0 caps list limits at 100 in the schema, but size, scale and fps limits sit in prose rather than min and max, and layers is an open object (10). Request and response examples per endpoint. Error tables with status codes appear on five endpoints (font, render, template and upload deletes and template update), none on create render (9). Versioned /v1 path, a dated changelog now at templated.io/changelog/ and tagged MCP releases (15). 18 + 10 + 12 + 10 + 9 + 15 = 74.

Agent ergonomics Templated API + MCP +16

Contentdrips API and MCP 54

29 MCP tools (15 for 11 to 30), with no toolsets or read-only subset (15 of 25). list_posts filters by status and get_my_templates by type and workspace, and no pagination is documented (8 of 20). Errors carry error and message, and the troubleshooting section explains template-not-found and label mismatches (12 of 20). Access labels in the docs, confirmed: true on publish_post, and job polling that is safe to repeat, but no idempotency key on renders or post creation, and the labels couldn't be confirmed as MCP annotations (12 of 20). Two required fields to render (template_id, output), and no SDK beyond an Embed SDK for the editor (7 of 15). 15 + 8 + 12 + 12 + 7 = 54.

Templated API + MCP 70

25 MCP tools (15), plus results passed through field allowlists, and MCP 1.9.0 prunes JSON results (get_template_layers about 78 per cent smaller by the release note) (3). Lists take page and limit, default 25 and at most 100 in the MCP, and the MCP can filter to one folder or external ID (17). The API docs give status tables on five endpoints. MCP 1.9.0 (8 October 2026) turns each status into an instruction, such as calling the list tool for a missing ID, reconnecting on 401 or waiting for Retry-After on 429, and rejects unknown layer names before rendering (12). Every tool carries readOnlyHint and destructiveHint, with deletes and template updates marked destructive. No idempotency key (15). Only template is required and renders are synchronous by default, but there are no official SDKs, only code samples in JavaScript, Python and PHP (8). 18 + 17 + 12 + 15 + 8 = 70.

Transparency & trust Templated API + MCP +16

Contentdrips API and MCP 60

Closed service under terms of use dated 11 December 2024, governed by the laws of Pakistan (15). The privacy policy of 9 August 2026 states retention while the account is active, deletion of content as soon as the account is deleted apart from short-lived backups, deletion of social tokens on disconnect, and no training of Contentdrips' own models on user content (22 of 30). No deprecation policy. The legacy carousel input is 'still supported' with no end date (3 of 20). The policy names OpenAI, OpenRouter, Google Gemini and TinyPopups and has an international transfers section, without a full subprocessor list or hosting locations (12 of 20). 15 + 22 + 3 + 12 = 52.

Templated API + MCP 76

MCP server MIT with a LICENSE file. The rendering service is closed under published terms (18). Privacy policy updated 18 October 2026 with retention stated per data type (until you delete, files purged within 90 days of deletion, logs up to 90 days, billing records five years) and a DPA at templated.io/dpa, though it doesn't say whether customer content trains models (25). No deprecation policy or dated deprecation notices found (0). Subprocessors named by purpose, including Gemini, OpenAI, Anthropic and DeepSeek for AI functions, Photoroom for background removal, PostHog and Plausible for analytics and Stripe, Creem and Spedy for payments (18). 18 + 25 + 0 + 18 = 61.

Security & auth Templated API + MCP +11

Contentdrips API and MCP 31

API keys from the dashboard, with no scopes, expiry or rotation documented. The MCP server also runs OAuth 2.0 with PKCE and dynamic client registration, but its one mcp scope authorises the same full key (18 of 30). No read-only key or endpoint. publish_post needs confirmed: true and the docs ask for confirmation before deletes (10 of 20). Tools read blog, YouTube and TikTok links and download external images, and no prompt-injection guidance was found (3 of 15). No audit log or per-call record documented (0). No security.txt, disclosure policy, bug bounty or certification found (0). 18 + 10 + 3 + 0 + 0 = 31.

Templated API + MCP 42

The REST key has full account access by the docs' own words, and the privacy policy says it can be regenerated. The hosted MCP is an OAuth 2.1 resource server since MCP 1.6.0 (18). The MCP setup guide still documents ?apiKey= in the server URL for automations, less 10 (8). Folder and external ID scoping is enforced server side, and destructive tools are annotated so clients can ask first. No read-only key (12). Tool results pass through allowlists, and the docs describe server-side scoping as a guard against prompt injection (12). No audit log or per-call log found for the customer beyond the render list (3). A valid security.txt since 28 October 2026 (Last-Modified), sending reports to support@templated.io and expiring 8 October 2027, and 2FA since September 2026. No certification or bug bounty found (7, as a valid security.txt to a support address with nothing else). 8 + 12 + 12 + 3 + 7 = 42.

Score by category

CategoryWeight this runContentdrips API and MCPTemplated API + MCPEdge
Reliability16%202365Templated API + MCP +42
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.24874Templated API + MCP +26
Agent ergonomics13%16.25470Templated API + MCP +16
Security & auth14%17.53142Templated API + MCP +11
Payments & pricing10%12.52535Templated API + MCP +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.81580Templated API + MCP +65
Transparency & trust7%8.86076Templated API + MCP +16
Negative events≤150-3
TotalF 36.3/100C 58.8/100

Facts side by side

FactContentdrips API and MCPTemplated API + MCP
KindHTTP APIHTTP API
VendorContentdrips SMC Pvt LtdTemplated
Hosted endpointhttps://mcp.contentdrips.com/mcphttps://api.templated.io/v1
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP, stdio
AuthOAuth or keyOAuth or key
PricingPaidPaid
x402nono
LicenceClosed service under the Contentdrips terms of use (last updated 11 December 2024)MIT
Tools exposed2925
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listedio.github.templated-io/mcp-server-templated
Last release2026-05-272026-10-08
Terms last updated2024-12-112026-01-10
Privacy policy last updated2026-08-092026-09-08
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waiveryesnot found in the text
Popularitynone3 stars, 62 npm/wk
Agent reviewsnone4/5 (2)

How the scores have moved

Verdicts

Contentdrips API and MCP

Agents can fill saved templates into PNG or PDF graphics and carousels through a polled render API, and the MCP server labels each tool's access and requires explicit confirmation before publishing. There is no status page, OpenAPI file, rate-limit figure or changelog, and the pricing pages contradict each other on what API access costs.

Templated API + MCP

Templated's MIT-licensed MCP server has 25 tools, each annotated with readOnlyHint and destructiveHint, and can be fenced to one folder or customer. The REST key has full account access, the MCP docs still document it as ?apiKey= in the URL, and MCP 1.9.0 began rejecting calls 1.8.0 accepted with no notice.

Before you call either

Contentdrips API and MCP

  1. Call get_template_structure before filling a template; labels must match meta_labels character for character or the call returns 400
  2. Poll /job/:jobId/status every 5 seconds and give up after 5 minutes, as the docs advise
  3. Never set confirmed: true on publish_post until the user has agreed and named LinkedIn, Instagram or both
  4. Ask before delete_graphic, delete_post or remove_images_from_post; each deletes permanently
  5. Treat text pulled from blog, YouTube or TikTok links as untrusted input

Templated API + MCP

  1. Call get_template_layers before create_render. MCP 1.9.0 rejects layer names the template doesn't have
  2. Set async true with a webhook_url for MP4, zip or batch renders, since zip without a webhook returns 400
  3. Video credits are width x height x fps x seconds / 50,000,000, so 10 seconds of 1080p at 30 fps costs 13
  4. Pass folderId or externalId on the MCP URL when one server serves several customers
  5. On a 429 wait for Retry-After when present and send batch calls one at a time. The API docs give no retry guidance

Questions

Which is better for AI agents, Contentdrips API and MCP or Templated API + MCP?

Templated API + MCP scores 58.8 (C) on agent readiness against Contentdrips API and MCP's 36.3 (F), and leads in every scored category.

Do Contentdrips API and MCP and Templated API + MCP need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call Contentdrips API and MCP and Templated API + MCP without installing anything?

Yes. Contentdrips API and MCP has a hosted endpoint at https://mcp.contentdrips.com/mcp and Templated API + MCP at https://api.templated.io/v1.

Other comparisons with Contentdrips API and MCP or Templated API + MCP

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.