deploy.social

social.deployPublished by deploy.socialOfficial publisherv1.0.1Updated Oct 28, 2026

Post a video once to YouTube Shorts, Instagram/Facebook Reels, TikTok, Threads, X and Bluesky

VerifiedStreamable HTTPWeb executableCommunication & CollaborationMedia & Design

Overview

AI-generated overview

Remote MCP server that lets an assistant publish one short video to YouTube Shorts, Instagram/Facebook Reels, TikTok, Threads, X and Bluesky at once.

What you can do
  • Publish a single short video to multiple social platforms in one step, covering YouTube Shorts, Instagram and Facebook Reels, TikTok, Threads, X and Bluesky.
  • No tool list is published, so the exact operations (upload, scheduling, status) are not documented in the supplied material.
When to use it
Useful when you want an assistant to distribute the same short-form video across several social networks without uploading it to each platform separately.
Requirements
A remote endpoint at api.deploy.social over streamable HTTP; OAuth authentication is required, so a deploy.social account and an OAuth grant are needed. No environment variables or headers are declared.
Before you install
The server posts content publicly to connected social accounts, so review the video and caption before authorizing a publish. OAuth access to those accounts should be limited to what is needed and revocable. Tool-level behavior is not documented here.

Installation

In SourceWeft

  1. Open deploy.social in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/social.deploy%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "deploy-social": {
      "type": "http",
      "url": "https://api.deploy.social/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v1.0.1LatestSep 30, 2026
  2. v1.0.0Sep 30, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Deploy integrations