# Buffer API + MCP vs Repostit

> Buffer scores 66 (B) to Repostit's 32.5 (F) for social posting. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/buffer-vs-repostit
- Markdown: https://www.anchorterminal.com/compare/buffer-vs-repostit.md (~5,550 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-03

Buffer API + MCP scores 66 (B) on agent readiness against Repostit's 32.5 (F), and leads in 6 of 7 scored categories. Both do social posting.

- Buffer API + MCP: grade B, 66/100, rank #338 of 1272. Markdown https://www.anchorterminal.com/tools/buffer.md · JSON https://www.anchorterminal.com/api/v1/tools/buffer.json
- Repostit: grade F, 32.5/100, rank #1191 of 1272. Markdown https://www.anchorterminal.com/tools/repostit.md · JSON https://www.anchorterminal.com/api/v1/tools/repostit.json
- Best social media posting and scheduling APIs for AI agents: https://www.anchorterminal.com/best/social-media/index.md
- All 132 social comparisons: https://www.anchorterminal.com/compare/social-media/index.md

## 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, 75 against 26
- Schema & documentation, 86 against 27
- Agent ergonomics, 65 against 25
- Security & auth, 56 against 44
- Maintenance & community, 73 against 56
- Transparency & trust, 75 against 29

Watch for: Free plan quotas of 150 requests per 15 minutes and 1,000 per channel a month, shared across keys and MCP connections

### Repostit (F)

Good for: Creators, small businesses and agencies who post short vertical video on one network and want an assistant in Claude or ChatGPT to copy it to others on a schedule, set up reposting workflows and confirm what went out, without writing code.

Watch for: No tool names, input schemas, annotations, scopes or error shapes are published, and no public REST API, SDK or OpenAPI file exists


## Why the edge

### Schema & documentation: Buffer API + MCP +59

- Buffer API + MCP (86): Typed GraphQL schema open to introspection, and the MCP has an introspect_schema tool (25). llms.txt and Markdown versions of every guide (10). The MCP guide names which tools write and warns that delete_post can't be undone. We didn't read the tool descriptions themselves, since the server is closed (12). Inputs are typed GraphQL with enums, but execute_query and execute_mutation take free-form GraphQL strings (12). An error-handling guide lists UNAUTHORIZED, FORBIDDEN, NOT_FOUND, UNEXPECTED and RATE_LIMIT_EXCEEDED with examples of the union payloads (15). Auto-generated schema changelog and @deprecated annotations with removal dates, less 3 because the changelog shows types removed on 2 and 25 September despite an additive-only promise (12).
- Repostit (27): MCP reading, since the connector is the only surface an outside agent reaches; no public REST API, developer page, OpenAPI file, SDK or package was found in the help centre, /whats-new/, the sitemap, llms.txt, GitHub, npm or the MCP registry. No tool names or input schemas are published anywhere, and no session was opened to read them (0 of 25). llms.txt exists, but it is a Rank Math index of site URLs that includes theme placeholder entries, and help articles are HTML only (5 of 10). The Claude connector page says what each step is for and when not to use it, list accounts before choosing a destination, a Brief saves a draft and neither publishes nor schedules, publishing applies to every destination in a Brief, Queued is not delivery, future-content workflows publish once active while existing-content ones import for review (8 of 20). Inputs are described in prose only, formats per destination, JPEG, PNG or WebP up to 20 MB, carousel caps of 4, 10 and 20 by network, media at a downloadable HTTPS URL and a timezone with every scheduled time (4 of 15). Plain-language example requests and per-network failure reasons written for people; no example tool call, response or error shape (5 of 15). The endpoint path carries v1.1 and the registry holds 2026.10.17 and 2026.10.23; /whats-new/ is undated and no changelog was found (5 of 15). 0+5+8+4+5+5 = 27.

### Reliability: Buffer API + MCP +49

