Postdom

io.github.deanfankhauserPublished by GitHub account deanfankhauserv0.4.1Updated Oct 24, 2026

Videos that make your business go viral, made for you.

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

A remote MCP server from Postdom, a service that makes promotional videos for a business, connected to an assistant over streamable HTTP with OAuth sign-in.

What you can do
The listing gives no tool list, instructions or README, so the specific actions are not documented. The registry description says the service produces videos intended to help a business go viral, made on the customer's behalf. An assistant connected to it would presumably work with that video-making service, but which operations are exposed cannot be confirmed from the supplied material.
When to use it
Worth considering if you already use Postdom for business video content and want an assistant to reach the service directly. Because no tools are documented, check the provider's own documentation before relying on it for a specific workflow.
Requirements
A remote endpoint reached over streamable HTTP at the provider's API host. Authentication is OAuth and is required, so the user must sign in to a Postdom account and authorize the connection. No environment variables or headers are declared.

Installation

In SourceWeft

  1. Open Postdom 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/io.github.deanfankhauser%2Fpostdom/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": {
    "postdom": {
      "type": "http",
      "url": "https://api.postdom.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

2
  1. v0.4.1LatestOct 6, 2026
  2. v0.4.0Sep 25, 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.