How to Post Release Notes to Social Media from Cursor

You can post release notes to social media from Cursor by adding the PostAxis MCP server to mcp.json and signing in once. Cursor's Agent can then summarise the branch you are on, write an announcement for each network and schedule it to X, LinkedIn, Telegram, Threads and the rest, all from the same window as the code. This is for developers who finish a feature at 6pm and would rather not open four apps to tell people about it.

What you can automate with Cursor

Cursor's Agent already has your repository open. It can read files, run git commands in the terminal and call MCP tools. That covers most release communication.

• Branch summaries: "what changed on this branch" as an X post scheduled for this evening.
• PR write-ups as drafts: a LinkedIn post about a performance PR, saved for review.
• Release posts with a screenshot: one release, a different caption for X, LinkedIn and Telegram, the same image attached.
• Monthly roundups from merged PRs, planned and validated before scheduling.
• Team-wide setup: commit the config to the repo so every engineer on the project has the same PostAxis tools.

What you need

• A PostAxis account. Sign up at app.postaxis.io; every plan has a 7-day free trial and includes MCP access with OAuth sign-in.
• Your social accounts connected under Accounts in PostAxis.
• Cursor, using the Agent chat.
• The PostAxis API add-on only if you want to authenticate with an API key instead of signing in.

How to connect Cursor to PostAxis (step by step)

It takes about two minutes.

1. Create your PostAxis account and connect your social accounts. Open Accounts and connect Instagram, TikTok, YouTube, X, LinkedIn, Facebook Pages, Threads or Telegram channels. The agent can only post to accounts connected here, and it never sees your social media passwords.

2. Open your MCP config. Use ~/.cursor/mcp.json to have PostAxis in every project, or .cursor/mcp.json inside one project. You can also go to Cursor Settings → MCP and click Add new MCP server; menu names can shift between Cursor versions.

3. Add the PostAxis block. If the file already has mcpServers, add only the postaxis entry inside it.

{
  "mcpServers": {
    "postaxis": {
      "url": "https://postaxis.io/api/mcp"
    }
  }
}

4. Sign in. Open Cursor Settings → MCP. PostAxis shows a Login (or Needs login) button. Click it, sign in to PostAxis in your browser and approve.

5. Check it works. PostAxis turns green in the MCP list with 11 tools. If it stays red, toggle it off and on or reload the window. Then ask the Agent:

Which accounts can you post to?

The Agent calls list_accounts and lists your profiles. Cursor asks before running each tool unless you have allowed it to run tools automatically.

4 workflows you can copy

Summarise this branch as an evening X post

The simplest win. You just finished the work, the diff is right there, and posting at 18:00 catches people at the end of their day.

Summarise what changed on this branch compared to main, from a user's
point of view. Write one X post under 250 characters: what you can do
now that you couldn't before. No hashtags. Schedule it for 18:00
Europe/Paris today.

The Agent runs git diff main...HEAD or git log in the terminal, writes the post, calls list_accounts to find your X profile and create_post with the schedule time. You get something like: "Scheduled an X post for 18:00 today (189 characters) summarising the three changes on this branch."

Turn a performance PR into a LinkedIn draft

Performance work is invisible unless you explain it. LinkedIn gives you up to 3,000 characters to do that properly, and a draft lets you check the numbers before anyone sees them.

Read @docs/perf-notes.md and the changes in this branch. Write a LinkedIn
post about the performance work: the problem users had, what we changed
in plain words, and what they will notice. Only use numbers that appear
in the notes. Save it as a draft, don't schedule it.

Referencing a file with @ puts it in the Agent's context. The Agent calls create_post as a draft, which shows up under Drafts in PostAxis for you to edit and schedule. Telling it to use only numbers from your notes stops it from guessing.

Ship a release with a screenshot on three networks

When a release has a visual change, one good screenshot does more than a paragraph. PostAxis does not generate images, so you bring the screenshot and the Agent attaches it.

Release v2.0 is out. Use the screenshot at
https://example.com/blog/v2-dashboard.png. Write a punchy one-liner for X,
a short story for LinkedIn (3 paragraphs), and the full changelog from
@CHANGELOG.md for Telegram. Attach the screenshot to all three and
schedule them together for 14:00 America/Los_Angeles today.

