Upload Post

What Upload-Post MCP server does

Upload-Post MCP server gives an MCP client access to Upload-Post’s social publishing and analytics API. It can publish videos, photos, carousels, text posts, and LinkedIn documents to one or more connected profiles. Supported destinations include TikTok, Instagram, YouTube, LinkedIn, Facebook, X, Threads, Pinterest, Bluesky, and others exposed by the connected Upload-Post account.

The server also supports scheduled publishing, upload history, media browsing, account and profile administration, and social performance analysis. TikTok-specific helpers can find commercial music tracks or locations for use with video publishing. Facebook pages, LinkedIn pages, and Pinterest boards can be enumerated before selecting a destination.

How it works

Publishing calls return an asynchronous identifier rather than waiting for the platform operation to finish. Use get_status with the returned request_id until the operation succeeds or fails. Posts created with a schedule or queue use get_job_status and can be listed, edited, or cancelled through the scheduling tools.

Analytics can be requested at profile level, for total impressions, or for an individual post. get_cached_post_analytics reads metrics previously fetched live, which is useful when reviewing many posts without making another platform request. Audience data includes follower characteristics, activity by hour, account actions, and optional niche benchmarks. Suggestion queries return hashtag reach or search terms for a selected network.

A local stdio deployment runs the package through npx and passes an Upload-Post API key in the environment. A hosted deployment exposes the streamable HTTP endpoint and accepts each user’s key through an Authorization header. OAuth connection flows are also available in supported hosted clients and through JWT-based connection tools.

Setup and configuration

For local use, configure an MCP client with a command equivalent to:

{
  "command": "npx",
  "args": ["-y", "@upload-post/mcp"],
  "env": {
    "UPLOAD_POST_API_KEY": "YOUR_API_KEY"
  }
}

API keys are obtained from the Upload-Post application. Hosted deployments use the /mcp endpoint and can authenticate with either Authorization: ApiKey YOUR_KEY or, for clients that require it, Authorization: Bearer YOUR_KEY.

Video inputs must be public or signed HTTPS URLs, or absolute local paths readable by a local server. A hosted server cannot access files on the user’s computer or chat attachments. For local files with an HTTP-capable client, stage the bytes with the media-upload flow, complete the upload, and pass the resulting media URL to the publishing tool. Staged media is removed after 24 hours. Inline base64 video is limited by UPLOAD_POST_MAX_INLINE_MB, which defaults to 100 MB.

Tools and capabilities

• Publish videos, photos, carousels, text posts, and LinkedIn documents.
• Schedule, inspect, edit, and cancel pending posts.
• Retrieve upload status, queued-job status, history, and connected-profile media.
• Read profile analytics, impressions, post metrics, cached metrics, and audience information.
• Manage Upload-Post profiles and generate or validate connection JWTs.
• Discover Facebook pages, LinkedIn pages, Pinterest boards, TikTok music, and TikTok locations.

Limitations and notes

Reddit is currently unavailable as a publishing target and returns reddit_unavailable; do not select it when publishing. TikTok audience and suggestion features require the relevant profile_analytics capability, while keyword suggestions also require trend_search. TikTok music and location helpers depend on the corresponding capabilities of the connected account.

Analytics responses vary by platform. TikTok post metrics may include retention curves, impression sources, audience types, follower gains, reach, and watch-time fields in addition to common counters. Audience date windows are limited to 60 days and end before the current day. Cached post metrics exist only after the post has been queried live and are not refreshed in the background.