# Metricool API + MCP vs Repostit (slim)

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

- Full: https://www.anchorterminal.com/compare/metricool-vs-repostit.md (~4,950 tokens) · this version ~3,030 tokens · JSON https://www.anchorterminal.com/compare/metricool-vs-repostit.json · canonical https://www.anchorterminal.com/compare/metricool-vs-repostit
- 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-03
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Metricool API + MCP scores 38.4 (E) on agent readiness against Repostit's 32.5 (F), and leads in 5 of 7 scored categories. Repostit leads on maintenance & community. Both do social posting.

- Metricool API + MCP: E 38.4, rank #1160 of 1272 · https://www.anchorterminal.com/tools/metricool.min.md
- Repostit: F 32.5, rank #1191 of 1272 · https://www.anchorterminal.com/tools/repostit.min.md
- Metricool API + MCP, good for Reporting agents that read analytics and ad results, and for drafting posts for human review on a free account. Ahead on Reliability, 35 against 26; Schema & documentation, 56 against 27; Agent ergonomics, 39 against 25; Transparency & trust, 61 against 29.
- Repostit, 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. Ahead on Maintenance & community, 56 against 6. Also Free to start without a card.

| Category | Metricool API + MCP | Repostit |
| --- | --- | --- |
| Reliability (16%) | 35 | 26 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 56 | 27 |
| Agent ergonomics (13%) | 39 | 25 |
| Security & auth (14%) | 48 | 44 |
| Payments & pricing (10%) | 30 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 6 | 56 |
| Transparency & trust (7%) | 61 | 29 |

| Fact (where they differ) | Metricool API + MCP | Repostit |
| --- | --- | --- |
| Kind | HTTP API | Platform |
| Vendor | Metricool | Repostit LLC |
| Hosted endpoint | `https://app.metricool.com/api` | `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 |
| 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 |
| MCP registry | not listed | `io.github.hax98/repostit` |
| Last release | 2025-10-07 | 2026-10-23 |
| Terms last updated | no date given | not read yet |
| Privacy policy last updated | no date given | 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 | not found in the text | not read yet |
| Terms or service can change without notice | yes | not read yet |
| Arbitration or class-action waiver | not found in the text | not read yet |
| Popularity | 424 PyPI/wk | none |
| Agent reviews | 2.5/5 (2) | none |

Why the edge:
- Maintenance & community, Repostit +50: Metricool API + MCP 6 (No dated API or MCP change found. The PyPI server mcp-metricool is still at 1.1.9 from 7 October 2025 (0). No releases or dated changelog entries in the last 90 days (0). No public API changelog. The help centre's MCP pages were updated in late September 2026 and support exists (6). No official SDKs or registry entry (0). The GitHub repo the help centre names isn't public. The metricool organisation's only public repository is a fork of modelcontextprotocol/servers, last updated 13 May 2025 (0).); 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.)
- Transparency & trust, Metricool API + MCP +32: Metricool API + MCP 61 (Closed service with published terms from METRICOOL SOFTWARE, SL of Madrid, part of the team.blue group (15). Privacy policy says all data sits on EU servers, gives statutory retention periods of 4 to 6 years and folds a DPA into the service terms. A signed DPA is available on request from legal@metricool.com, with deletion or return of data when the contract ends. Processors are named only by category (22). No deprecation policy or dated notices found (0). Data location stated, subprocessors not named (10).); 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.)
- Schema & documentation, Metricool API + MCP +29: Metricool API + MCP 56 (OpenAPI 3.0 at app.metricool.com/api/swagger.json covering 553 paths, per the 30 September check. On 1 and 2 October app.metricool.com answered our reader's robots.txt request with an HTTP 500, so neither the spec nor the API docs page could be re-read (25). llms.txt on the help centre, re-read on 2 October (10). The help centre explains what the MCP can and can't do, and the MCP tools are closed source, so we didn't read their descriptions (8). Typed parameters per the spec, but every call also needs userId and blogId (8). The errors page documents two cases, access denied and posts scheduled without media (5). No API or MCP changelog. The only changelog in the help centre's llms.txt is for the Looker Studio connector (0).); 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.)
- Agent ergonomics, Metricool API + MCP +14: Metricool API + MCP 39 (The help centre's MCP basics page lists six hosted tools, four that read (metrics, analytics, best time, scheduled posts) and two that write (create and update a scheduled post). We couldn't read their definitions without an OAuth session, and the older PyPI package lists 28 (20). Analytics take date ranges. We didn't verify pagination or field selection (8). Two documented error cases, no codes an agent can act on (5). No idempotency or tool annotations found, though the MCP can submit a post for review instead of scheduling it (3). No SDKs, and three values per REST call (3).); 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.)
- Reliability, Metricool API + MCP +9: Metricool API + MCP 35 (A status page at status.metricool.com, per the 30 September check (20). Its robots.txt blocked our reader on 1 and 2 October, for the page, its history and the incident API, and the statuspage.io mirror too, so we have no readable history. That's our limit, not proof of a clean record. IsDown's Metricool page lists three entries since December 2025, all in June 2026, but shows no components and reads like user reports, so we don't treat it as a mirror (5). No rate limits published. The API guide, the errors page and the MCP limits page give plan caps (20 scheduled posts and 30 days of analytics on Free) but no request limits (0). No 429 or retry guidance found (0). No SLA found (0). The API and MCP aren't labelled beta (10).); 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.)