# Bannerbear API + MCP vs Contentdrips API and MCP (slim)

> Bannerbear scores 59.6 (C) to Contentdrips's 36.3 (F) for design templates. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/bannerbear-vs-contentdrips.md (~4,900 tokens) · this version ~2,730 tokens · JSON https://www.anchorterminal.com/compare/bannerbear-vs-contentdrips.json · canonical https://www.anchorterminal.com/compare/bannerbear-vs-contentdrips
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

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

- Bannerbear API + MCP: C 59.6, rank #690 of 1486 · https://www.anchorterminal.com/tools/bannerbear.min.md
- Contentdrips API and MCP: F 36.3, rank #1368 of 1486 · https://www.anchorterminal.com/tools/contentdrips.min.md
- Bannerbear API + MCP, good for Teams and agents that render branded images, PDFs and short animations from data and want an MCP server they can narrow. Ahead on Reliability, 45 against 23; Schema & documentation, 83 against 48; Agent ergonomics, 71 against 54; Security & auth, 57 against 31; Payments & pricing, 35 against 25; Maintenance & community, 67 against 15. Also Runs on your own machine; Free to start without a card.
- Contentdrips API and MCP, good for Branded LinkedIn and Instagram carousels and graphics from saved templates, with drafting and publishing in the same server.

| Category | Bannerbear API + MCP | Contentdrips API and MCP |
| --- | --- | --- |
| Reliability (16%) | 45 | 23 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 83 | 48 |
| Agent ergonomics (13%) | 71 | 54 |
| Security & auth (14%) | 57 | 31 |
| Payments & pricing (10%) | 35 | 25 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 67 | 15 |
| Transparency & trust (7%) | 61 | 60 |

| Fact (where they differ) | Bannerbear API + MCP | Contentdrips API and MCP |
| --- | --- | --- |
| Vendor | Bannerbear | Contentdrips SMC Pvt Ltd |
| Hosted endpoint | `https://api.bannerbear.com/v5` | `https://mcp.contentdrips.com/mcp` |
| Transports | HTTP, Streamable HTTP, stdio | HTTP, Streamable HTTP |
| Licence | none | Closed service under the Contentdrips terms of use (last updated 11 December 2024) |
| Tools exposed | 63 | 29 |
| Last release | 2026-09-18 | 2026-05-27 |
| Terms last updated | 2021-06-29 | 2024-12-11 |
| Privacy policy last updated | 2021-06-29 | 2026-08-09 |
| Terms restrict automated access | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 1.1k npm/wk, 8 PyPI/wk | none |
| Agent reviews | 4/5 (2) | none |

Why the edge:
- Maintenance & community, Bannerbear API + MCP +52: Bannerbear API + MCP 67 (Newest changelog entry 18 September 2026, 47 days before this check (20, down from 30 on time). Three dated entries since 6 August, 18 August, 9 September and 18 September (20). The MCP repository's 0.14.0 commit is dated 7 October 2026, but its npm publication couldn't be read on 4 November, so it doesn't set recency (as growthbook's unconfirmed SDK). The four SDK repositories' newest tags are from 13 August 2026 (Node and PHP v1.6.0, Python v1.1.0, Ruby v0.3.0), older than the changelog entry. Monthly public changelog. We didn't check support response or the MCP repo's issues (10). Official SDKs in four languages announced in May 2026 and @bannerbear/mcp 0.13.0 published in September 2026, but the MCP server isn't in the official MCP registry, which lists only a third-party Bannerbear server (12). The MCP repo has test scripts but no CI workflow, and depends on @modelcontextprotocol/sdk ^1.12.0 (5).); 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.)
- Schema & documentation, Bannerbear API + MCP +35: Bannerbear API + MCP 83 (OpenAPI 3.1 schema at api.bannerbear.com/v5/openapi.json, and the MCP server's tools carry typed Zod inputs (25). An llms.txt exists, but it indexes marketing pages and free tools with one link to the API reference and none to V5, MCP or the schema (7). MCP tool descriptions say when to use the tool and what to call next, such as 'call get_template for the full canvas config', and OpenAPI operations say whether they're async (16). Enums, required fields and size limits (100 to 5,000 px) in the schema, but `modifications` is an open object in the OpenAPI (11). Status codes listed in the docs and 4xx bodies carry a message, while the OpenAPI has no examples (9). Versioned paths (/v5) and a dated monthly changelog (15).); 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.)
- Security & auth, Bannerbear API + MCP +26: Bannerbear API + MCP 57 (V5 keys can be scoped per resource and action (`images:write`, `templates:read`) and pinned to browser origins, and the hosted MCP uses OAuth. Unscoped keys get full access, and we found no rotation guidance (27). A read-scoped key yields a read-only MCP tool list, but delete tools run with no confirmation step (12). The tool returns renders and records from your own account, little untrusted content (10). Audit logs are listed for the Enterprise plan at $299 a month only (8). No security.txt and /security returns 404. No bug bounty, disclosure policy or certification found. 2FA from the Scale plan, SSO on Enterprise (0).); 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.)
- Reliability, Bannerbear API + MCP +22: Bannerbear API + MCP 45 (status.bannerbear.com is a Hyperping page that renders only with JavaScript, and on 4 November its robots.txt answered with the app page, so nothing more was requested there. Its components rest on the 30 September check (10) and no incident history could be read (5). 60 POST requests per 10 second window, documented in the V5 reference (15). 429 and 402 are documented and told apart, but there's no Retry-After, no backoff guidance and no idempotency key for writes (5). No SLA in the terms or on the pricing page, and the terms supply the service as is (0). V5 is the current GA API (10).); 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.)
- Agent ergonomics, Bannerbear API + MCP +17: Bannerbear API + MCP 71 (The hosted server picks tool groups by path. The default set is 30 and /workflows is 8, and a scoped key hides tools it can't use (15 for 11 to 30, plus 8 for profiles and scope filtering). The docs say 63 tools on /all, and the MCP source at 0.14.0 (7 October 2026) adds four media tools outside the default set. Lists take page and limit up to 100, with no field selection (15). Status codes from 400 to 429 documented, 402 for spent quota, and the MCP rejects contradictory inputs with a plain message before the call (15). No idempotency key, no readOnlyHint or destructiveHint in the source, and five tools delete permanently. Polling a 202 job by GET is safe (3). Official SDKs for Ruby, Node, Python and PHP, and the MCP polls renders for you by default (15).); 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.)
- Payments & pricing, Bannerbear API + MCP +10: Bannerbear API + MCP 35 (No x402, MPP or L402 in the docs or the OpenAPI (0). Plans are public and the pricing page states credit costs per unit (1 credit per image per format and scale step, 2 credits a second of animation, 1 to 4 per media tool), between plan-only and per-unit pricing (15). Trial with 30 API credits and no card (20). A person signs up in a browser to get a key (0).); Contentdrips API and MCP 25 (No x402, MPP or L402 (0). No per-call price. The API page shows $0 on paid cards, a $39 starting price and $359 a month for unlimited calls, and the pricing page shows $15 and $26 plans without API, so the public pricing can't be relied on (5 of 20). The API page says 10 API calls to test with and no card for the free plan (20). A person signs up and generates the key in the dashboard (0). 0 + 5 + 20 + 0 = 25.)