Postdom for Grok Bot

Postdom gives Grok Bot a native, OAuth-connected MCP toolset for scheduling and publishing finished social content under human guardrails, then reading the real outcome and available performance evidence back.

Status: PREPARED_NOT_SUBMITTED. The canonical public repository is https://github.com/deanfankhauser/postdom-grokbot, but it is currently empty while this repository receipt passes exact-head audit; it is not yet a published source mirror. This package has not been submitted to the Cursor Marketplace, installed in hosted Grok Bot, or approved by either marketplace. Do not describe it as listed, live, verified, featured, or available in Grok Bot.

What it supports

Postdom currently publishes to TikTok, Instagram, YouTube, LinkedIn, Facebook, X, Snapchat, Threads, and Bluesky. The publish tool supports destination-specific surfaces such as Instagram Reels, Facebook Reels, YouTube Shorts, stories, feeds, and long-form YouTube where the selected account and media allow them.

The production MCP server exposes 15 agent-authority tools for workspace status, the workspace brief and learning digest, account discovery and connection, media upload and status, publication plans, publishing, post reads, schedule reads, and evidence-backed performance reads.

Postdom does not generate video. The user or another tool supplies finished media. Postdom validates it, schedules or publishes it, preserves human review and policy boundaries, and returns the terminal outcome.

Related MCP server: automate-idea-to-social-mcp

Authentication

The plugin contains no credential and implements no authentication code. Its only server declaration is the production Streamable HTTP endpoint at https://api.postdom.com/mcp.

Authentication is handled by the client. Postdom publishes OAuth 2.1 discovery, protected-resource metadata, PKCE S256, dynamic client registration, and read/write scopes. The Agent Plugins 1.0 format intentionally defines no portable OAuth fields, so the client starts and stores the browser OAuth connection. No client secret, access token, refresh token, workspace key, or signed upload URL belongs in this package.

Postdom agent credentials cannot call human approval, billing, policy-administration, or dashboard routes. The MCP server exposes only the agent-authority menu. Bluesky uses an app password and is connected by a human in the Postdom dashboard; connect_account deliberately does not request or handle that credential.

Included workflows

• Publish social content: check the workspace, choose connected destinations, validate and upload finished media, schedule or publish under the workspace's review policy, and follow the post to a terminal outcome.

• Read social performance: inspect available performance without turning missing metrics into zero or claiming evidence the platform did not return.

Local validation

From this directory, run npm test. The checks pin the portable manifest, the exact production MCP endpoint, credential-free configuration, honest submission state, tool inventory, business metadata, and the one-post/no-blind-retry closed-loop protocol.

Before any submission, the plugin still needs:

1. This canonical repository receipt merged, followed by publication of the exact merged integrations/grokbot/ tree to the public repository and a byte-identity check.

2. Local installation and validation in a compatible Agent Plugins client from that verified public source mirror.

3. A hosted Grok Bot OAuth connection test using browser OAuth.

4. A single-post closed loop that reaches a terminal state without a blind retry.

5. Exact-head merge audit and explicit outward-submission approval.

Support and policies

• Product: https://postdom.com

• Documentation: https://postdom.com/docs

• Support: support@postdom.com

• Privacy: https://postdom.com/privacy

• Terms: https://postdom.com/terms