Autoposting

ai.autopostingPublished by autoposting.aiOfficial publisherv1.0.0Updated Oct 24, 2026

Schedule, generate and publish social posts to X, LinkedIn, Instagram, Threads and YouTube

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

Autoposting is a remote MCP server that lets an assistant schedule, generate and publish social media posts to X, LinkedIn, Instagram, Threads and YouTube.

What you can do
Schedule social posts for future publishing across connected channels, including X, LinkedIn, Instagram, Threads and YouTube. Generate post content with the assistant before it goes out. Publish posts to the connected social accounts. The manifest lists no individual tools, so the exact operations are not documented here.
When to use it
Useful when you want an assistant to draft, queue and publish social media content across several platforms from one place, rather than working inside each network's own composer.
Requirements
A remote MCP server reached over streamable HTTP at the provider's hosted endpoint; no local package or runtime is needed. The manifest declares no authentication, environment variables or headers, but publishing to social accounts will normally require connecting those accounts in the provider's app.
Before you install
Publishing sends content publicly to third-party social networks under your accounts, and scheduled posts may go out without further review. The manifest declares no authentication, so confirm how access to your accounts is actually secured before connecting. Content you generate or upload is handled by the provider.

Installation

In SourceWeft

  1. Open Autoposting in the dashboard and add it to a workspace.
  2. 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/ai.autoposting%2Fautoposting/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.

{
  "mcpServers": {
    "autoposting": {
      "type": "http",
      "url": "https://app.autoposting.ai/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

56% 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 listedRequired15 pts

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

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • 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.