Dystro

dev.dystroPublished by dystro.devOfficial publisherv1.0.0Updated Oct 24, 2026

Unified social posting, inbox & analytics across 12+ platforms. Sign in with Dystro or API key.

VerifiedStreamable HTTPWeb executableCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

Dystro is a remote MCP server that lets an assistant publish social posts, manage a unified inbox and read analytics across 12+ platforms.

What you can do
  • Publish and schedule social posts across 12+ connected platforms
  • Read and manage a unified inbox of incoming social messages
  • Review cross-platform analytics and performance data
  • Work from one account spanning multiple social networks
When to use it
Useful when you want an assistant to draft, publish or schedule social content and check engagement without switching between each network's own dashboard.
Requirements
A remote MCP endpoint at app.dystro.dev over streamable HTTP; OAuth sign-in with a Dystro account is required, or an API key. No local runtime or environment variables are declared.
Before you install
The server can post and send content publicly on connected social accounts and can read inbox messages, so review actions before they go out. Access is granted through OAuth or an API key, which should be kept private; connected account data is handled by Dystro as a third party.

Installation

In SourceWeft

  1. Open Dystro 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/dev.dystro%2Fdystro/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": {
    "dystro": {
      "type": "http",
      "url": "https://app.dystro.dev/api/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.0LatestSep 16, 2026

Score

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

    Publish an icon in the registry entry.

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