Octopost

ink.octopostv1.0.0Updated Oct 8, 2026

Cross-post, schedule and queue social posts to X, Bluesky, LinkedIn, Threads, Mastodon and more.

VerifiedStreamable HTTPWeb executableBusiness & CommerceCommunication & Collaboration

Overview

AI-generated overview

Lets an assistant cross-post, schedule and queue social media posts to X, Bluesky, LinkedIn, Threads, Mastodon and other networks.

What it does
Octopost is a remote MCP server for social publishing. According to its registry description, it lets an assistant cross-post, schedule and queue posts across networks such as X, Bluesky, LinkedIn, Threads and Mastodon. No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Worth adding when you want an assistant to publish or schedule the same content to several social networks from one place, rather than opening each network separately.
Requirements
A remote streamable HTTP endpoint at octopost.ink; nothing runs locally. It requires an Octopost API key (op_...), obtained from Dashboard > API keys, sent in the Authorization header as a Bearer token. Network access to the endpoint is needed.
Before you install
The Authorization header carries a secret API key, so treat it as a credential and avoid exposing it. The server publishes and schedules content on connected social accounts, which means posts can go out publicly; review what an assistant is about to send before it acts.

Installation

In SourceWeft

  1. Open Octopost 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.

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "octopost": {
      "type": "http",
      "url": "https://octopost.ink/mcp"
    }
  }
}

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v1.0.0LatestOct 8, 2026