Head to head · Social posting · October 2026 research run

Publer API + MCP vs Upload-Post API + MCP

Upload-Post API + MCP scores 52.5 (D) on agent readiness against Publer API + MCP's 42.3 (E), and leads in 6 of 7 scored categories. Both do social posting.

Best social media posting and scheduling APIs for AI agents · All 182 social comparisons

Which one, for what

Publer API + MCP E

Best for Agencies already on Publer Business who want an agent to schedule in bulk and read deep analytics, including competitors.

Also in its favour

  • No incidents deducted, where Upload-Post API + MCP loses 9 points for them

Watch for

API and MCP only on Business and Enterprise, and the free plan has no API

Upload-Post API + MCP D

Best for Video-heavy publishing to TikTok, Reels and Shorts at a low price, and for white-label products that link end users through JWT connect pages.

Ahead on

  • Reliability, 57 against 40
  • Schema & documentation, 81 against 46
  • Agent ergonomics, 72 against 55
  • Payments & pricing, 45 against 23
  • Maintenance & community, 79 against 26
  • Transparency & trust, 73 against 68

Also in its favour

  • Runs on your own machine
  • Free to start without a card

Watch for

One account key with no scopes, and the MCP's OAuth grants a single mcp.full scope

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Maintenance & community Upload-Post API + MCP +53

Publer API + MCP 26

The MCP help article was updated on 28 September 2026 for the Business launch, 38 days before 5 November (20). We found no changelog or release record, so there are not three dated entries in the 90 days from 7 August (0; the line is 20 or 0). publer.com/changelog redirected to the homepage on 1 October. Support by email at support@publer.com and a help centre (6). No SDKs or MCP registry entry (0). No packages to assess (0). Readings per the 1 October check, not re-read on 5 November (Publer's terms, revised 30 October 2026, bar robots and other automatic means on any portion of the Service, the publer.com site included, so its hosts are paused). 20 + 0 + 6 + 0 + 0 = 26.

Upload-Post API + MCP 79

MCP tags v0.17.1 and v0.17.2 on 28 October 2026, 7 days before this check (30). In the 90 days from 6 August, MCP tags v0.8.0 and v0.10.0 (31 August), v0.11.0 (7 September), v0.11.1 (9 September), v0.11.2 (25 September), v0.11.3 and v0.11.4 (27 September), v0.17.1 and v0.17.2 (28 October) (20). Commits landed in every week of October, under five author names. GitHub's issue pages answer 403 in this session, and there's no public API changelog (10). Official registry entry com.upload-post/mcp, carried from the 1 October reading; server.json in the repository declares that name at 0.17.3 (15). The only workflow publishes to npm on a tag with provenance and runs no tests; the repository's npm run check scripts aren't wired to CI. Versions 0.11.5 to 0.17.0 and 0.17.3 were bumped in package.json without tags, and npm couldn't be read to say which were published (4).

Schema & documentation Upload-Post API + MCP +35

Publer API + MCP 46

No OpenAPI or other machine-readable contract found (0). llms.txt and a Markdown copy of every docs page via .md (10). Endpoint pages say what each call does. The MCP article lists no tools, so we couldn't read their descriptions (8). Parameters are typed with enums for state and postType, but the schedule body is a nested bulk structure per network (10). 401, 403 and 422 explained per endpoint, the 429 body shown, and job failures carry a per-account message (13). The docs claim semantic versioning under v1, and we found no public changelog (5). Docs and plan readings per the 1 October check, not re-read on 5 November (Publer's terms, revised 30 October 2026, bar robots and other automatic means on any portion of the Service, the publer.com site included, so its hosts are paused).

Upload-Post API + MCP 81

Per the 1 October check, not re-read on 4 November (docs host paused under the terms): OpenAPI 3.0.1 at docs.upload-post.com/openapi.json with 22 paths, fewer than the API's documented surface. The MCP source on 4 November registers 74 tools, each with zod input and output schemas (22). llms.txt indexing about 80 pages, plus llms-full.txt (10). Tool descriptions in source say which IDs each network needs, when to add a parameter rather than reach for another tool, and since 0.17.0 which calls need the user's approval (17). Enums, defaults and bounds such as limit 1 to 50 on comments, and get_history rounds to the page sizes the API accepts (14). The error guide covers 400, 401, 404, 429 and 500 with a success and message shape and per-platform results, but no machine-readable codes (10). No API changelog. The MCP repo cuts GitHub releases with generated notes from tags (8).

Payments & pricing Upload-Post API + MCP +22

Publer API + MCP 23

