Social posts from Cursor. One mcp.json entry, every network.
Add Postbroad to Cursor and ask the chat to turn a pull request or a changelog into posts for each network. Cursor asks before it runs a tool, and Postbroad previews every write first.
Connect Cursor in three steps.
Cursor uses the hosted Postbroad MCP server. There is nothing to install: you sign in in the browser and pick the brands.
- Add the entry to mcp.jsonPaste it into your project or global Cursor settings. It holds only the address, so it is safe to commit.
- Sign in and pick brandsThe first time the client connects, Postbroad opens a sign-in page in your browser. Sign in and choose the brands this connection may touch. There is no key to copy.
- Check the toolsOpen Settings, MCP, check that postbroad lists its tools, and ask: "List my Postbroad brands."
{
"mcpServers": {
"postbroad": {
"url": "https://app.postbroad.com/mcp"
}
}
}- Put the entry in ~/.cursor/mcp.json and Postbroad is there in every project.
Prompts to start with.
Each one only reads or proposes until you say yes. Paste one into a chat once Postbroad is connected.
Every channel you connect.
Cursor posts to the channels you connected in Postbroad, each with its own limits and its own state.
See every channelCursor questions.
Do I need to install anything?
No. The client connects to the hosted Postbroad MCP server over the web, and you sign in in the browser. There is no program to run and no key to paste.
Can the agent post without asking me?
Not by default. Each agent or connection has a mode: draft only, needs approval (the default), or auto within a budget. Scheduling and publishing always show a preview first.
Which networks can it post to?
The channels you have connected in Postbroad. Each network keeps its own limits and its own state. See every channel.
Can I take the access away?
Yes. Remove the connection in the client, or revoke its grant or its API key in Postbroad, and the access ends.
Other agents.
The same Postbroad, the same rules, from another client.