Openpost logo

Openpost

Create drafts, schedule social posts, and check publishing results through OpenPost’s MCP automation interface.

Install Openpost

Pick your client, then add it in one click or paste the config.

No confirmed install command yet

We only publish a config when the install details come from the project itself — its README, its docs, or a verified owner. We haven’t found those for openpost, and we’d rather show nothing than a guess you’d paste into your client.

Open setup steps on GitHub

Overview

openpost connects AI agents to OpenPost’s social publishing workflows through MCP. Agents can create drafts, schedule posts, and inspect publishing results, while OpenPost manages connected accounts, platform-specific content versions, queues, and publishing. Reach for it when an agent needs to automate social content operations across supported networks. OpenPost also provides workflows, media management, analytics, inbox features, and optional AI-assisted writing around those publishing tasks.

Use cases

  • Create drafts from agent-generated social content
  • Schedule posts across connected social accounts
  • Check whether scheduled publishing completed
  • Turn release or RSS events into reviewable drafts

Key features

  • Create post drafts
  • Schedule posts and queue content
  • Check publishing results
  • Adapt posts per platform
  • Reuse account groups with Social Sets
  • Connect publishing to workflows and n8n

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

8/8 checks healthy over the last 45d

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars753Stargazers on the source repository.
Last commitTodayMost recent push to the default branch.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How Openpost works

What openpost does

openpost exposes OpenPost’s social publishing automation features to AI agents through the Model Context Protocol. The main supported operations are creating post drafts, scheduling content, and checking the outcome of publishing jobs. OpenPost acts as the workspace behind those operations, with connected social accounts, account groups, platform-specific post variations, previews, calendars, queues, and publishing limits that can vary by provider.

This makes the server relevant for agent-driven content workflows rather than only one-off posting. An agent can prepare content for review, send it into a publishing schedule, and inspect whether the publishing operation completed successfully. OpenPost can be self-hosted or used through OpenPost Hosted.

How it works

OpenPost organizes social publishing around workspaces and connected accounts. Posts can be adapted for each selected account, then scheduled for a chosen time or the next available queue slot. Social Sets let teams reuse groups of accounts when preparing recurring campaigns.

The wider OpenPost workflow system can turn GitHub releases, RSS feeds, and scheduled prompts into drafts. Visual workflow steps can include AI or conditions, and custom data can be handled with HTTP requests and JavaScript. Drafts can be reviewed before scheduling, and workflow runs can be inspected afterward.

The MCP automation layer is intended to let scripts, agents, and n8n workflows create drafts, schedule posts, and query publishing results. OpenPost also supports a TypeScript SDK and command-line interface for automation outside MCP.

Tools and capabilities

  • Create social post drafts for connected accounts.
  • Schedule posts at a selected time or place them in a queue.
  • Check publishing results after scheduled content runs.
  • Adapt text and media for individual platforms before publication.
  • Reuse account groups through Social Sets.
  • Combine publishing automation with OpenPost workflows triggered by releases, feeds, or prompts.

OpenPost’s surrounding workspace includes a media library for reusable images, videos, fonts, and brand assets; image and carousel design; video editing; inbox handling for supported comments and direct messages; analytics; and post repurposing. These capabilities provide context for a broader social publishing process, while the MCP-focused automation functions center on drafts, scheduling, and result checks.

Limitations and notes

Connected providers retain their own capabilities and publishing limits, so available behavior can differ by social network. Auto-reposting is available only on supported networks and can use delay and engagement rules. AI writing is optional, and generated content is intended for review before publishing.

OpenPost Hosted signups are currently handled through a waitlist while additional social platform approvals are completed. Existing hosted accounts can continue signing in. The project can also be self-hosted, giving teams another way to run the OpenPost workspace behind their own deployment.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Openpost

openpost is an MCP server that connects AI agents to OpenPost for social publishing workflows. Its main tools create drafts, schedule posts, and check publishing results through OpenPost’s automation interfaces. It can support agent-driven content operations while OpenPost handles connected accounts, platform-specific versions, queues, and publishing workflows.

Yes, openpost can schedule posts through OpenPost. Content can be assigned a specific publishing time or placed into the next available queue slot, with OpenPost applying the capabilities and publishing limits of each connected social provider.

Yes, openpost can check publishing results after content is scheduled or processed. This supports agent workflows that need to inspect the outcome of social publishing operations.

Yes, OpenPost supports adapting text and media for each connected account before publishing. Agents can create drafts within that workflow, while each provider retains its own capabilities and publishing limits.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewOpenpost AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/openpost?style=directory)](https://allmcps.com/mcp/openpost)
HTML Embed
<a href="https://allmcps.com/mcp/openpost"><img src="https://allmcps.com/api/badge/openpost?style=directory" alt="Openpost on AllMCPs" /></a>