Discord 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 Discord.
Queue Discord 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 Discord 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 Discord 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 Discord.
Tell Claude Code when your servers and channels are busiest and it schedules messages into that window on Discord, day after day, without reminders.
Claude Code lists your connected servers and 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 server members on Discord until you do.
Claude Code calls postqueen to list your connected servers and channels and sees what Discord supports, so drafts start from real capabilities, not guesses.
Give it the brief. The agent writes Discord-shaped messages and proposes publish times that match when your server 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 Discord tools are there in every session. It also runs commands, so the CLI covers the same Discord 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 servers and 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 Discord 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. Pick any combination of connected servers and channels when composing and postqueen fans the message out to all of them. You can tweak the copy per destination before anything publishes.
The usual causes are the bot losing Send Messages or Attach Files permission in that channel, the bot being removed from the server, or a file that exceeds the server's upload cap. postqueen flags failed posts so you can fix the permission and retry.
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.