Zoosial

com.zoosialPublished by zoosial.comOfficial publisherv1.0.0Updated Oct 29, 2026

Social media API for AI agents: publish, DMs, comments, Meta ads and leads.

VerifiedStreamable HTTPWeb executableCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

Remote MCP endpoint for Zoosial, a social media API that lets an assistant publish posts, handle DMs and comments, and work with Meta ads and leads.

What you can do
  • Publish content to social media channels
  • Read and respond to direct messages
  • Manage comments
  • Work with Meta ads and lead data
  • No tool list is published, so exact operations are not documented here.
When to use it
Consider it when an assistant should act on social media accounts directly: posting content, answering messages and comments, or handling Meta advertising and lead follow-up from within a conversation.
Requirements
A remote MCP endpoint at zoosial.com reached over streamable HTTP. OAuth authentication is required, so a Zoosial account and an authorized connection are needed. No environment variables or headers are declared.
Before you install
The server can publish posts, send messages and reply to comments, so assistant actions are publicly visible and hard to undo. It also touches Meta ads and leads, which may involve ad spending and customer personal data. Access is granted through OAuth to a Zoosial account; review the scopes granted and confirm what data is shared with the provider.

Installation

In SourceWeft

  1. Open Zoosial 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.zoosial%2Fzoosial/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": {
    "zoosial": {
      "type": "http",
      "url": "https://zoosial.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

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