# How to schedule social media posts from Codex with MCP

> Connect DunSocial’s hosted MCP in Codex, verify your workspace, draft with AI Memory, then schedule with human confirm. 53 tools included at USD 20/mo.

- Published: 2026-09-16
- Last updated: 2026-09-16
- Author: Sanju (Founder & CEO @ DunSocial)
- Topics: mcp, codex

---

<script>
	import { CodeSnippet, RelatedPost } from '$lib/components/content';
</script>

Codex can call hosted MCP tools from the ChatGPT desktop app, the Codex CLI, & the IDE extension. The useful how-to is not "paste a caption into a coding agent."

It is add DunSocial’s hosted MCP, finish OAuth, verify the workspace, draft with **AI Memory**, then schedule with **human confirm**, while you stay in the same agent loop that ships product updates.

## Short answer

Add DunSocial’s hosted MCP in Codex using `https://api.dunsocial.com/api/mcp` (Streamable HTTP), complete browser OAuth for your workspace (prefer OAuth over pasted tokens), and verify with a read-only account list before drafting.

Ask Codex to draft in your saved voice via **AI Memory**, show copy, destinations, time, & timezone, then confirm. DunSocial keeps **human confirmation** in front of publish for AI-written work.

The hosted MCP exposes **53 tools** for posts, drafts, memory, media, workspaces, & personalization, included in the **USD 20/mo** or **USD 192/yr** plan (**14-day** trial, no card; **1** seat included; extra seats USD 8/mo).

Posts land on the same calendar as the web app, CLI, Claude, ChatGPT, Grok, & Cursor flows, tagged MCP. Prefer Claude or ChatGPT connectors when those are your daily clients; prefer the CLI in a repo shell; use Cursor when that is your agent IDE. See [/mcp](/mcp).

| Step | Action | Surface |
| --- | --- | --- |
| 1 | Add hosted MCP URL `https://api.dunsocial.com/api/mcp` as Streamable HTTP | Codex MCP settings, CLI, or config.toml |
| 2 | Browser OAuth: sign in, pick workspace, grant scopes | DunSocial OAuth (`codex mcp login` or Authenticate) |
| 3 | Read-only verify: list accounts & name the workspace | Hosted MCP tools |
| 4 | Draft with Memory, show copy/time/timezone, confirm, then schedule | Same calendar as web & CLI |

