PostOwl - Let Claude Code or Codex post to your socials

by•
What's new: post without a browser. Install the CLI (npm i -g postowl), or point Claude Code, Cursor, or Codex at our MCP server, and your AI agent drafts, posts, and schedules to X, LinkedIn, Instagram, TikTok & Threads on your behalf. Through your own connected accounts, with scoped, revocable access. This launch was posted by the CLI itself, from the terminal.

Add a comment

Replies

Best
Maker
šŸ“Œ
Hey Product Hunt šŸ‘‹ This week I taught my coding agent to post for me. Now I stay in Claude Code and say "post that we shipped the CLI and schedule a follow-up for 9am," and it does. I never open a social app. Two pieces make it work: • A CLI: npm i -g postowl, then postowl login and postowl post create "..." --schedule "friday 9am". Threads, media, natural-language scheduling, and --json on every command for scripts. • A hosted MCP server: point Claude Code, Cursor, or Codex at it and the agent gets scoped tools to post and schedule to X, LinkedIn, Instagram, TikTok and Threads, through your own connected accounts. The fun part: this launch was announced on X by the CLI itself, from the terminal. The tool shipped the news about itself. The honest bit: the first time an agent posted to my real account before I'd read the text, my stomach dropped a little. That's why the access it gets is scoped and revocable, not your session, and it can't touch anything outside your connected accounts. So I'll ask you the question I keep asking myself: would you let an agent post to your real accounts? If not, what is the one thing that would change your mind? Happy to answer anything about the MCP setup or the auth model. šŸ¦‰

Have you considered adding a sentiment analysis feature that scores scheduled posts before they go live? It would help catch tweets that might come across tone-deaf or off-brand, especially when AI is generating content quickly. A simple red/yellow/green indicator next to each draft would be really useful for staying consistent with voice.