LotsSocial

io.github.sivaguruayyaduraiPublished by GitHub account sivaguruayyaduraiv1.0.0Updated Oct 25, 2026

Approval-first social planning, publishing, and analytics across 12 platforms.

The publisher's own server: LotsBlog

VerifiedStreamable HTTPWeb executableCommunication & CollaborationData & Analytics

Overview

AI-generated overview

LotsSocial is a remote MCP server for approval-first social planning, publishing and analytics across 12 platforms.

What you can do
Plan social posts and schedule them across multiple platforms, with an approval step before anything goes out. Publish approved content to the connected social accounts. Review analytics on how published posts perform. The registry lists no individual tools, so the exact actions available are not documented here.
When to use it
Useful when an assistant should help draft, schedule and publish social content across several platforms while keeping a human approval step, and when you also want performance reporting in the same workflow.
Requirements
A remote MCP endpoint reached over streamable HTTP; no local package or runtime is needed. The manifest declares no authentication, environment variables or headers, so how accounts are connected and authorized is not documented.
Before you install
It publishes to live social accounts, so content can go public; the approval-first design is the main safeguard. The manifest declares no authentication, which is unusual for a publishing service and should be confirmed before connecting accounts. Analytics data is held by the third-party service.

Installation

In SourceWeft

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

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/io.github.sivaguruayyadurai%2Flotssocial/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.

{
  "mcpServers": {
    "lotssocial": {
      "type": "http",
      "url": "https://api.lots.social/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 21, 2026

Score

25% 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

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

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

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Lots integrations