Soft CTA: open [/mcp](/mcp), or start a [14-day trial](https://app.dunsocial.com/login) and connect from Codex the same day. Sibling how-tos: [Claude](/blog/schedule-social-posts-from-claude-mcp), [ChatGPT](/blog/schedule-social-posts-from-chatgpt-mcp), [Grok](/blog/schedule-social-posts-from-grok-mcp).

## Prerequisites

Before Codex can schedule anything useful:

1. A DunSocial account on the USD 20/mo or USD 192/yr plan (or an active 14-day trial).
2. Social networks connected in the DunSocial web app first. MCP cannot create network logins for you.
3. A Codex client with MCP support: ChatGPT desktop app, Codex CLI, or IDE extension. Those clients share MCP configuration for the same Codex host. Labels can drift; verify the live [OpenAI Codex MCP docs](https://learn.chatgpt.com/docs/extend/mcp) if menus moved.

If MCP servers are unavailable on the Codex surface you are using, stop and use the [web app](https://app.dunsocial.com/login), the [CLI](/cli), or another supported client from [/agents](/agents) instead of inventing a different auth path.

## Add the DunSocial MCP connector in Codex

DunSocial’s hosted endpoint is the same URL every sibling client uses:

<CodeSnippet
	label="url"
	highlight={false}
	code={`https://api.dunsocial.com/api/mcp`}
/>

Prefer **OAuth**. Do **not** paste a long-lived access token into chat. Do **not** invent an Authorization-header path for DunSocial unless product docs say so.

**ChatGPT desktop app:** Open **Settings**, then **MCP servers**, then **Add server**. Name it `DunSocial`, choose **Streamable HTTP**, paste the URL, save, & restart when asked. When the list shows OAuth is required, select **Authenticate**, finish browser sign-in, choose your workspace, & grant scopes.

**IDE extension:** Open the gear menu, select **MCP servers**, then **Add server**. Same pattern: name, Streamable HTTP, URL, save, restart if prompted, then **Authenticate**.

**Codex CLI:**

<CodeSnippet
	label="cli"
	code={`codex mcp add DunSocial --url https://api.dunsocial.com/api/mcp
codex mcp login DunSocial
codex mcp list`}
/>

In the Codex TUI, `/mcp` shows active servers. Desktop, CLI, & IDE share `~/.codex/config.toml` (or a project-scoped `.codex/config.toml` on trusted projects), so you configure once per host. Optional Streamable HTTP shape:

<CodeSnippet
	label="toml"
	highlight={false}
	code={`[mcp_servers.DunSocial]
url = "https://api.dunsocial.com/api/mcp"`}
/>

Then run `codex mcp login DunSocial`. Ask before approving OAuth on someone else's behalf, and never type another person's password. Product overview: [/mcp](/mcp). Agents: [/agents](/agents).

## Verify workspace before you write

After authorization, start with a read-only request:

<CodeSnippet
	label="prompt"
	highlight={false}
	code={`List my connected social accounts. Name the DunSocial workspace. Do not create or change anything.`}
/>

If the workspace is wrong or expected accounts are missing, stop. Connect or switch those accounts in the DunSocial web app, then return to Codex. MCP uses the accounts already linked to the workspace you approved in OAuth.

Why this step matters: coding agents are fast. A wrong workspace can schedule into the wrong brand calendar. Thirty seconds of verify saves a cleanup later. The Claude, ChatGPT, & Grok how-tos lead with the same habit.

## Draft with Memory, then schedule with confirm

Give Codex a source you trust: a release note, changelog, PR summary, or approved campaign brief. Ask for a draft that uses your saved **AI Memory** & **Voice Presets**, then preview before anything is timed.

<CodeSnippet
	label="prompt"
	highlight={false}
	code={`Draft an X thread and a LinkedIn post in my DunSocial voice.
Show the copy, destinations, time, and timezone. Do not schedule until I confirm.`}
/>

Review exact copy, destinations, time, timezone, & media. When ready, tell Codex to schedule. DunSocial requires **human confirmation** before an MCP-created post can publish, even inside a coding session.

Scheduled work lands on the same calendar as the web app, tagged **MCP**. Draft-only work stays editable in the web app. Extra brands are separate **USD 20** workspaces.

## What the 53 tools cover (high level)

DunSocial hosted MCP exposes **53 tools**. You do not need to memorize every name:

| Group | What Codex can do |
| --- | --- |
| Posts | List, get, schedule, publish now, threads, reschedule, cancel, delete |
| Drafts | List, get, create, update, delete |
| Memory | Collections, save, batch save, semantic search, update, delete |
| Media | List, upload, complete, delete |
| Workspaces | List, details, members, social accounts, Pinterest boards |
| Personalization | Get & update the workspace AI voice profile |

Full tool map: [/mcp](/mcp).

<RelatedPost slug="best-social-media-mcp-servers-2026" />

Related: [best AI social media scheduler for Cursor agents](/blog/best-ai-social-media-scheduler-for-cursor-agents).

Platforms on the same plan: X, LinkedIn, Instagram, Threads, Bluesky, Reddit, Pinterest, YouTube Shorts, Discord, & Slack; TikTok limited beta. That is **10 generally available networks**, including Discord & Slack.

Connect accounts in the app first, then schedule from Codex against that shared calendar.

## Codex vs Claude vs ChatGPT vs Grok vs Cursor vs CLI

The hosted MCP URL is the same everywhere. Only the client connector UI changes.

| Path | When to use it | Entry |
| --- | --- | --- |
| Codex hosted MCP (this page) | You already ship work in Codex / coding-agent workflows | [/mcp](/mcp) |
| Claude hosted MCP | Claude.ai / Desktop / mobile is your daily client | [Claude how-to](/blog/schedule-social-posts-from-claude-mcp) · [/claude](/claude) |
| ChatGPT connector | ChatGPT is your daily assistant | [ChatGPT how-to](/blog/schedule-social-posts-from-chatgpt-mcp) · [/chatgpt](/chatgpt) |
| Grok connector | Grok (or Grok Bot) is your assistant | [Grok how-to](/blog/schedule-social-posts-from-grok-mcp) |
| Cursor agents | Cursor is your agent IDE | [Cursor agents guide](/blog/best-ai-social-media-scheduler-for-cursor-agents) |
| DunSocial CLI | Terminal, CI, or local agents without remote MCP | [/cli](/cli) |

All of these drive the **same DunSocial workspace** when you connect the same account. Prefer Codex when product updates & social should share one agent loop; Claude/ChatGPT/Grok when those chats are daily; Cursor for the IDE agent; CLI for JSON & CI.

Side-by-side Claude/ChatGPT setup: [connect DunSocial MCP to Claude or ChatGPT](/blog/connect-dunsocial-mcp-to-claude-or-chatgpt).

## A practical first session

1. Connect networks in the DunSocial web app (once), including Discord & Slack if needed.
2. Add the Codex MCP server with `https://api.dunsocial.com/api/mcp`, then finish OAuth (`Authenticate` or `codex mcp login DunSocial`).
3. Run the read-only verify prompt.
4. Save a short brand memory note if you have not already (tone, product one-liner, words you never use).
5. Draft one post from a real changelog or PR summary.
6. Confirm copy, accounts, time, timezone.
7. Schedule, then open the web calendar and confirm the MCP tag.

That session teaches the loop better than any feature tour. After that, Codex can help with weekly batch drafts while you keep the confirm step.

## Common mistakes (and the fix)

- <strong class="!font-semibold">Skipping verify.</strong> Always run the read-only account list before drafting.
- <strong class="!font-semibold">Inventing tokens.</strong> Prefer browser OAuth (`Authenticate` or `codex mcp login`). Do not paste a bearer token into Codex chat for DunSocial.
- <strong class="!font-semibold">Scheduling without timezone.</strong> Ask Codex to print the timezone next to the local time. Confirm both.
- <strong class="!font-semibold">Treating Codex as the only calendar.</strong> Open the DunSocial web calendar after the first few MCP schedules so you trust the MCP tag & the time slots.
- <strong class="!font-semibold">Forgetting brand memory.</strong> Save audience, offer, tone, & banned phrases, then ask Codex to search memory before drafting.
- <strong class="!font-semibold">Assuming Codex menus never change.</strong> Re-check [learn.chatgpt.com/docs/extend/mcp](https://learn.chatgpt.com/docs/extend/mcp) if Add server or Authenticate moved.

## Why this path fits builders in Codex

If Codex is already where you review diffs and write release notes, scheduling from the same agent removes a context switch. DunSocial hosted MCP keeps OAuth, **53 tools**, brand memory, & confirm-before-publish on the same **USD 20** workspace as the web app & CLI.

Favour DunSocial when you want that full loop without leaving the coding agent. See [/mcp](/mcp) & [/pricing](/pricing).

## FAQ

### Is MCP an extra cost?

No. Hosted MCP with **53 tools** is included in the USD 20/mo or USD 192/yr plan. See [/pricing](/pricing).

### Is there a trial?

Yes. 14-day trial, no card.

### How much are extra seats?

Extra seats are USD 8/mo each. The base plan includes 1 seat. Extra brands are separate USD 20 workspaces.

### Which platforms can I schedule to from Codex?

X, LinkedIn, Instagram, Threads, Bluesky, Reddit, Pinterest, YouTube Shorts, Discord, & Slack; TikTok limited beta. Connect accounts in the DunSocial app first.

### What does human confirm mean in Codex?

Ask Codex to show copy, destinations, time, & timezone, then explicitly confirm before schedule or publish. DunSocial keeps human confirmation in front of publish for AI-written work.

### Can MCP create social network logins?

No. Connect networks in the DunSocial web app. MCP uses accounts already linked to the workspace you approve in OAuth.

### Codex UI changed. What should I do?

Re-check OpenAI’s current Codex MCP docs for Add server, Streamable HTTP, Authenticate, & `codex mcp login`. The DunSocial URL stays `https://api.dunsocial.com/api/mcp`.

### Codex, Claude, ChatGPT, or Grok?

Use this page when Codex is your daily coding agent. Use the [Claude](/blog/schedule-social-posts-from-claude-mcp), [ChatGPT](/blog/schedule-social-posts-from-chatgpt-mcp), or [Grok](/blog/schedule-social-posts-from-grok-mcp) how-tos when those are your daily clients. Same hosted MCP URL either way.

---

## About this document

This is the Markdown representation of https://www.dunsocial.com/blog/schedule-social-posts-from-codex-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