Cursor · one connector
Publish to social from Cursor.
The announcement usually gets written in the editor anyway. This is the part where it leaves the editor.
Shipping something and telling anyone about it are separated by a tab switch, and the tab switch is where the telling stops happening. With the server installed in Cursor, the agent that just wrote your changelog can put a version of it out — reshaped per network, checked against each ceiling — while you are still looking at the diff.
Installation is a deeplink or a few lines in your MCP configuration file, both on our MCP page, and the authorisation happens in a browser once. After that the tools appear alongside everything else the agent can reach, and nothing about your project configuration knows anything about your social accounts.
Publishing from Cursor
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.
Draft a short release note from the changelog and post it — not Instagram, no image for it
from CHANGELOG.md · three accounts
Drafted and checked. Before I send:
Say the word and it goes. Nothing is published until you answer — but there is no gate enforcing that, only me asking.
Where to add it in Cursor
~/.cursor/mcp.json, or the one-click install deeplink on the MCP page
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 Cursor can do once it is connected
Installs from a link
A deeplink or a short entry in your configuration file, both generated from the live server address rather than copied out of a document.
Announce without leaving the diff
The agent that just wrote your changelog can put a version of it out while the change is still on screen, which is the tab switch that usually kills the announcement.
The config holds only an address
Committing it shares nothing: authorisation belongs to your account and happens in your browser, so a teammate installing the same server connects their own accounts.
There is no review step
Nothing sits between an agent deciding to publish and the post being public, and on some networks a published post cannot be deleted through any API at all.
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 Cursor 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.
An editor agent will act, which is the point and the risk
An agent in an editor is built to take actions without stopping to ask, and that is exactly what makes it useful for this. It is also why the tools it gets here are shaped the way they are: publishing reports each network separately rather than as one success, a failed network can be retried without touching the ones that went out, and the tools that remove things say plainly which networks cannot be undone. Instagram, Threads and TikTok cannot have a published post deleted through any API, so on those, an accidental publish stays published — that is worth knowing before you point an autonomous agent at it.
A limitation of this product. Ours to fix. From documentation, checked 2026-08-09.
When this is the wrong tool
There is no approval step between the agent deciding to publish and the post going out. If your work needs somebody to review copy before it becomes public, that gate does not exist here and you would be relying on the agent asking first, which is not a guarantee anyone can make.
Questions people actually ask
How do I install it in Cursor?
Either the one-click deeplink on our MCP page or a short entry in your MCP configuration file. Both are generated from the live server address rather than typed into a document.
Do my teammates get access to my accounts?
No. The configuration holds only the server address; the authorisation belongs to your account and happens in your browser. Someone else installing the same server connects their own social accounts.
Can the agent post automatically when I merge something?
It can publish when you ask it to, including as a step in a longer task. It is not a CI trigger and does not watch your repository, so nothing goes out because a branch moved.
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.