Schedchie

com.schedchie.wwwPublished by www.schedchie.comv3.0.0Updated Oct 29, 2026

Schedule, publish and track posts on 12 social networks from your AI assistant. X is a paid add-on.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

Schedchie lets an AI assistant schedule, publish and track social media posts across 12 networks from one remote MCP endpoint.

What you can do
  • Schedule posts for future publishing across 12 social networks
  • Publish posts to connected social accounts
  • Track the performance of published posts
  • Manage social posting from within an AI assistant conversation
When to use it
Useful when you plan and publish social media content regularly and want to draft, schedule and monitor posts without leaving your AI assistant.
Requirements
A remote MCP endpoint at mcp.schedchie.com using streamable HTTP. OAuth authentication is required, so a Schedchie account and an OAuth sign-in flow are needed. X (Twitter) posting is a paid add-on.
Before you install
The server can publish content publicly to connected social accounts, so review scheduled posts before they go out. OAuth grants it access to your Schedchie account and linked networks. Posting to X requires a paid add-on, which may involve charges.

Installation

In SourceWeft

  1. Open Schedchie 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.schedchie.www%2Fschedchie/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": {
    "schedchie": {
      "type": "http",
      "url": "https://mcp.schedchie.com/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. v3.0.0LatestOct 29, 2026
  2. v2.4.0Sep 16, 2026

Score

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