Skip to main content
Glama
deanfankhauser

Postdom MCP Server

Postdom MCP

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

Postdom makes short-form videos and slideshows in your brand and posts approved content to TikTok, Instagram, YouTube, Facebook, LinkedIn, X, Snapchat, Threads and Bluesky. AI agents can connect to a Postdom workspace through MCP to prepare publishing plans, schedule supported content and read outcomes and performance.

This public repository contains Postdom's remote MCP declaration and Agent Plugins workflows. It is available at https://github.com/deanfankhauser/postdom-grokbot. It connects to Postdom's hosted service; it does not contain the service's implementation.

Connect to Postdom

Use an MCP client that supports OAuth to connect to the endpoint. Postdom uses OAuth 2.1 with PKCE S256 and read/write scopes. The client handles browser authorization and stores the connection. Review the workspace and requested access before authorizing it.

The package's mcp.json declares the remote endpoint without credentials. Never put a client secret, access token, refresh token, workspace key or signed upload URL in this repository. The optional local MCP package and client-specific setup instructions are documented on the Postdom website.

Related MCP server: ViralHunt MCP

Current hosted tools

The hosted MCP server exposes 16 tools, verified through the Glama connector on 7 October 2026:

Purpose

Tools

Workspace and brand context

get_workspace_status, get_brief, get_digest, get_learning

Connected accounts

list_accounts, connect_account

Media and slideshows

upload_media, get_media, create_slideshow

Publishing plans

submit_plan, get_plan

Publishing and outcomes

publish_video, get_publish, list_posts

Performance

get_performance, get_best_posts

Postdom's app creates videos and slideshows. Agents can also upload supported finished media and create slideshows through the exposed tools. Check the current tool schemas for exact inputs and supported operations; app functionality and MCP functionality are separate surfaces.

Human approval and evidence

Agent credentials cannot approve posts, change autonomy or policy, or administer billing. Humans connect social accounts and manage permissions in the Postdom dashboard. For supported platform OAuth flows, connect_account returns an authorization URL for a human to complete.

The publishing workflow checks workspace policy and plan authorization, follows a post to its observed outcome, and stops on uncertain states rather than retrying a failed publish automatically. Performance reads preserve missing measurements and availability states instead of treating absent values as zero.

Included workflows:

Repository package status

The hosted MCP service and Glama connector are available. The Grok Bot and Cursor Marketplace submission materials in submission/ are separate preparation artifacts and retain the status PREPARED_NOT_SUBMITTED. This repository does not establish that the plugin has been submitted to, installed in or approved by either marketplace.

Before submitting the Grok Bot package, validate the exact package version in a compatible client, test hosted OAuth, perform the single-post closed-loop protocol with human approval, and obtain explicit outward-submission approval. The public package may differ from a later integrations/grokbot/ tree in Postdom's main repository; verify the intended version before submission.

Local validation

Run npm test from this directory. The checks cover the portable manifest, production endpoint, credential-free configuration, workflow boundaries and honest marketplace submission status. The submission/ inventory describes the prepared package; use the hosted tool schemas and the table above for the current service inventory.

Support and policies

Related MCP Connectors

Related MCP Servers