PostNitro for Claude — the design step your pipeline is missing
You have already automated the writing. The part that still needs a human is the design: someone opens a tool, picks a template, applies the brand, exports. PostNitro's connector closes that gap — Claude renders the post in your brand and books the slot, in the same session that wrote it.
Scoped OAuth token, no API key in a dotfile, no MCP config to maintain. Available in Claude Code and Cowork as well as the apps.
Runs in
Claude Code, Cowork, apps
Auth
Scoped OAuth, revocable
Surface
35 MCP tools
Output
Rendered files or an editable design
Why the connector, rather than the raw API
The REST API and MCP server have been there all along. This is about what you stop having to operate.
No credential to store
The connector holds a scoped token tied to your workspace, so there is no API key sitting in a dotfile, a CI secret, or an MCP config you have to rotate. Revoke it from either side and it dies immediately.
One connection, every context
Connect on your account and the same tools are there in Claude Code, in Cowork sessions, and in the desktop and web apps. You are not maintaining a config per machine.
Brand fidelity is the hard part
Anything can post text. Applying the right client’s fonts, palette, logo and template to twenty slides without a designer is the step that usually breaks automation. That is the step this closes.
Reviewed, not a README URL
Directory connectors are reviewed by Anthropic before listing. For anyone who has to justify a new integration internally, that is a materially different conversation.
Where it actually runs
Claude Code and Cowork are the interesting ones — that is where a content pipeline stops being a chat and starts being a job that runs.
Claude Code
Generate posts from the terminal, inside a repo
Cowork
Long-running agent sessions can design and schedule
Claude desktop
Same account, same connector
Claude web
Add from the directory or Settings → Connectors
Claude mobile
Approve or reschedule away from your desk
What it does that a publishing API cannot
Every item is a tool the connector exposes. The distinction throughout: these design the post, they do not just transmit one.
Batch, not one-at-a-time
Feed a list of topics, article URLs or your own slide copy and get a deck per item. The credit cost is per slide, so a month of posts is one predictable number rather than an afternoon.
A brand kit per client
List, create and update brand kits programmatically. Agencies can onboard a client as a script — fonts, palette, logo, headshots — and every post after that comes out right by default.
Save defaults once
Template, brand, AI preset and output format persist between sessions, so a request collapses to one line instead of restating the whole configuration every time.
Design and schedule in one call
One request writes the deck, renders it and books the slot across LinkedIn, Instagram, TikTok and Threads. Nothing to poll, no second step to stitch together.
Own the calendar from code
List, create, update and delete scheduled posts and drafts. Reconcile against your own planning system rather than keeping two calendars in your head.
Hand the draft back to a human
Ask for a design instead of a rendered file and the deck opens in the editor. The agent does the first ninety percent; a person approves the last ten. That is usually the only workflow a client will sign off on.
When you want the layer underneath
The connector is the managed path. If you are running in CI, or driving this from a language Claude is not in, the MCP server is a hosted endpoint any MCP client can point at, the CLI is JSON in and JSON out, and the REST API is the layer both are built on. Same credits, same tools, same account.
Thirty seconds, once per account
After this the setup is not something you think about again.
1
Add the connector
From the directory listing, or Settings → Connectors inside Claude. Nothing to install locally.
2
Approve the scope
Sign in to PostNitro and approve access to the workspace you want. The token is scoped to that workspace and nothing else.
3
Set your defaults, then forget them
Tell Claude which template and brand to use by default. Every later request inherits them, so the interesting part of the prompt is just the content.
What this looks like in practice
Real requests from a pipeline, not a demo script.
In a batch
“Take these six blog URLs and make a LinkedIn carousel from each, using the Acme brand kit.”
“Regenerate slide 3 across all of them — the stat is out of date.”
“Same deck again for the Contoso brand kit, and give me the designs rather than PNGs.”
Across a calendar
“Spread these eight posts over the next four weeks, Tuesdays and Thursdays at 9am, LinkedIn and Instagram.”
“What is queued for Acme next week, and which of it is still a draft?”
“Move everything scheduled after Thursday back by a week — the launch slipped.”
Per client
“Create a brand kit for this client from their site — palette, fonts, logo.”
“Which social accounts are connected, and which workspace is each in?”
“Set the 4:5 template and the Acme brand as the defaults for this session.”
What a security review will ask
Scoped to one workspace
The token reaches your templates, brands, designs, scheduled posts and the accounts you connected. Not your machine, not your other workspaces, not your other tools.
Confirmation before it acts
Claude asks before running a tool, so a batch job cannot quietly publish or delete something while you are reading. You see the call before it happens.
Revoke from either end
Remove the connector in Claude, or revoke access in PostNitro. The token stops working immediately — there is no key still valid somewhere you forgot about.
Not training data
We do not train AI models on your content. Work created through the connector is treated exactly like everything else in your account.
What it costs to run
Claude, on any connector-capable plan
Added from the directory or Settings → Connectors. Claude Code and Cowork pick up the same connection.
Embed API credits
The connector runs on the same credits as the REST API and MCP server, so it needs the Embed API add-on on a paid plan or a Plus plan that bundles them. Import costs one credit per slide, AI generation two. There is no free tier for programmatic access.
Connected accounts, for publishing
Connect LinkedIn, Instagram, TikTok or Threads once per workspace and Claude can schedule to them. Without it you still get rendered files back, which is enough if something else does your posting.
Frequently Asked Questions
Close the design gap
Connect once, set your defaults, and stop opening a design tool by hand.
Open the directory listing