Ship the feature. Post about it. Never leave Cursor.
The reason a release is worth posting about lives in the diff — not in a social scheduler you open on Friday and regret. Add PostMCP as an MCP server and Cursor can write the announcement where the work happened.
Setup, in full
- 1Settings → Features → MCP
Open Cursor’s MCP panel and choose “Add New MCP Server”.
- 2Type: command
Name it postmcpai. The command is npx -y @postmcpai/server.
- 3Environment variable
POSTMCPAI_API_KEY = your key from the PostMCP dashboard.
- 4Save
Sixteen tools register. Ask it to list your connected accounts to confirm.
{
"mcpServers": {
"postmcpai": {
"command": "npx",
"args": ["-y", "@postmcpai/server"],
"env": {
"POSTMCPAI_API_KEY": "pmcp_sec_•••"
}
}
}
}What developers actually use it for
Release notes → announcement
Cursor already has the diff and the changelog in context. Ask it to turn the last tag into a LinkedIn post and an X post, check both against their limits, and schedule them for tomorrow morning.
Ship-day thread
One prompt produces the announcement, the follow-up detail post and the “here is what we learned” post, all spaced across three days on the calendar.
Build it into your own tooling
The same tools are plain REST. A release script can call preflight_post then create_post directly, so publishing becomes part of CI rather than something you remember afterwards.
Prefer to wire it into CI rather than the editor? The same tools are plain REST.
Developer guideCursor integration FAQ
How do I add PostMCP to Cursor?+
Open Cursor Settings → Features → MCP, click Add New MCP Server, set the type to command and the command to npx -y @postmcpai/server. Add POSTMCPAI_API_KEY as an environment variable with a key from your PostMCP dashboard, then save. The tools appear in Cursor’s tool list.
What can Cursor actually do once it is connected?+
The full toolkit: read your queue and connected profiles, read brand kits, dry-run a post against every network’s limits, generate an image, create and schedule posts, reschedule, retry failures and delete. Sixteen tools in total, the same ones the dashboard uses.
Why post from an IDE at all?+
Because that is where the context is. The reason a release is interesting — what changed, what it fixes, what it took — is in the diff and the commit history, not in a social scheduler. Writing the post where the work happened produces better copy and removes the switch that usually means it never gets written.
Will it post automatically when I merge?+
Not unless you build that. Cursor asks before running mutating tools, and PostMCP schedules rather than fires by default. If you do want automation on merge, call the REST API from CI — preflight_post first, then create_post with a schedule.
Does this work in VS Code and other MCP-capable editors?+
Yes. The server is a standard stdio MCP server, so any editor or agent runtime that speaks MCP can register it the same way. Cursor is documented here because it is the most common, not because it is required.
Is my API key exposed to the model?+
No. It is set as an environment variable on the server process. The model sees tool names, the arguments it chose and the results — never the credential, and never your social OAuth tokens, which stay encrypted in the PostMCP backend.