---
source: https://autoadify.com/blog/cursor-build-in-public-daily-posts
title: "How to Build in Public From Cursor: Post What You Shipped Today, With a Screenshot (Setup + 4 Prompts)"
author: Rupa T
published: 2026-11-05
updated: 2026-11-05
category: AI & Automation
tags: Cursor, MCP, Build in Public, Developer API, X (Twitter), Scheduling
reading_time: 6 min
---

# How to Build in Public From Cursor: Post What You Shipped Today, With a Screenshot (Setup + 4 Prompts)

> Building in public works because it's consistent, and it fails because posting is a context switch. With Autoadify connected to Cursor, the end-of-day post is written from your own diff, the screenshot comes straight from your project folder, and it's scheduled before you close the editor.

## Quick Answer

**Add Autoadify to `~/.cursor/mcp.json` with the URL `https://mcp.autoadify.com/mcp`, click Connect in Cursor's MCP settings and sign in. At the end of the day, ask Cursor to summarise what you shipped from the git log, write a short post, upload a screenshot from your project folder, and schedule it to X, Threads and Bluesky. Needs Autoadify Pro.**

## Cursor + Autoadify at a Glance

| Field | Value |
| --- | --- |
| Best for | Indie hackers and small teams building in public |
| Where it runs | Cursor's MCP settings, or mcp.json in your home folder or project. |
| Autoadify plan | Pro ($29/mo) and above, for MCP access |
| What Cursor does | Reads today's commits, writes the post, uploads a local screenshot, schedules it |
| Networks | X, Threads, Bluesky and LinkedIn suit build-in-public; all nine networks work |
| Team setup | A project-level `.cursor/mcp.json` shares the server; each person signs in with their own account |

## Why Post From the Editor

Every build-in-public account that stalls stalls the same way: the posting is a separate job. You finish at 7pm, open X, try to remember what you did, take a screenshot, crop it, write something, and decide it's not interesting enough. Tomorrow you skip it.

Cursor already knows what you did today: it's in the git log and the files you touched. Writing the post from there takes one prompt, and the screenshot is a file it can upload directly.

## 1\. Connect

1.  Add the entry below to ~/.cursor/mcp.json (or .cursor/mcp.json in a project).
2.  In Cursor's MCP settings, click Connect next to autoadify.
3.  Sign in to Autoadify in the browser and approve.

```
{
  "mcpServers": {
    "autoadify": { "url": "https://mcp.autoadify.com/mcp" }
  }
}
```

More: [Autoadify in Cursor](/mcp/cursor).

## 2\. The end-of-day routine (4 prompts)

> **Prompt 1.** Look at today's commits on this branch. In two sentences, what did I ship that a user would notice? If nothing user-facing, what did I learn or fix that another developer would find useful?

> **Prompt 2.** Write a build-in-public post from that: first line is the result, not "Day 47". Under 280 characters for X, a slightly longer Threads version, and a Bluesky version under 300 characters. Lowercase is fine, no hashtags, no emojis.

> **Prompt 3.** Upload ./screenshots/today.png to my Autoadify media library and attach it to all three.

> **Prompt 4.** Schedule all three for 8:30am tomorrow, when my followers are on their commute.

Cursor uses `create_media_upload` and `complete_media_upload` to send the screenshot from your disk, and `create_post` to schedule. Posting the next morning instead of at 7pm gives the post a better slot and gives you a night to delete it.

## Make it a habit

-   **Save the prompts as a Cursor rule or a command** so the routine is one line.
-   **Keep a screenshots folder** in the project (and in .gitignore). A screen recording works too: upload an .mp4 the same way.
-   **Once a week, ask for a recap**: _"List this week's scheduled posts and their live links, and write a Friday thread linking the three that did best."_

**Post tonight's progress before you close the editor:** [start with Autoadify](https://app.autoadify.com/?utm_source=blog&utm_medium=article&utm_campaign=feature&utm_content=cursor-build-in-public-daily-posts) and connect Cursor.

## Honest Limits

-   **Commit messages aren't a story.** If your log says "fix", "wip", "fix again", the summary will be thin. Tell Cursor what you were trying to do.
-   **Check screenshots for secrets.** API keys, customer emails and internal URLs end up in dev screenshots. Look before prompt 4.
-   **"Did best" needs live data.** Autoadify can return each post's status and link; engagement numbers vary by network.
-   **It's your voice on the line.** Build in public works because it sounds like a person. Edit the draft until it sounds like you.

## Frequently Asked Questions

### Does it work in Cursor's agent mode?

Yes. Once connected, Autoadify's tools are available to Cursor's agent like any other MCP server.

### Can my team share the setup?

Commit `.cursor/mcp.json` to the project. Each person still clicks Connect and signs in with their own Autoadify account.

### Can it post a video?

Yes. Upload a screen recording the same way as a screenshot and attach it.

### Which networks are best for building in public?

X, Threads and Bluesky for daily updates; LinkedIn for weekly recaps.

### Do I need an API key?

No. Cursor signs in with OAuth. API keys are for scripts and CI.

### Which Autoadify plan?

Pro ($29/mo) and above include the MCP server. See [pricing](/pricing).

## The Bottom Line

Building in public is a consistency game, and consistency dies on context switches. With Autoadify in Cursor, the daily post is four prompts at the end of the day, written from your own commits, with a real screenshot attached. [Connect Cursor](https://app.autoadify.com/?utm_source=blog&utm_medium=article&utm_campaign=feature&utm_content=cursor-build-in-public-daily-posts).

---

_Source: https://autoadify.com/blog/cursor-build-in-public-daily-posts · Autoadify — AI social media automation._