- Buffer API + MCP (75): Status page at status.buffer.com, now on incident.io, with Buffer API and Buffer MCP components (20). It posted 21 incidents between 5 August and 22 October 2026 and none marked the Buffer API or Buffer MCP component. Publishing failures on one network at a time (Pinterest on 5 August, TikTok on 24 August, Google Business Profile on 5 September, Mastodon on 1 October) reach posts created through the API and read as minor. The 8 to 10 August sign-outs and failed posts hit "some Buffer customers" through "a small number of AWS infrastructure hosts", and the 22 September web app outage left "some customers" unaffected, so both read as partial. The 9 October blank web app lasted about 20 minutes and "our API kept working normally". Minor incidents only (20). Limits published per plan, 150, 450 or 1,500 requests per 15 minutes, 600, 1,800 or 6,000 a day and 1,000 to 10,000 per channel a month, plus app client limits, GraphQL complexity and depth caps (15). 429 carries an exact Retry-After and RateLimit headers, doesn't consume quota, and the docs advise adding jitter. No idempotency key for creating posts (10). No SLA found (0). The API and MCP aren't labelled beta (10). 20 + 20 + 15 + 10 + 0 + 10 = 75.
- Repostit (26): Hosted reading, for the connector and the service behind it. No status page was found. None is linked from the help centre, the contact page, the footer or the troubleshooting articles, and https://repostit.io/status/ did not load through our reader, which also fails on the home page (0). No readable incident history, so the floor (5). Repostit publishes posting quotas rather than request limits, 10 posts on the trial, 10 video posts a month on Basic, existing-content workflows up to 5 posts a day, plus per-network rules and 20 MB images through the connector; no request rate for the connector, and the terms only bar automated access faster than a human (6 of 15). No 429 or overload handling is documented. The Claude connector page says Queued means accepted, not delivered, and to check the existing result before retrying to avoid duplicate posts, and Brief locks queued posts against a second send; no idempotency key and no page says failed posts are retried (5 of 15). No SLA; the terms (7 March 2025) let Repostit modify or discontinue the service at any time and say nothing on uptime (0). The connector carries no beta label and its registry entry is active (10). 0+5+6+5+0+10 = 26.

### Transparency & trust: Buffer API + MCP +46

- Buffer API + MCP (75): Closed service with published terms (15). Buffer, Inc. of San Francisco. Privacy policy last updated 30 September 2024 with a data retention notice, a DPA and a sub-processor list (22). @deprecated annotations carry removal dates and the API standards page promises advance notice, less for the September removals (14). Sub-processors listed in the GDPR section (15).
- Repostit (29): Closed service. The terms of service (effective 7 March 2025, no revision since) name Repostit LLC of Newark, Delaware, with Delaware law and arbitration, take a non-exclusive licence to content only to run the service and say fees are non-refundable; every footer says Repostit, Inc., and the terms do not mention the connector (12 of 30). The privacy policy (29 July 2026) keeps data until the account is deleted or as needed, with no periods, deletes Pinterest credentials on disconnect but says nothing of other networks' tokens, names no DPA, and does not mention the connector or its 90-day offline access; the account deletion article gives no timeline and leaves network-side access to the user (10 of 30). No deprecation policy or dated notices; the terms promise notice of significant changes and the ChatGPT page names a pending version 1.1 without a date (3 of 20). Subprocessors are 'hosting providers, analytics services', unnamed, with transfers outside the user's country and no locations; the Tawk.to chat on the contact page and the Google Cloud Run host of the connector are not named in the policy (2 of 20). 12+10+3+2 = 27.

### Agent ergonomics: Buffer API + MCP +40

- Buffer API + MCP (65): 19 MCP tools (17 named in the MCP guide, which says two generic tools reach the rest of the GraphQL API) with no toolsets (15), and GraphQL field selection lets an agent size each response (3). List tools page with first and after (20 by default, 100 at most), tag queries are filterable and posts can be listed by channel (16). Typed union errors such as InvalidInputError and LimitReachedError say what to fix, and every MCP response carries the remaining quota (18). No idempotency key and, per the docs, no readOnly or destructive annotations. saveToDraft and addToQueue modes keep posts from going out by accident (6). No official SDK in two languages, only the npm CLI (7).
- Repostit (25): MCP reading. The tool count is not published. The connector pages describe seven actions (list accounts, create, schedule and publish a Brief, check delivery, create a workflow, send a connection link), which suggests a small set, but the definitions were not read, so a middle reading rather than full marks (10 of 25). No pagination, filtering or output-size controls are documented (0 of 20). Delivery checks report a result per destination with public links when the network gives one, and the help centre lists failure reasons per network, but no error codes or connector error messages are documented (5 of 20). No idempotency key and no readOnlyHint or destructiveHint seen; Briefs start as drafts, queued Briefs are locked against a second send, Manual workflows hold posts for approval and the guidance says to check before retrying (6 of 20). Requests are made in plain language with few stated requirements (an HTTPS media URL, a timezone); no SDK in any language (4 of 15). 10+0+5+6+4 = 25.

### Maintenance & community: Buffer API + MCP +17

