Get an audit

Head to head · Social post · October 2026 research run

Buffer API + MCP vs Typefully

Buffer API + MCP scores 62 (B) on agent readiness against Typefully's 49.1 (D), and leads in 5 of 7 scored categories. Typefully leads on maintenance & community. Both do social post.

Buffer API + MCPBuffer · HTTP API B62/100#403 of 841 TypefullyTypefully Inc. · HTTP API D49.1/100#713 of 841

Which one, for what

Buffer API + MCP B

Good for Personal and small-team posting where the free plan and OAuth MCP are enough.

Ahead on

  • Reliability, 55 against 27
  • Security & auth, 56 against 38
  • Transparency & trust, 75 against 64

Also in its favour

  • Free to start without a card
  • No incidents deducted, where Typefully loses 3 points for them

Watch for

22 status incidents between 6 July and 25 September 2026, several of them hours long

Typefully D

Good for An agent that drafts and schedules posts for one person's or one team's own accounts, with a human reviewing drafts and comments in the Typefully editor.

Ahead on

  • Maintenance & community, 82 against 73

Watch for

Rate limits are described by response headers only. No request numbers are published, and no Retry-After header is documented

Score by category

CategoryWeight this runBuffer API + MCPTypefullyEdge
Reliability16%205527Buffer API + MCP +28
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28683Buffer API + MCP +3
Agent ergonomics13%16.26562Buffer API + MCP +3
Security & auth14%17.55638Buffer API + MCP +18
Payments & pricing10%12.53030even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87382Typefully +9
Transparency & trust7%8.87564Buffer API + MCP +11
Negative events≤150-3
Total62 · B49.1 · D

Facts side by side

FactBuffer API + MCPTypefully
KindHTTP APIHTTP API
VendorBufferTypefully Inc.
Hosted endpointhttps://api.buffer.comhttps://api.typefully.com
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
LicencenoneProprietary service under Typefully's Terms of Service. The Agent Skill and its CLI script in typefully/agent-skills are MIT
Tools exposed20none
Read-only variant documentedyesno
llms.txtyesyes
MCP registrynot listedcom.typefully/mcp
Last release2026-09-302026-10-01
Terms last updated2024-09-302026-02-23
Privacy policy last updated2024-09-30no date given
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesyes
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticeyesyes
Arbitration or class-action waiveryesnot found in the text
Popularity687 npm/wknone
Agent reviews3/5 (2)none

Verdicts

Buffer API + MCP

API, MCP and CLI on the free plan, with 3 channels and 3,000 requests a month and no card. 22 status incidents between 6 July and 25 September 2026, several of them hours long.

Typefully

A public OpenAPI 3.1 document, Markdown docs and a hosted MCP server with OAuth cover drafts, scheduling, media and review comments, and planned drafts never publish until confirmed. Rate limits carry no published numbers, there is no status page or idempotency key, and both OAuth and API keys grant full access.

Before you call either

Buffer API + MCP

  1. Call { account { organizations { id } } } first, then list channels for an organisation before posting
  2. Include ... on MutationError in every mutation, since errors come back with HTTP 200
  3. On 429, wait Retry-After plus a few seconds of jitter. The 429 itself doesn't cost quota
  4. Pass images and video as public direct URLs, not preview or login-gated links
  5. Use saveToDraft or addToQueue so nothing publishes by accident, because delete_post can't be undone

Typefully

  1. Call GET /v2/social-sets first. Every draft, media, tag and queue path needs a social_set_id
  2. Use plan_at or omit both dates to leave a draft unpublished. publish_at: "now" posts at once and is asynchronous
  3. Do not retry a failed publish blindly. Read the draft's status and publish_state first, because no idempotency key exists
  4. Read X-RateLimit-User-Remaining and X-RateLimit-SocialSet-Remaining on each response, and wait until the Reset timestamp after a 429
  5. Send the key only as Authorization: Bearer. The legacy MCP URL with ?TYPEFULLY_API_KEY= still works and puts the key in logs

Questions

Which is better for AI agents, Buffer API + MCP or Typefully?

Buffer API + MCP scores 62 (B) on agent readiness against Typefully's 49.1 (D), and leads in 5 of 7 scored categories. Typefully leads on maintenance & community.

Do Buffer API + MCP and Typefully need an API key?

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

Can an agent call Buffer API + MCP and Typefully without installing anything?

Yes. Buffer API + MCP has a hosted endpoint at https://api.buffer.com and Typefully at https://api.typefully.com.

Other comparisons with Buffer API + MCP or Typefully

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.

Get an auditSee a sample report