# How to turn recent code changes into social draft ideas with MCP

> Let a coding agent inspect a bounded diff or changelog, identify user-visible changes, and save accurate social ideas as DunSocial drafts.

- Published: 2026-08-06
- Last updated: 2026-08-06
- Author: DunSocial
- Topics: mcp, how-to

---

A raw commit list is not a content plan. Many commits are refactors, tests or private operational work. Ask the coding agent to identify only user-visible changes and show its evidence before it drafts anything.

This workflow saves ideas as drafts. It does not publish from an unreviewed diff.

Search phrases: code changes to social posts, MCP developer marketing, git diff social media ideas, Claude Code launch draft, build in public automation.

## What you will do

- Bound the repository material the agent may inspect.
- Separate user-visible changes from internal work.
- Save a small set of evidence-backed draft ideas.

## Before you start

- An active DunSocial workspace with the intended social accounts already connected.
- An MCP client that supports Streamable HTTP and OAuth, such as Claude, ChatGPT, Cursor or Copilot Studio.
- A person who can review the final account, copy and time before publishing.
- A clean working tree or an explicit commit range, plus public release notes when they exist.

## Step by step

### 1. Define the review range

Point the agent at a merged pull request, tag range or named files. Explicitly exclude secrets, customer data and private issue discussion.

### 2. Ask for evidence

Require the file, test or public doc supporting each proposed user-visible change.

> Inspect this commit range. List only user-visible changes, who benefits, and the public-safe evidence for each. Do not write social copy.

### 3. Choose worthwhile ideas

A change is post-worthy when a user can understand what became possible or easier. Skip dependency bumps and implementation detail with no user consequence.

### 4. Save drafts in DunSocial

Ask for concise, platform-aware drafts and preserve limitations or migration requirements.

> Create DunSocial drafts for the two approved changes. Use the cited public facts, our personalization and relevant memory. Do not schedule or publish.

## Check before you finish

- The assistant names the correct DunSocial workspace and destination accounts.
- Every factual claim comes from the source material or saved workspace memory.
- The final action, timezone and returned post or draft IDs are visible.

## Where to go next

Review each draft beside the diff and public docs, then use the developer scheduling guide only after the release is actually available.

---

## About this document

This is the Markdown representation of https://www.dunsocial.com/blog/turn-recent-code-changes-into-social-draft-ideas-with-mcp. The HTML version of the same page is at the same URL. You can also request Markdown from any page by sending `Accept: text/markdown`.

Machine-readable summary of the whole site: https://www.dunsocial.com/llms.txt

## Company

- Product: DunSocial, https://www.dunsocial.com
- Legal entity: THISUX PRIVATE LIMITED, Chennai, Tamil Nadu, India
- Support: support@dunsocial.com
- Open the app: https://app.dunsocial.com/login