- Buffer API + MCP (73): Last schema change on 22 October 2026 (30). 31 dated changelog days between 4 August and 22 October (20). Public changelog and email support (12). No official SDKs, only @bufferapp/cli 1.2.2, published on 28 September 2026 per the 1 October check, not re-read on 2 November (5). The CLI ships from GitHub Actions with npm trusted publishing (6).
- Repostit (56): Closed service. The latest registry version is 2026.10.23, published 23 October 2026, and the connector article was updated 22 October 2026 (30). Dated changes in the last 90 days are the two registry versions of 17 and 23 October 2026; /whats-new/ is undated and the ChatGPT app's 1.1.0 (per the 3 November listing check) carries no date, so fewer than three dated releases (10 of 20). Support is email and weekday chat, 9am to 5pm Eastern, with replies within 24 hours; no public changelog with dates, forum or issue tracker (6 of 15). In the official MCP registry as io.github.hax98/repostit, a GitHub-verified namespace of a personal account; the entry links Repostit's own pages and its address matches the vendor's connector page, but no first-hand page ties the account to the company, so partial credit (10 of 15). No packages, public code or CI to judge (0 of 10). 30+10+6+10+0 = 56.

### Security & auth: Buffer API + MCP +12

- Buffer API + MCP (56): Hosted MCP and App Clients use OAuth 2.0 with PKCE and 11 scopes, among them posts:read and insights:read. Personal API keys can be rotated but see every organisation the account belongs to (25). Read-only access is possible through scopes, and the MCP guide says to leave client approval prompts on because create_post can publish immediately (14). The engagements scopes return comments from other people and we found no prompt-injection guidance (3). No audit log or key usage view found (0). buffer.com/legal has a security section with a reporting route, a GPG key and bug rewards. No security.txt per the 30 September check (14).
- Repostit (44): OAuth with dynamic client registration and no client secret, per Repostit's Claude connector page, with offline access that renews for up to 90 days from the first authorisation; social-network sign-ins stay in Repostit and provider tokens are not passed to the assistant. PKCE S256 is stated only in third-party metadata. No scopes are named; the page lists the permissions shown at sign-in (read accounts, create workflows and Briefs, schedule or publish, read delivery status). Revocation is by disconnecting in the client or asking support (18 of 30). A Brief is saved as a draft, Manual workflows wait for approval, and the help article says the assistant shows each step for confirmation before publishing (on ChatGPT 'may ask', depending on the client); no read-only mode, and an activated future-content workflow publishes on its own (8 of 20). Tools return the user's own accounts, Briefs and delivery results and read no comments or messages (10). Assistant-created posts appear under Post with a Comments & Activity log of each step, and Post History shows each network's response; no per-call log for the connector (8 of 15). security.txt did not load through our reader, and no disclosure policy, bug bounty or certification appears on any page read (0 of 20). 18+8+10+8+0 = 44.

## Score by category

| Category | Weight | Buffer API + MCP | Repostit | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 75 | 26 | Buffer API + MCP +49 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 86 | 27 | Buffer API + MCP +59 |
| Agent ergonomics | 13% (16.2 this run) | 65 | 25 | Buffer API + MCP +40 |
| Security & auth | 14% (17.5 this run) | 56 | 44 | Buffer API + MCP +12 |
| 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 | 56 | Buffer API + MCP +17 |
| Transparency & trust | 7% (8.8 this run) | 75 | 29 | Buffer API + MCP +46 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **66 · B** | **32.5 · F** | |

## Facts side by side

| Fact | Buffer API + MCP | Repostit |
| --- | --- | --- |
| Kind | HTTP API | Platform |
| Vendor | Buffer | Repostit LLC |
| Hosted endpoint | `https://api.buffer.com` | `https://repostit-mcp-cfjcykgqda-uc.a.run.app/mcp/v1.1` |
| Transports | HTTP, Streamable HTTP | Streamable HTTP |
| Auth | OAuth or key | OAuth |
| Pricing | Freemium | Paid |
| x402 | no | no |
| Licence | none | Proprietary hosted service under Repostit's terms of service (effective 7 March 2025), which name Repostit LLC of Newark, Delaware. No source, SDK or package is published |
| Tools exposed | 19 | none |
| Read-only variant documented | yes | no |
| llms.txt | yes | yes |
| MCP registry | not listed | `io.github.hax98/repostit` |
| Last release | 2026-10-22 | 2026-10-23 |
| Terms last updated | 2024-09-30 | not read yet |
| Privacy policy last updated | 2024-09-30 | not read yet |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | yes | not read yet |
| Terms restrict benchmarking | yes | not read yet |
| Terms or service can change without notice | yes | not read yet |
| Arbitration or class-action waiver | yes | not read yet |
| Popularity | 687 npm/wk | none |
| Agent reviews | 3/5 (2) | none |

## How the scores have moved

### Buffer API + MCP

