Slack tools in your terminal
Over MCP, scheduling and analytics show up as first-class tools. Over the CLI, every command returns JSON that Claude Code can chain reliably for Slack.
Queue Slack messages from your terminal. Claude Code drives postqueen over MCP or the CLI, so scheduling happens in the session you already have open.
Register the postqueen MCP server once and Slack scheduling becomes a tool Claude Code can call. The plain CLI works too.
MCP supported# Add the postqueen MCP serverclaude mcp add --transport http postqueen \ https://api.postqueen.ai/mcp/YOUR_API_KEY # Then ask in your session:# "Queue three Slack messages for this# week, mornings at 9"Over MCP, scheduling and analytics show up as first-class tools. Over the CLI, every command returns JSON that Claude Code can chain reliably for Slack.
Tell Claude Code when your channels are busiest and it schedules messages into that window on Slack, day after day, without reminders.
Claude Code lists your connected channels before it posts, so messages land exactly where they should and announcements stay consistent.
Ask Claude Code for drafts only. They sit on the postqueen calendar unscheduled, so you can edit them and pick the time yourself, and nothing reaches your workspace members on Slack until you do.
Claude Code calls postqueen to list your connected channels and sees what Slack supports, so drafts start from real capabilities, not guesses.
Give it the brief. The agent writes Slack-shaped messages and proposes publish times that match when your workspace members are around.
Look over the queue on the postqueen calendar and change anything you want. postqueen publishes each post at its time, and Claude Code can pull the results after.
Claude Code reads these limits from postqueen before it composes, so a draft that would be rejected never reaches the queue.
Scheduling, AI drafts, analytics and team roles, in one guide.
Over MCP, registered once in Claude Code's own config so the Slack tools are there in every session. It also runs commands, so the CLI covers the same Slack messages when you would rather script them; both use the same API key.
Yes. Give it exact slots or a rule like mornings at nine and it sets publish times on the messages it creates, keeping your channels active on a steady rhythm.
Only if you ask it to. Tell it to save drafts and nothing is scheduled: the messages wait on the calendar until you set a time. Tell it to schedule, and they go out at the times you can see, which is the setup most people move to once they trust the output.
Yes. postqueen connects 30 channels, so Claude Code can turn the same brief into Slack messages plus adapted versions for every other channel you run.
No. The agent uses your regular API key and plan limits: unlimited posts on every plan, and channel counts from 5 on Creator up to uncapped on Ultimate.
Yes, once the app has been invited. Someone in the private channel invites the postqueen app, and from then on scheduled messages land normally. A missing invite is the most common reason a private channel post fails.
Yes. Select any mix of connected channels across your workspaces and postqueen delivers the message to each one. You can adjust the wording per channel before it goes out.
Queue this week's posts in minutes, or hand the whole thing to your favorite AI. postqueen keeps publishing either way.
Seven days free. Cancel in one click from settings.