Dribbble 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 Dribbble.
Queue Dribbble shots 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 Dribbble 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 Dribbble shots 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 Dribbble.
Tell Claude Code when your followers are most active and it schedules shots into that window on Dribbble, day after day, without reminders.
Images upload in the same postqueen call, so Dribbble shots arrive with their media in place instead of a bare link.
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 followers on Dribbble until you do.
Claude Code calls postqueen to list your connected profiles and sees what Dribbble supports, so drafts start from real capabilities, not guesses.
Give it the brief. The agent writes Dribbble-shaped shots and proposes publish times that match when your followers 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 Dribbble tools are there in every session. It also runs commands, so the CLI covers the same Dribbble shots 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 shots it creates, so your followers see them at the right moment.
Only if you ask it to. Tell it to save drafts and nothing is scheduled: the shots 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 Dribbble shots 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.
You connect the same Dribbble account you already publish from. postqueen signs in through the official API with OAuth, so you authorize on Dribbble itself and never hand over your password.
Yes. Send the same artwork to Instagram, Pinterest, X, LinkedIn and any of the 30 supported channels, with a caption tuned per network before anything goes live. The Dribbble version keeps its tags while the social versions get their own copy.
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.