SosoAPI

ai.sosoapiPublished by sosoapi.aiv0.5.7Updated Oct 27, 2026

Prepare, schedule and publish approved social posts using your connected SosoAPI accounts.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

SosoAPI is a remote MCP server that lets an assistant prepare, schedule and publish approved social media posts through connected SosoAPI accounts.

What you can do
  • Prepare social media posts for connected SosoAPI accounts.
  • Schedule posts for later publishing.
  • Publish posts that have been approved.
When to use it
Useful when you want an assistant to draft, queue and publish social media content through an existing SosoAPI account instead of switching to the SosoAPI interface.
Requirements
A remote streamable HTTP endpoint; no local package or runtime is needed. OAuth authentication is required, so you need a SosoAPI account and must complete the OAuth sign-in flow. No environment variables or headers are declared.
Before you install
The server can publish content to social accounts, so review drafts and approvals before anything goes live. Access is granted through OAuth to your SosoAPI accounts; grant only the accounts you intend to use and revoke access when no longer needed. Post content is handled by a third-party service.

Installation

In SourceWeft

  1. Open SosoAPI 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/ai.sosoapi%2Fsosoapi/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": {
    "sosoapi": {
      "type": "http",
      "url": "https://gqeshlawtcexsapabaui.supabase.co/functions/v1/remote-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. v0.5.7LatestOct 21, 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.