The Agent calls upload_media_from_url to pull the image into your PostAxis media library, checks get_platform_rules, and creates one post with a caption override per account. Media is shared by the whole post, so the screenshot goes everywhere. Watch Telegram here: with media attached, the caption limit drops from 4,096 to 1,024 characters, so a long changelog may need trimming or a link. PostAxis will reject it before saving if it is too long, and the Agent can shorten it.

If the screenshot is only on your machine, ask the Agent for an upload link instead. It calls create_upload_link, which returns a one-time link for uploading a local file.

Plan a monthly roundup from merged PRs

Once a month, turn everything you merged into a short series instead of one wall of text.

List the PRs merged to main in September (use the gh CLI). Group them into
4 themes. Plan 4 posts for X and Threads, one per theme, Tuesday to Friday
next week at 11:00 Europe/London. Validate the plan and show me a table
with the date, networks and text before scheduling.

If the GitHub CLI is installed and signed in, the Agent can run gh pr list itself; otherwise paste the list in. It then calls create_posts_bulk with validate_only set to true. PostAxis checks every post and saves nothing. After you approve the table, the Agent sends the same batch for real. Bulk calls take up to 50 posts and are for scheduling, not publishing immediately.

Network limits Cursor works within

Videos must be MP4 or MOV, 3 to 300 seconds, in 16:9, 9:16, 4:3, 3:4 or 1:1, and a post holds either images or one video, never both.

PostAxis checks every post against these rules before it is saved. If the Agent writes an X caption that is too long, or attaches media Telegram can't caption that long, the call fails with a clear error and the Agent fixes it in the same chat. You never find a broken post in the calendar later.

Tips for better posts

• Put your voice in a project rule. Cursor supports project rules (in recent versions under .cursor/rules). A short "Social posts" rule with your audience, tone, banned words and hashtag policy keeps every announcement consistent.
• Share the setup with your team. Commit .cursor/mcp.json to the repository. Everyone who opens the project gets PostAxis, and each person signs in to their own PostAxis account.
• Keep tool approval on for posting tools. Auto-running tools is handy for reading files; for create_post and delete_post, seeing the call before it runs is worth the extra click.
• Validate first when there is more than one post. Ask for "validate and show me a table". It costs nothing.
• Say the timezone. "18:00 Europe/Paris", not "6pm". Without one, the agent uses the timezone it was told or UTC.
• Use drafts for anything with numbers or promises. Performance claims, pricing and dates should be read by a human.

Troubleshooting

PostAxis stays red or shows Needs login. Click Login in Cursor Settings → MCP and approve in the browser. If it still fails, toggle the server off and on or reload the window. Cursor picks up mcp.json changes after a reload.

401 Unauthorized or "sign in again". The sign-in expired or was revoked. Log in again from the MCP settings. With an API key, check it is still active under Settings → API keys.

The Agent says no accounts are connected. Connect at least one social account under Accounts in PostAxis. If you use several workspaces, tell it which: "use my Acme workspace".

A post was rejected before saving. PostAxis checks caption length, media count, video length and format first. The error says what to change. Ask the Agent to fix it.

Posts are scheduled at the wrong time. Put the timezone in the prompt, for example "9:00 Europe/Berlin".

FAQ

Can Cursor post to social media?

Yes. Cursor's Agent can call any MCP server in mcp.json. With PostAxis added, it can draft, schedule, publish, edit and delete posts on Instagram, TikTok, YouTube Shorts, X, LinkedIn, Facebook Pages, Threads and Telegram channels.

Should I use the global or project config in Cursor?

Use ~/.cursor/mcp.json to have PostAxis in every project, or .cursor/mcp.json to share the setup with your team in one repository. Each person signs in to their own PostAxis account either way.

Do I need to restart Cursor?

Cursor picks up mcp.json changes after a reload. The first PostAxis tool call, or the Login button in the MCP settings, opens the sign-in page.

Can I use an API key instead of signing in?

Yes. Add a headers object with "Authorization": "Bearer YOUR_API_KEY" to the postaxis entry. API keys need the PostAxis API add-on.

Does Cursor see my social media passwords?

No. Social accounts are connected inside PostAxis. Cursor only gets a PostAxis sign-in, which you can revoke at any time under Settings → API keys → Connected agents.

Is it free?

MCP access with OAuth is included in every PostAxis plan, and every plan starts with a 7-day free trial.

Set it up from the Cursor agent page, check the MCP server reference for every tool, and read the complete guide to AI agents for social media for how it all fits together. Working in other editors too? See Windsurf or Claude Code. Then start your free trial and announce your next branch before you close the laptop.