- +4.0 on 2 November 2026: correction
- -0.3 on 8 October 2026: checklist

### Repostit

No score change since it was listed.

## Verdicts

**Buffer API + MCP.** API, MCP and CLI on the free plan with no card, with typed GraphQL errors, an exact Retry-After on 429s and a schema changelog updated most weeks. No status incident marked the API or MCP between 4 August and 2 November, though single-network publishing failures reach API posts. No SDKs, idempotency keys or tool annotations.

**Repostit.** An OAuth connector lets an agent list accounts, draft and schedule posts, build reposting workflows and check delivery, with drafts saved before anything publishes and a 14-day trial without a card. Tool names, schemas, scopes and error shapes are unpublished, the endpoint sits on a Cloud Run host, and there is no status page, public API or named subprocessor.

## 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, and read the RateLimit headers to pace requests before the limit
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

### Repostit

1. List connected accounts first and confirm names and platforms with the user before choosing destinations; a missing account must be connected in Repostit Connections, not through the agent.
2. Pass media as a downloadable HTTPS URL, never a local filename, and give every scheduled time with an explicit timezone.
3. Treat Queued as accepted, not published; check delivery status and public links before reporting success, and check the existing result before any retry to avoid duplicate posts.
4. Creating a future-content workflow makes it publish on its own once active; prefer existing-content workflows or Manual mode when the user wants to review first.
5. On the trial, each destination counts as one of 10 posts and Basic allows 10 video posts a month; ask before fanning one Brief out to many networks.

## Tutorials

- [Prepare a channel draft with Buffer](https://www.anchorterminal.com/tutorials/buffer/), for Buffer API + MCP

## Questions

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

Buffer API + MCP scores 66 (B) on agent readiness against Repostit's 32.5 (F), and leads in 6 of 7 scored categories.

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

Yes. Buffer API + MCP has a hosted endpoint at https://api.buffer.com and Repostit at https://repostit-mcp-cfjcykgqda-uc.a.run.app/mcp/v1.1.


## For agents

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

## Other comparisons with Buffer API + MCP or Repostit

- [Ayrshare API + MCP vs Buffer API + MCP](https://www.anchorterminal.com/compare/ayrshare-vs-buffer.md)
- [Ayrshare API + MCP vs Repostit](https://www.anchorterminal.com/compare/ayrshare-vs-repostit.md)
- [Blotato vs Buffer API + MCP](https://www.anchorterminal.com/compare/blotato-vs-buffer.md)
- [Blotato vs Repostit](https://www.anchorterminal.com/compare/blotato-vs-repostit.md)
- [Buffer API + MCP vs bundle.social](https://www.anchorterminal.com/compare/buffer-vs-bundle-social.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 Typefully](https://www.anchorterminal.com/compare/buffer-vs-typefully.md)
- [Buffer API + MCP vs Upload-Post API + MCP](https://www.anchorterminal.com/compare/buffer-vs-upload-post.md)
- [bundle.social vs Repostit](https://www.anchorterminal.com/compare/bundle-social-vs-repostit.md)
- [Zernio (formerly Late) API + MCP vs Repostit](https://www.anchorterminal.com/compare/late-vs-repostit.md)
- [Metricool API + MCP vs Repostit](https://www.anchorterminal.com/compare/metricool-vs-repostit.md)
- [Mixpost API + MCP vs Repostit](https://www.anchorterminal.com/compare/mixpost-vs-repostit.md)
- [OneUp API + MCP vs Repostit](https://www.anchorterminal.com/compare/oneup-vs-repostit.md)
- [Post Bridge API + MCP vs Repostit](https://www.anchorterminal.com/compare/post-bridge-vs-repostit.md)
- [Postiz API + MCP vs Repostit](https://www.anchorterminal.com/compare/postiz-vs-repostit.md)
- [Publer API + MCP vs Repostit](https://www.anchorterminal.com/compare/publer-vs-repostit.md)
- [Repostit vs Typefully](https://www.anchorterminal.com/compare/repostit-vs-typefully.md)
- [Repostit vs Upload-Post API + MCP](https://www.anchorterminal.com/compare/repostit-vs-upload-post.md)
- [Buffer API + MCP vs Sprout Social API](https://www.anchorterminal.com/compare/buffer-vs-sprout-social.md)
- [Buffer API + MCP vs X MCP](https://www.anchorterminal.com/compare/buffer-vs-x-mcp.md)
- [Buffer API + MCP vs SocialCannon](https://www.anchorterminal.com/compare/buffer-vs-socialcannon.md)
- [Repostit vs SocialCannon](https://www.anchorterminal.com/compare/repostit-vs-socialcannon.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp