Claude · one connector
Publish to social from Claude.
Two settings screens to connect, then the assistant you already think out loud with can publish what you decided on.
Claude’s connector setup is the shortest of any client here: settings, connectors, add, paste the address. From then on the same tools are available in every conversation, and asking for a post to go out is a sentence rather than a workflow. The authorisation happens in a browser window, once.
What Claude tends to be used for makes a difference to what this is like. Long back-and-forth about how something should be phrased ends with a version worth publishing, and at that moment the gap between the draft and the post is a single instruction rather than a context switch into another tool and a fresh round of reshaping.
Publishing from Claude
Drawn rather than captured — but the outcomes are the ones this product really produces, including the network that could not be confirmed.
Set me up — what do you need?
Just the accounts. Connect them in the browser once and I can publish from here after that.
Done, connected
I will tell you before publishing if a network cannot take what you wrote.
Good. Drafting the launch note now
Send it over and I will check it before anything goes out.
Right, that version is good. Send it to everywhere except Instagram
three accounts selected · no media
Three of them, and none of the three needs a picture:
All three are out. Instagram was left alone as you asked — it would have refused this anyway, having no image.
Where to add it in Claude
Settings → Connectors → Add custom connector
The address to paste is on the MCP page, printed from live configuration rather than typed into a document — so it cannot be out of date here while being correct there.
What Claude can do once it is connected
Two screens and a browser tab
The shortest setup of any client here — settings, connectors, add, paste, authorise. Nothing to install and no file to edit.
From the argument to the post
The version you finally agreed on is one instruction away from being published, instead of being copied into another tool and reshaped again by hand.
Ask how it did
Engagement reads back into the same conversation for the networks that report it, and stays visibly empty for the ones that do not.
One set of accounts per person
Connectors are configured for an account rather than a project, so there is no way to let one person publish while another only drafts.
How it works
Connect once
~2 minLink the accounts you use in a browser. OAuth, no passwords typed into a chat, no API keys to paste anywhere.
ChatGPT
Claude
Cursor
Ask, in your own words
one sentenceTell Claude to publish to every network you picked, now or on a day you name. No dashboard, no tab switch.
Read the receipt
per networkOne line per network — what landed, what failed and why, and what genuinely could not be determined.
For a while, we sent Claude users back to ChatGPT
The consent screen you see when authorising is shared by every client, and the button at the end of it said “Return to ChatGPT” — to everybody, including the people who had arrived from Claude, Cursor or a terminal. It was a hardcoded string in a flow that had only ever been tested from one direction, and it is a good example of what a second integration surfaces that a first one hides. The screen now names the client you actually came from. Mentioning it here because a page claiming a flawless integration is worth less than one that tells you what got fixed and when.
A limitation of this product. Ours to fix. Measured on a live account, 2026-08-07.
When this is the wrong tool
Connectors are configured per account rather than per project, so everyone sharing a workspace shares the connected social accounts. If you need one person to be able to publish and another only to draft, that separation does not exist here yet and you should not design a process around it.
Questions people actually ask
Where do I add the connector in Claude?
Settings, then Connectors, then Add custom connector. Paste the address from our MCP page and authorise in the browser window that opens.
Is this the same integration as Claude Code?
The same server and the same tools, connected a different way — one through a settings screen, one through a single terminal command. Accounts and scheduled posts are shared between them, because they are one account.
Can Claude read back how a post performed?
For the networks that report engagement, yes — asked and answered in the conversation. Where a network reports nothing we say so instead of showing a zero, and where an outcome genuinely could not be determined it is labelled unknown rather than guessed at.
Something else? Ask us — a person answers.
Read next
Start where you already work.
Connect an account and post your first update in about two minutes. The first 30 deliveries each month are free.
Posts go out through each network’s official API — not scraping.