AIsa Social

one.aisaPublished by aisa.oneOfficial publisherv1.0.1Updated Oct 24, 2026

What people post and say across the major social platforms, in one place.

The publisher's own server: AIsa Agent Mail

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

AIsa Social is a remote MCP server that gives an assistant access to what people post and say across major social platforms in one place.

What you can do
Access social platform content in one place, covering posts and public commentary from major networks. The manifest lists no individual tools, so the exact operations are not documented; the description only states that cross-platform social content is brought together. Authentication is required via OAuth before use.
When to use it
Consider it when you want an assistant to work with social media content from several major platforms through a single hosted connection, rather than separate integrations per network.
Requirements
A remote MCP endpoint at mcp.aisa.one over streamable HTTP, with OAuth authentication required. No environment variables, headers or local packages are declared. Network access to the endpoint is needed.
Before you install
OAuth grants the server access to your account, so review the scopes requested at sign-in. The tool list is not published, so what the assistant can read or change is unclear; confirm before relying on it. Social content is fetched from third-party platforms through the provider.

Installation

In SourceWeft

  1. Open AIsa Social 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/one.aisa%2Fsocial/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": {
    "aisa-social": {
      "type": "http",
      "url": "https://mcp.aisa.one/social/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.1LatestSep 16, 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.

Other Aisa integrations