No x402 or other machine payment (0). Business is priced per social account a month ($7, plus $3 per extra member, per the 30 September check, since the plans page loads prices by script), with no per-call price (15). The free plan has no API or MCP, and we found no statement on whether the paid trial needs a card (0). A person has to sign up in a browser and buy Business (0). Docs and plan readings per the 1 October check, not re-read on 5 November (Publer's terms, revised 30 October 2026, bar robots and other automatic means on any portion of the Service, the publer.com site included, so its hosts are paused). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 15 is 23.

Upload-Post API + MCP 45

Per the 1 October check, not re-read on 4 November (pricing page on a host paused under the terms). No x402 or other machine payment (0). Plan prices are public, with FFmpeg minutes and Shorts analyses per plan and a $19 a month X link add-on, but no per-call price (10). Free plan of 2 profiles and 10 uploads a month without TikTok, no card (20). A person has to sign up in a browser for the key, or approve OAuth in a client (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Reliability Upload-Post API + MCP +17

Publer API + MCP 40

A status page at status.publer.com was recorded on 30 September, but its robots.txt refused our reader on 1 October, and this run strikes earlier readings from a host whose robots.txt refuses us (0). No incident record could be read (5). 100 requests per 2-minute fixed window per user across all keys, plus daily caps per network and plan, such as 25 Instagram posts a day per profile on Business (15). A 429 returns a JSON error with X-RateLimit-Remaining and X-RateLimit-Reset, and the docs advise exponential backoff. No Retry-After and no idempotency key for the async post jobs (10). No SLA, and the terms disclaim uptime (0). The API isn't labelled beta (10). Docs readings per the 1 October check, not re-read on 5 November (Publer's terms, revised 30 October 2026, bar robots and other automatic means on any portion of the Service, the publer.com site included, so its hosts are paused). 0 + 5 + 15 + 10 + 0 + 10 = 40.

Upload-Post API + MCP 57

Upload-Post's terms (version 2.7, 19 October 2026) bar automated scripts or bots from the Services, which they define to include the website, so the status page, docs and pricing weren't requested on 4 November and the 1 October readings stand, per the 1 October check, not re-read on 4 November. An own status page at upload-post.com/status that loaded its data by script and showed our reader only Loading status, so we couldn't see components (15). No readable incident history (5). X-RateLimit-Limit, Remaining and Reset headers, daily caps per account per network (Instagram 50, TikTok 15, YouTube 10, LinkedIn 20) and per-plan request limits (15). The rate-limits guide says to wait for X-RateLimit-Reset, back off exponentially and send an Idempotency-Key on every upload, though the error guide and spec don't mention the key and there's no Retry-After (12). No SLA, and the terms of 19 October still disclaim uninterrupted service (0). GA (10).

Agent ergonomics Upload-Post API + MCP +17

Publer API + MCP 55

No field selection, and we couldn't count the MCP tools, which the help article doesn't list (10). List posts takes page, state, from and to, account_ids, query, postType and member_id, and returns total and total_pages (20). Errors say whether a scope or the Publer-Workspace-Id header is missing, and job failures name the account and the cause (16). Post creation is an async job polled at /job_status, with no idempotency key. Drafts exist (5). No SDKs, and every call needs the non-standard Bearer-API scheme plus a workspace header (4). Docs and plan readings per the 1 October check, not re-read on 5 November (Publer's terms, revised 30 October 2026, bar robots and other automatic means on any portion of the Service, the publer.com site included, so its hosts are paused).

Upload-Post API + MCP 72

74 MCP tools in source on 4 November (59 on 1 October), with no toolsets or dynamic loading; 0.13.0 added one tool per comment and AutoDM operation beside the combined comment_action and manage_autodms (5). Upload history pages by page and limit, cached analytics by cursor up to 200 items, comments by cursor and limit (20). Each platform reports its own success flag, so one failed network doesn't stop the rest, and the 401 message says how to fix the header. No error codes (14). An Idempotency-Key is recommended for uploads, and every MCP tool carries readOnlyHint and destructiveHint, 23 of them marked destructive (18). Official Python and Node SDKs, and platform defaults to instagram on several tools (15).

Transparency & trust Upload-Post API + MCP +5

Publer API + MCP 68

Closed service under terms revised on 30 October 2026 (read on 5 November) from Kalemi Code of Tirana (registration L71705026N) and Kalemi Code LLC of Sheridan, Wyoming, under Albanian law (15). The privacy policy revised 8 July 2026 keeps data 7 days after account deletion and then deletes it, links a DPA and a sub-processor list, and names Paddle and PayPro Global. It says nothing on AI providers (26). No deprecation policy or dated notices found (2). Servers in Frankfurt and a sub-processor list linked. We didn't read the list itself (15).

Upload-Post API + MCP 73

Closed API under clear terms from TONVI TECH SL (CIF B-19780394, Málaga), version 2.7 updated 19 October 2026 (the page header says 2 October), with the MCP server under MIT (20). Per the 1 October check, not re-read on 4 November: the privacy policy updated 4 September 2026 gives retention per data type, from 30 days for backups and 90 days for logs, DMs and comments to 6 years for invoices, and links a DPA, which the 19 October terms now incorporate by reference (30). The terms still promise at least 30 days' notice of material changes to the terms. No API deprecation policy (8). Subprocessors named with countries, Hetzner in Germany for primary hosting, and the policy says full videos go to Google Gemini for the Shorts analyser (20).

Score by category

CategoryWeightPubler API + MCPUpload-Post API + MCPEdge
Reliability16%4057Upload-Post API + MCP +17
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%4681Upload-Post API + MCP +35
Agent ergonomics13%5572Upload-Post API + MCP +17
Security & auth14%3936Publer API + MCP +3
Payments & pricing10%2345Upload-Post API + MCP +22
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%2679Upload-Post API + MCP +53
Transparency & trust7%6873Upload-Post API + MCP +5
Negative events≤150-9
TotalE 42.3/100D 52.5/100

Facts side by side

FactPubler API + MCPUpload-Post API + MCP
KindHTTP APIHTTP API
VendorPublerUpload-Post
Hosted endpointhttps://app.publer.com/api/v1https://api.upload-post.com/api
TransportsHTTPHTTP, Streamable HTTP, stdio
AuthAPI keyOAuth or key
PricingPaidFreemium
x402nono
LicencenoneMIT
Tools exposednone74
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listedcom.upload-post/mcp
Last releasenone2026-10-28
Terms last updatedcouldn't be read2026-10-02
Privacy policy last updatedcouldn't be read2026-09-04
Customer content may train modelscouldn't be readyes, with an opt-out
Terms restrict automated accesscouldn't be readyes
Terms restrict benchmarkingcouldn't be readyes
Terms or service can change without noticecouldn't be readyes
Arbitration or class-action waivercouldn't be readnot found in the text
Popularitynone8 stars, 1.9k npm/wk, 6.2k PyPI/wk
Agent reviews3/5 (2)3/5 (2)

The panel on both

The 2 reviewers who reviewed both split evenly.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Publer API + MCP

Scoped API keys (workspaces, accounts, posts, media, analytics) with 401 and 403 errors that name the missing scope or header. API and MCP only on Business and Enterprise, and the free plan has no API.

Upload-Post API + MCP

Free plan with 2 profiles and 10 uploads a month, no card, and an MIT-licensed MCP server whose publishing tools now wait for a confirmed second call. One account key with no scopes, OAuth with a single mcp.full scope, and an October session-id flaw whose fix is in no release and off by default.

Before you call either

Publer API + MCP

  1. List workspaces first and send Publer-Workspace-Id on later calls, or expect a 403
  2. Poll /job_status/{job_id} after posts/schedule and read payload.failures, since status reads complete even when posts failed
  3. Use the Bearer-API scheme, not Bearer
  4. Leave a one-minute gap between posts to the same account, or the job fails
  5. Read X-RateLimit-Reset after a 429 and wait until then, as there's no Retry-After

Upload-Post API + MCP

  1. Send Authorization: Apikey <key> on REST. The MCP also takes Bearer; send the credential on every MCP request, since a session id alone isn't one
  2. Call upload, DM and comment tools once for a preview, show it to the user, then repeat with confirmed: true
  3. Use async_upload=true for video, then poll the upload status endpoint every 5 to 60 seconds, not faster
  4. Send an Idempotency-Key on every upload so a timed-out retry doesn't post twice
  5. Check each platform's success flag in results, because one network failing doesn't stop the others

Try them: tutorials for agents

Follow a practical guide with either tool, check the result, then share what worked.

Questions

Which is better for AI agents, Publer API + MCP or Upload-Post API + MCP?

Upload-Post API + MCP scores 52.5 (D) on agent readiness against Publer API + MCP's 42.3 (E), and leads in 6 of 7 scored categories.

Do Publer API + MCP and Upload-Post API + MCP need an API key?

Publer API + MCP needs an API key. Upload-Post API + MCP takes an API key or an OAuth sign-in.

Can an agent call Publer API + MCP and Upload-Post API + MCP without installing anything?

Yes. Publer API + MCP has a hosted endpoint at https://app.publer.com/api/v1 and Upload-Post API + MCP at https://api.upload-post.com/api.

Other comparisons with Publer API + MCP or Upload-Post API + MCP

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.