yeetpost

com.yeetpostPublished by yeetpost.comOfficial publisherv1.0.0Updated Oct 29, 2026

Post and schedule to LinkedIn, X, Bluesky, Discord, Telegram and Mastodon from AI agents.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

Remote MCP server that lets an AI assistant publish and schedule posts to LinkedIn, X, Bluesky, Discord, Telegram and Mastodon.

What you can do
  • Publish posts to connected social and chat channels (LinkedIn, X, Bluesky, Discord, Telegram, Mastodon)
  • Schedule posts for later delivery
  • Manage the connected accounts and destinations behind those posts
  • Authenticate either with an API key or through OAuth 2.1 with PKCE and dynamic client registration
When to use it
Useful when you want an assistant to draft and then actually publish or queue social media and community announcements across several networks without switching apps. Best for teams already using yeetpost as their posting hub.
Requirements
A remote endpoint at api.yeetpost.com over streamable HTTP; no local package or runtime. An account with yeetpost and connected destination accounts. Authentication is required: either an Authorization header carrying a Bearer API key or OAuth 2.1 (PKCE, dynamic client registration, scope mcp). Network access to the service.
Before you install
The server can post publicly and schedule content on real accounts, so review drafts before letting it publish. The Authorization header holds a secret API key; keep it out of logs and shared configs. Posts and account data go to a third-party service, and connected networks receive the published content.

Installation

In SourceWeft

  1. Open yeetpost 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/com.yeetpost%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": {
    "yeetpost": {
      "type": "http",
      "url": "https://api.yeetpost.com/api/v2/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

1
  1. v1.0.0LatestOct 29, 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 listed15 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.