Posta is for developers, AI agents, automation engineers, and the creators they support — anyone who treats social posting as a pipeline rather than a manual task. Plug Posta into an MCP server, an n8n workflow, a Claude Code skill, or the REST API and let the agent do the rest.

What is the Posta MCP server?

Posta ships an MCP (Model Context Protocol) server so any MCP-capable client — Claude Desktop, Claude Code, Cursor, or your own agent — can create, schedule, and publish social media posts as tool calls. One install (npx posta-mcp), one token, every supported network.

Does Posta work with n8n?

Yes. The n8n-nodes-posta community node turns every Posta endpoint into a typed n8n node. We publish ready-to-fork workflows for blog-to-social, YouTube-to-social, product launch campaigns, and LinkedIn carousel generation — wire any trigger to Posta in a few clicks.

Can I post to social media from Claude Code or the terminal?

Yes. The Posta Claude Code skill lets you create, schedule, and publish posts straight from your terminal or IDE using natural-language slash-commands. No dashboard required, no context-switch from your editor.

Does Posta publish directly to social networks?

Yes. Posta publishes directly to LinkedIn, TikTok, Instagram, YouTube, Pinterest, Facebook, Bluesky, and Threads via each platform's official API, and fires HMAC-signed webhooks back to your agent when posts go live — so closed-loop pipelines know exactly when they can act on a result.

How is this different from Buffer, Hootsuite, or Later?

Those tools are dashboards designed for humans clicking buttons. Posta is API-first and agent-first: full public REST API on every paid tier, HMAC-signed outbound webhooks, an MCP server, a Claude Code skill, and an n8n community node — none of which the dashboard-led incumbents ship.

Can I influence the roadmap?

Yes. Early users help shape integrations, workflow and pricing. Tell us how you work and what your current agent stack looks like when you request access.

Post to LinkedIn from the terminal with Claude Code

Most "post to LinkedIn" tooling assumes you’ll switch to a browser tab. The Posta Claude Code skill assumes the opposite — that you’re in your terminal anyway, that you’d like to stay there, and that your editor’s agent is the best place to draft. Here’s the 90-second setup and a few patterns that make it worth the install.

Setup

You need three things: a Posta account, a connected LinkedIn account, and Claude Code. If you have all three, this is the whole install — one command in Claude Code, pointing at the skill repo:

# In Claude Code:
/install-skill https://github.com/STGime/posta-skill

# Once installed, Claude can call Posta in natural language —
# no Posta-specific slash-commands required.

The skill is natural-language driven: there are no /posta create or /posta schedule commands to memorize. You ask Claude in plain English ("schedule a LinkedIn post about…") and the skill handles authentication, calls Posta under the hood, and reports back. The full reference is on the CLI posting landing page.

Pattern 1 — One-shot draft

You finished a piece of work and want to post about it. The terminal is open, Claude Code is up. Just ask:

"Draft a LinkedIn post: 'Shipped Posta v2.1 — per-platform caption
limits + batch media endpoint. Matters for anyone running multi-network
automations because…' Save it as a draft so I can review."

Claude takes the prompt, calls Posta to create the draft on LinkedIn, returns the draft ID and a preview URL. Open the URL in a browser when you want to review, or ask Claude to schedule it inline.

Pattern 2 — Draft from the repo state

A more agentic pattern: hand Claude Code the repo and ask it to find what’s worth posting:

"Look at the git log since last Monday. Pick the most ship-worthy
commit. Draft a LinkedIn post about it, schedule it for Tuesday 9am
CET, save as draft so I can review."

Claude reads the log, picks a commit, drafts the post, and calls Posta to schedule it as a draft. You review and approve in the Posta dashboard, or ask Claude to list scheduled drafts and approve from the terminal.

Pattern 3 — Carousel from a README

For a longer-form release post: ask Claude to build a LinkedIn carousel directly from a README or CHANGELOG. The skill calls Posta’s carousel endpoint, which composites the slides as a PDF and ships it to LinkedIn’s document API. Walked through end-to-end in the blog-to-LinkedIn-carousel workflow.

Why not the MCP server?

You can also install the Posta MCP server into Claude Code. The difference: the skill is a focused wrapper around the common posting workflows (draft, schedule, list, publish), tuned for Claude Code specifically. The MCP server exposes Posta’s full tool surface — createPost, schedulePost, listAccounts, getPostStatus, listMedia, uploadMedia, listPosts — to any MCP client, including Claude Code. Most users start with the skill, add the MCP server when they outgrow it.

Combine with autonomous mode

Claude Code’s autonomous mode means you can wire the skill into a longer-running task. A common pattern in our repo: a "ship the week" prompt that picks the top three commits, drafts a post per audience (LinkedIn long-form, Bluesky short-form), and schedules all three — without context-switching from the terminal.

Where to go from here

The skill is one of four surfaces — see MCP vs n8n vs Claude Code for the decision framework, or jump straight to the CLI posting landing page for the install and full command reference. 14-day free trial covers all four surfaces and every supported network.