Skip to main content
Both MCP servers share the same core tools. Upload differs. There is no web_search_duckduckgo tool (Claude/ChatGPT/Cursor already search).

Accounts

Platforms for connect: linkedin, instagram, facebook, tiktok, youtube, pinterest, threads, bluesky, snapchat

Posts

Media before publish

For image / video / document posts: call upload_media first so files land in Postsiva storage, then pass media_id / public_url into publish.

publish highlights

  • Web MCP: opens a live preview (caption + image/video/document). User toggles Facebook Pages, LinkedIn personal + orgs, and other connected accounts by name, then Post / Schedule / Draft / Reject. Writing happens only after confirm (complete_publish is app-only).
  • CLI MCP: same JSON tool as before (draft, scheduled_time, overrides).
  • scope: feed (personal) or pages (Facebook Pages / LinkedIn orgs) — CLI / backend mapping
  • Media: default_image_id, default_image_url, video_id, video_url, document_id, document_url

Upload

Web hosts may keep an internal app-only completion helper for the iframe; it is not shown to the model.

Inbox

Analytics

AI content

None of the AI tools publish automatically — chain with publish if needed. On web MCP, content_to_image and analyze_media open an in-chat MCP App while the tool runs.

REST equivalents

GPT Actions

Custom GPT Actions are a separate OpenAPI surface (/unified/gpt-actions/*), not these MCP URLs. See ChatGPT.