LinkedIn 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 LinkedIn.
Queue LinkedIn posts 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 LinkedIn 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 LinkedIn posts 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 LinkedIn.
Tell Claude Code when your followers are most active and it schedules posts into that window on LinkedIn, day after day, without reminders.
Images upload in the same postqueen call, so LinkedIn posts 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 LinkedIn until you do.
Claude Code calls postqueen to list your connected profiles and company pages and sees what LinkedIn supports, so drafts start from real capabilities, not guesses.
Give it the brief. The agent writes LinkedIn-shaped posts 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 LinkedIn tools are there in every session. It also runs commands, so the CLI covers the same LinkedIn posts 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 posts 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 posts 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 LinkedIn posts 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. The assistant drafts posts in your voice, tightens them to fit the 3,000 character limit and rewrites anything you highlight. Nothing publishes until you schedule it, and agents like Claude Code or Cursor can prepare a batch through the built-in MCP server.
LinkedIn traffic skews to weekdays and working hours, but the exact slot depends on where your audience works. Schedule similar posts into a few different slots for a couple of weeks, compare them in postqueen analytics, and keep the ones that land.
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.