Web app · CLI (yominpost) · MCP server () · Agent Skill () · MIT
Self-hosted AI social media studio: one piece of material in, platform-native posts out. Format router, self-critique, pre-publish risk gate, real OAuth publishing. Web app + CLI + MCP server + agent skill.
No install and no config. All you need is uv (curl -LsSf https://astral.sh/uv/install.sh | sh):
# 1) Start the studio (web UI on http://127.0.0.1:8300, data in ~/.yominpost/)
uvx --from git+https://github.com/mrlong0129/yominpost yominpost --open
# 2) Or generate posts straight from the terminal
uvx --from git+https://github.com/mrlong0129/yominpost yominpost run \
--brand "Acme" --source "Acme turns one long-form idea into ten platform-native posts." \
--platform x --platform linkedin --platform tiktok --topics 3
# 3) Claude Code: register the MCP server in one line
claude mcp add yominpost -- uvx --from git+https://github.com/mrlong0129/yominpost yominpost-mcp
Cursor: add this to ~/.cursor/mcp.json (global) or .cursor/mcp.json (project):
Posting the same idea to X, LinkedIn, Instagram, TikTok and Telegram means rewriting it five times, guessing which format each platform wants, and hoping the AI-written version doesn't get the account flagged. Hosted schedulers lock your tokens and drafts in someone else's cloud, and most AI writers stop at "here is a caption".
YominPost does the whole loop on your own machine:
It decides the format, not just the words. A rule-based router picks text, thread, image post, carousel or short video per platform and explains why.
It critiques its own drafts. Every draft is scored and rewritten once if it misses the bar.
It protects the account. A pre-publish risk gate catches leaked prompts, engagement bait, hashtag stuffing, duplicate posts and unsafe posting cadence. These are the signals that get AI-assisted accounts restricted.
It actually publishes. Real OAuth2 + PKCE connectors, encrypted tokens, a scheduler that fires on time and never double-posts.
Paste text, a URL or image links → analysis → research → strategy → one draft per channel, shown on an infinite canvas with chat-style refinement
Swappable drivers
template (offline, deterministic, default) · claude_code (local claude CLI) · codex (local codex CLI) · agy · anthropic (API). Automatic fallback chain, so a failing driver never breaks a run
Real publishing
X, LinkedIn, Reddit, Facebook Page, Instagram, YouTube Shorts, Discord, Mastodon (zero-config app registration), Telegram, Bluesky, Webhook. TikTok, Xiaohongshu, Threads and Pinterest are simulated for now
Pre-publish risk gate
Prompt-leak and engagement-bait lint, hashtag/link limits, duplicate detection, per-platform cadence caps, auto-freeze after a platform block
Operations
Calendar (week/list), scheduled queue with retry, asset library, topic bank, per-channel health (native signals such as karma, strikes and account status), daily channel sync
Self-hosted and safe by default
FastAPI + SQLite, no build step. Fernet-encrypted tokens, operator access key (required for public deploys), SSRF-guarded URL fetching, daily backups
Agent-native
MCP tools generate_posts, check_post, save_draft, list_posts, list_platforms. There is deliberately no publish tool: a human approves in the UI
Architecture
flowchart LR
subgraph Inputs
U[Operator in browser]
A[AI agent via MCP]
C[CLI]
end
U --> WEB[FastAPI app<br/>web/app.py + vanilla JS SPA]
A --> MCP[MCP server<br/>mcp_server.py]
C --> CLI[cli.py]
WEB --> SVC[services.py<br/>compose · posts · publish]
MCP --> SVC
CLI --> ORCH
SVC --> ORCH[orchestrator.py<br/>8-slot pipeline]
ORCH --> DRV{{Driver chain<br/>template · claude · codex · anthropic}}
SVC --> RISK[platform_risk.py<br/>pre-publish gate]
RISK --> CONN[connectors/<br/>OAuth2 + PKCE · token · webhook]
CONN --> P[(X · LinkedIn · Reddit · IG · FB · YT<br/>Telegram · Discord · Mastodon · Bluesky)]
SVC --> DB[(SQLite<br/>~/.yominpost/data)]
SCHED[scheduler.py<br/>due posts · health · backups] --> SVC
Real image generation (gpt-image, any OpenAI-compatible endpoint)
X_CLIENT_ID, LINKEDIN_CLIENT_ID, …
OAuth apps for one-click Connect (or paste them once on the Settings page)
YOMINPOST_HOME
Data root, default ~/.yominpost
YOMINPOST_PUBLIC_URL + YOMINPOST_ACCESS_KEY
Public deployment. The app refuses to start publicly without an access key
FAQ
Do I need an API key? No. The default template driver runs offline and deterministically, so you can try the whole flow and run the test suite with zero keys. For production-quality copy, switch to claude_code or codex (uses the CLI you are already logged into) or anthropic.
Is the offline output good enough to post? It is a solid scaffold that follows your material's language, not a replacement for a real model. Use it to try the workflow, then plug in a driver.
Can the MCP server publish for me? No, and that's on purpose. Agents can generate, check and save drafts; you review and press Publish in the UI. Publishing goes out under your real accounts and can't be undone.
Where is my data? In ~/.yominpost/ (SQLite DB, encryption key, generated posters). Back up data/.secret.key together with the DB, or stored OAuth tokens can't be decrypted.
Which platforms really publish? X, LinkedIn, Reddit, Facebook Page, Instagram, YouTube Shorts, Discord, Mastodon, Telegram, Bluesky and Webhook. TikTok, Xiaohongshu, Threads and Pinterest use a simulated connector until their APIs are wired in.
What language is the UI? The web UI is currently in Chinese. Generated copy follows your material (English in, English out) or --language en|zh. An English UI is on the roadmap; PRs welcome.
How is this different from Postiz / Buffer? Same "connect → compose → schedule → publish" backbone, plus an AI content engine that picks formats and critiques itself, a platform-risk gate built for AI-assisted posting, and an MCP server so coding agents can draft for you. It is a single-user, self-hosted Python app, not a SaaS.
Development
git clone https://github.com/mrlong0129/yominpost && cd yominpost
uv venv && uv pip install -e ".[dev]"
.venv/bin/pytest -q # offline, no keys needed
.venv/bin/yominpost serve # or ./run.sh
Self-hosted AI social media studio: one piece of material in, platform-native posts out. Format router, self-critique, pre-publish risk gate, real OAuth publishing. Web app + CLI + MCP server + agent
Self-hosted AI social media studio: one piece of material in, platform-native posts out. Format router, self-critique, pre-publish risk gate, real OAuth publishing. Web app + CLI + MCP server + agent skill.
ตรวจสอบล่าสุดเมื่อ 2026-10-27 Self-hosted AI social media studio: one piece of material in, platform-native posts out. Format router, self-critique, pre-publish risk gate, real OAuth publishing. Web app + CLI + MCP server + agent skill.