Distro Publisher (beta)

media.distroPublished by distro.mediaOfficial publisherv2.0.3Updated Oct 24, 2026

AI-native news publishing: manage publications, write stories, upload media, and browse feeds.

VerifiedStreamable HTTPWeb executableCommunication & CollaborationMedia & Design

Overview

AI-generated overview

A remote, OAuth-protected MCP server for AI-native news publishing that lets an assistant manage publications, write stories, upload media and browse feeds.

What you can do
Manage publications and their settings through the assistant. Write and edit news stories. Upload media assets for use in publishing. Browse feeds to review published or incoming content.
When to use it
Useful for newsrooms, publishers or content teams that want an assistant to draft and publish stories, keep publications organized, and review feeds without switching tools.
Requirements
A remote MCP endpoint at app.distro.media over streamable HTTP. OAuth authentication is required, so a Distro account and a completed sign-in flow are needed. No environment variables or headers are declared.
Before you install
The server can write and publish content and upload media, so changes may go live publicly. Access is granted through OAuth to your publishing account; review the scopes requested during sign-in before authorizing.

Installation

In SourceWeft

  1. Open Distro Publisher (beta) 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/media.distro%2Fdistroverse/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": {
    "distro-publisher-beta": {
      "type": "http",
      "url": "https://app.distro.media/mcp/stream"
    }
  }
}

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. v2.0.3LatestSep 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.