social-media-mcp
Upload-Post is the all-in-one social media MCP server — the Model Context Protocol server for social media publishing, scheduling and analytics.
What it can do
- Upload Video: Publish a video to one or more platforms. Use `videoPathOrUrl` only for public/signed HTTPS URLs, or for absolute local paths when the MCP server runs on the same machine as the file. Ho
- Upload Photos: Publish one or more photos (single image or carousel). Each item in `photosPathsOrUrls` may be a public URL or a local path.
- Upload Text: Publish a text-only post. Title is required for Reddit. `linkUrl` (or platform-specific *LinkUrl) attaches a link preview where supported.
What data it sees
Do you need an account
No: the server works without sign-in
Upload-Post is the all-in-one social media MCP server — the Model Context Protocol server for social media publishing, scheduling and analytics. Connect any MCP-compatible AI agent (Claude, Cursor, ChatGPT, Claude Desktop, n8n, and more) and publish, schedule and analyze content across 13+ social networks from one API: TikTok, Instagram, YouTube, YouTube Shorts, Instagram Reels, LinkedIn, Facebook, X (Twitter), Threads, Pinterest, Reddit, Bluesky, Google Business, Discord and Telegram.
A single social media MCP for cross-posting, content automation, post scheduling, analytics and engagement: ~45 tools covering video/photo/text uploads, scheduling queues, performance analytics and impressions, comment management, direct messages (DMs) and auto-DMs, plus GPU FFmpeg video encoding. Perfect for social media automation, AI content agents, marketing workflows and social media management.
Remote hosted server (streamable-HTTP + OAuth) or local stdio. Listed on the official MCP Registry as com.upload-post/mcp.
Keywords: social media MCP, MCP social media, social media API, social media automation, post scheduler, cross-posting, content automation, TikTok MCP, Instagram MCP, YouTube MCP, LinkedIn MCP, social media analytics.
Server tool list (45)
Raw names from tools/list. Only developers need these.
| upload_video | Publish a video to one or more platforms. Use `videoPathOrUrl` only for public/signed HTTPS URLs, or for absolute local paths when the MCP server runs on the same machine as the file. Hosted clients such as ChatGPT and claude.ai cannot publish attached files by passing `/mnt/data`, sandbox, or mounted local paths; for those files, ALWAYS call `open_upload_studio` first so the browser stages the video to Upload-Post/R2, then publishes it. `videoBase64` is only for clients that can provide raw bytes directly and is capped by UPLOAD_POST_MAX_INLINE_MB (default 100). Returns a `request_id` you can poll with `get_status`. Supports per-platform overrides (tiktokPrivacyLevel, youtubePrivacyStatus, youtubePlaylistId, facebookPageId, instagramMediaType, etc.). |
| upload_photos | Publish one or more photos (single image or carousel). Each item in `photosPathsOrUrls` may be a public URL or a local path. |
| upload_text | Publish a text-only post. Title is required for Reddit. `linkUrl` (or platform-specific *LinkUrl) attaches a link preview where supported. |
| upload_document | Publish a document (PDF / PPT / PPTX / DOC / DOCX) to LinkedIn. Title is required. |
| get_status | Check the status of an async upload by `request_id`. Poll this until `status` is 'success' or 'failed'. |
| get_job_status | Check the status of a scheduled or queued upload by `job_id`. Use this for posts created with `addToQueue` or `scheduledDate`. |
| get_history | Paginated history of uploads across all profiles. |
| get_media | Retrieve recent media (videos, photos, text posts) pulled directly from a profile's connected social accounts. Supports instagram, tiktok, youtube, linkedin, facebook, x, threads, pinterest, bluesky, reddit. Useful for browsing what already exists on a platform before posting more. |
| list_scheduled | List all currently scheduled (not-yet-published) posts. |
| cancel_scheduled | Cancel a scheduled post by its `job_id`. |
| edit_scheduled | Reschedule a post: change date and/or timezone. |
| get_analytics | Aggregated analytics for a profile across selected platforms (followers, views, engagement). |
| get_total_impressions | Sum of impressions for a profile from daily snapshots. Use `period` for presets, or `startDate`/`endDate` for custom ranges. |
| get_post_analytics | Per-platform metrics for a specific post identified by `request_id`. |
| get_platform_metrics | Reference: which metrics are available per platform (impressions, likes, …) and their human labels. |
| get_account_info | Validate the current API key and return account information. Useful as a first call to confirm credentials before doing real work. |
| list_users | List all Upload-Post profiles in the account, with their connected social accounts. |
| create_user | Create a new Upload-Post profile (logical container for connected socials). |
| delete_user | Permanently delete a profile and disconnect its socials. |
| generate_jwt | Generate a JWT + connection URL so an end-user can connect socials inside an embedded Upload-Post flow (white-label integration). |
| validate_jwt | Verify a JWT previously issued by `generate_jwt`. |
| get_facebook_pages | Facebook pages connected to a profile. |
| get_linkedin_pages | LinkedIn company pages connected to a profile. |
| get_pinterest_boards | Pinterest boards available to a profile. |
| get_google_business_locations | Google Business Profile locations the profile can post to. |
| select_google_business_location | Pick the active Google Business location for a profile. Subsequent posts to `google_business` will publish there. |
| get_reddit_detailed_posts | Recent Reddit posts published from a profile, with the platform-side metadata (subreddit, flair, score, …). |
| get_post_comments | List comments on an Instagram post. Identify the post by either `postId` or `postUrl`. |
| reply_to_comment | Send a private DM to the author of an Instagram comment (within Instagram's 7-day reply window). |
| public_reply_to_comment | Post a public reply visible under the original Instagram comment. |
| send_dm | Send an Instagram DM to a recipient from a connected Upload-Post profile. Use a recipient_id returned by Instagram comments or DM conversation tools. |
| list_dm_conversations | Recent DM conversations for a profile on a given platform. |
| manage_autodms | Control Instagram AutoDM monitors. For action='start', provide post_url, reply_message, and profile_username. For stop/pause/resume/delete/logs, provide monitor_id. For status, optionally set include_inactive=true. |
| submit_ffmpeg_job | Submit a private FFmpeg processing job through Upload-Post. Provide `input_url` for one input, or `files` for multiple public URLs. Optionally provide `full_command` beginning with ffmpeg for explicit trim/transcode/watermark/thumbnail commands. Returns a `job_id` you can poll with `get_ffmpeg_job`. |
| get_ffmpeg_job | Poll the status of an FFmpeg job. When status is 'completed', call `download_ffmpeg_result` to obtain the file. |
| download_ffmpeg_result | Returns the download URL and metadata for a completed FFmpeg job without streaming the processed file through MCP. |
| get_ffmpeg_consumption | Monthly FFmpeg processing minutes used vs. plan allowance. |
| get_queue_settings | Posting queue configuration (slots per day, time windows, timezone). |
| update_queue_settings | Update posting queue configuration for a profile. Fields are flat, not nested: timezone, slots, days_of_week, and max_posts_per_slot. |
| preview_queue | Preview the upcoming queue slots and what would land in them. Optionally `nextSlot=true` returns just the next available slot timestamp. |
| create_media_upload | Internal/app staging helper for clients that can directly PUT file bytes to the returned upload_url. Do NOT use this directly from the ChatGPT/claude.ai model for attached files: the model/server environment cannot read or upload ChatGPT attachment bytes. For ChatGPT attached video uploads, call open_upload_studio first; the Studio browser component will call this tool after the user selects the file. Use this directly only in MCP clients that truly hold the file bytes and can perform the HTTP PUT themselves. Staging media is deleted after 24 hours; scheduled posts are safe because upload_video copies the media into durable scheduler storage. |
| complete_media_upload | Internal/app staging helper. Validate a media upload only after the browser/client has successfully PUT the actual file bytes to upload_url. Do NOT call this immediately after create_media_upload from the model; without the intervening PUT, completion will fail or produce no publishable media. Returns a temporary media_url that can be passed to upload_video/upload_photos immediately. |
| get_media_upload | Internal/app staging helper. Get status for a short-lived MCP media upload. Optionally returns a fresh temporary media_url for an already-uploaded staging object. |
| delete_media_upload | Internal/app staging helper. Delete a short-lived MCP staging media upload from R2. This does not delete scheduler durable copies created later by upload_video. |
| open_upload_studio | Open the ChatGPT UI for local/attached video uploads. Use this FIRST when the user attaches a video in ChatGPT or claude.ai and does not provide a public HTTPS URL. Do not try upload_video with /mnt/data, sandbox, or mounted local paths first: hosted MCP servers cannot read those files. The Studio lets the user select the file in the browser, stages it in short-lived Upload-Post/R2 storage, and publishes it through Upload-Post. |