Automate Dribbble with Cursor

Over MCP, registered once in Cursor'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 Cursor 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.

postqueen keeps a clean history of every shot it published and when, so you can compare timing and topics across your queue. Views, likes and saves for each shot live on Dribbble itself, and reading the two together shows what your audience responds to.

The usual causes are an expired Dribbble connection or a file outside the platform rules, like a wrong aspect ratio or an oversized upload. postqueen flags the failure in the calendar so you can reconnect or fix the file and retry.