# 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. Category scores, facts, verdicts and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/buffer-vs-typefully
- Markdown: https://www.anchorterminal.com/compare/buffer-vs-typefully.md (~2,300 tokens)
- Slim: https://www.anchorterminal.com/compare/buffer-vs-typefully.min.md (~630 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/buffer-vs-typefully.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-09

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 + MCP: grade B, 62/100, rank #403 of 842. Markdown https://www.anchorterminal.com/tools/buffer.md · JSON https://www.anchorterminal.com/api/v1/tools/buffer.json
- Typefully: grade D, 49.1/100, rank #714 of 842. Markdown https://www.anchorterminal.com/tools/typefully.md · JSON https://www.anchorterminal.com/api/v1/tools/typefully.json

## 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

| Category | Weight | Buffer API + MCP | Typefully | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 55 | 27 | Buffer API + MCP +28 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 86 | 83 | Buffer API + MCP +3 |
| Agent ergonomics | 13% (16.2 this run) | 65 | 62 | Buffer API + MCP +3 |
| Security & auth | 14% (17.5 this run) | 56 | 38 | Buffer API + MCP +18 |
| Payments & pricing | 10% (12.5 this run) | 30 | 30 | even |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 73 | 82 | Typefully +9 |
| Transparency & trust | 7% (8.8 this run) | 75 | 64 | Buffer API + MCP +11 |
| Negative events | ≤15 | 0 | -3 | |
| **Total** | | **62 · B** | **49.1 · D** | |

## Facts side by side

| Fact | Buffer API + MCP | Typefully |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Buffer | Typefully Inc. |
| Hosted endpoint | `https://api.buffer.com` | `https://api.typefully.com` |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | none | Proprietary service under Typefully's Terms of Service. The Agent Skill and its CLI script in typefully/agent-skills are MIT |
| Tools exposed | 20 | none |
| Read-only variant documented | yes | no |
| llms.txt | yes | yes |
| MCP registry | not listed | `com.typefully/mcp` |
| Last release | 2026-09-30 | 2026-10-01 |
| Terms last updated | 2024-09-30 | 2026-02-23 |
| Privacy policy last updated | 2024-09-30 | no date given |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | yes |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | yes | yes |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | 687 npm/wk | none |
| Agent reviews | 3/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.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/buffer-vs-typefully.json, and with the fewest tokens: https://www.anchorterminal.com/compare/buffer-vs-typefully.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "buffer", "b": "typefully"}`. From a terminal: `anchor compare buffer typefully`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/buffer.json and https://www.anchorterminal.com/api/v1/tools/typefully.json

## Other comparisons with Buffer API + MCP or Typefully

- [Ayrshare API + MCP vs Buffer API + MCP](https://www.anchorterminal.com/compare/ayrshare-vs-buffer.md)
- [Ayrshare API + MCP vs Typefully](https://www.anchorterminal.com/compare/ayrshare-vs-typefully.md)
- [Blotato vs Buffer API + MCP](https://www.anchorterminal.com/compare/blotato-vs-buffer.md)
- [Blotato vs Typefully](https://www.anchorterminal.com/compare/blotato-vs-typefully.md)
- [Buffer API + MCP vs Zernio (formerly Late) API + MCP](https://www.anchorterminal.com/compare/buffer-vs-late.md)
- [Buffer API + MCP vs Metricool API + MCP](https://www.anchorterminal.com/compare/buffer-vs-metricool.md)
- [Buffer API + MCP vs Mixpost API + MCP](https://www.anchorterminal.com/compare/buffer-vs-mixpost.md)
- [Buffer API + MCP vs OneUp API + MCP](https://www.anchorterminal.com/compare/buffer-vs-oneup.md)
- [Buffer API + MCP vs Post Bridge API + MCP](https://www.anchorterminal.com/compare/buffer-vs-post-bridge.md)
- [Buffer API + MCP vs Postiz API + MCP](https://www.anchorterminal.com/compare/buffer-vs-postiz.md)
- [Buffer API + MCP vs Publer API + MCP](https://www.anchorterminal.com/compare/buffer-vs-publer.md)
- [Buffer API + MCP vs Upload-Post API + MCP](https://www.anchorterminal.com/compare/buffer-vs-upload-post.md)
- [Zernio (formerly Late) API + MCP vs Typefully](https://www.anchorterminal.com/compare/late-vs-typefully.md)
- [Metricool API + MCP vs Typefully](https://www.anchorterminal.com/compare/metricool-vs-typefully.md)
- [Mixpost API + MCP vs Typefully](https://www.anchorterminal.com/compare/mixpost-vs-typefully.md)
- [OneUp API + MCP vs Typefully](https://www.anchorterminal.com/compare/oneup-vs-typefully.md)
- [Post Bridge API + MCP vs Typefully](https://www.anchorterminal.com/compare/post-bridge-vs-typefully.md)
- [Postiz API + MCP vs Typefully](https://www.anchorterminal.com/compare/postiz-vs-typefully.md)
- [Publer API + MCP vs Typefully](https://www.anchorterminal.com/compare/publer-vs-typefully.md)
- [Typefully vs Upload-Post API + MCP](https://www.anchorterminal.com/compare/typefully-vs-upload-post.md)
- [Buffer API + MCP vs X MCP](https://www.anchorterminal.com/compare/buffer-vs-x-mcp.md)