# How to schedule social posts from Grok with MCP

> Connect DunSocial’s hosted MCP in Grok or Grok Bot, verify your workspace, draft in your voice, then schedule with human confirm. 53 tools at USD 20/mo.

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

---

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

Grok can call hosted MCP. Grok Bot agents share connectors differently. The useful how-to is not "paste a caption into Grok." It is connect DunSocial hosted MCP, finish browser OAuth, verify the workspace, draft in your voice, then schedule with human confirm — from Grok chat or from a Grok Bot agent on a persistent cloud computer.

## Short answer

Add the connector URL `https://api.dunsocial.com/api/mcp`. In **Grok chat**, open connector settings and add a custom MCP named DunSocial. In **Grok Bot**, add it once at [https://grok.com/connectors](https://grok.com/connectors) (New Connector, Custom). OAuth only — no Authorization header, no pasted token. Verify with a read-only account list. Draft in voice; show copy, destinations, time, and timezone; confirm. Human confirm even on persistent Bot agents. **53 tools** are included in **USD 20/mo** or **USD 192/yr** (14-day trial, no card; extra seats USD 8/mo). Posts land on the same calendar as the web app and CLI, tagged MCP.

Product steps: [/grok](/grok) and [/grok-bot](/grok-bot). Trial: [app.dunsocial.com/login](https://app.dunsocial.com/login).

| Step | Action | DunSocial surface |
| --- | --- | --- |
| 1 | Add custom connector URL `https://api.dunsocial.com/api/mcp` | Grok connectors or grok.com/connectors |
| 2 | Browser OAuth: sign in, pick workspace, grant scopes | DunSocial OAuth |
| 3 | Read-only verify: list accounts and name the workspace | Hosted MCP tools |
| 4 | Draft in voice, show copy/time/timezone, confirm, then schedule | Same calendar as web and CLI |

## Grok chat vs Grok Bot

### Grok chat

Open **Grok connector settings**, add a custom MCP named `DunSocial`, and enter this server URL:

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

Save the connector. Grok opens DunSocial in a browser so you can sign in, choose a workspace, and approve access.

Do **not** add an Authorization header. Do **not** paste an access token into Grok. The connector flow is browser OAuth only. Ask before approving OAuth or completing signup on someone else's behalf, and never type another person's password.

Product walkthrough: [/grok](/grok).

### Grok Bot

Grok Bot runs named agents on a persistent cloud computer. Connectors are added **once** at [https://grok.com/connectors](https://grok.com/connectors): New Connector, Custom, same URL as Grok chat, named `DunSocial`. Agents that have access to that connector can call DunSocial tools. Persistence does not skip review. Confirm is still required before schedule or publish.

Do **not** add an Authorization header. Do **not** paste a token. OAuth only.

Product walkthrough: [/grok-bot](/grok-bot).

## Verify workspace before you write

After authorization, confirm that DunSocial tools appear. Start with a read-only request:

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

If the workspace is wrong or the expected accounts are missing, stop. Connect or switch those accounts in the DunSocial web app, then return to Grok. MCP cannot create an X, LinkedIn, Instagram, Slack, or other network login for you. That happens once in the app; Grok then uses the accounts already connected.

Why this step matters: assistants are fast. A wrong workspace can schedule into the wrong brand calendar. Thirty seconds of verify saves a cleanup later.

## Draft in voice, then schedule

Give Grok a source you trust (release note, changelog, approved campaign brief). Ask for a draft that uses your saved **AI Memory** and **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:

1. Exact copy (including thread beats if you asked for a thread)
2. Destination accounts
3. Time and timezone
4. Media attachments if any

When you are ready, tell Grok to schedule. DunSocial requires **human confirmation** before an MCP-created post can publish — in Grok chat **and** on Grok Bot. Scheduled work appears on the same calendar as the web app and is tagged **MCP**, so there is one record of what the assistant created.

If you want a draft only, say so. Drafts also land in the shared workspace and can be edited in the web app later.

## What the 53 tools cover (high level)

DunSocial hosted MCP exposes **53 tools**. You do not need to memorize every name. At a high level they cover:

| Group | What Grok 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 and update the workspace AI voice profile |

Full tool map and client list: [/mcp](/mcp).

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

Platforms on the same plan: X, LinkedIn, Instagram, Threads, Bluesky, Reddit, Pinterest, YouTube Shorts, Discord, and Slack; TikTok limited beta.

## Grok vs Claude vs ChatGPT vs CLI

| Path | When to use it | Entry |
| --- | --- | --- |
| Grok chat hosted MCP (this page) | You live in Grok chat | [/grok](/grok) |
| Grok Bot | You run named agents on a persistent cloud computer | [/grok-bot](/grok-bot) |
| Claude hosted MCP | Claude is your daily assistant | [Schedule from Claude MCP](/blog/schedule-social-posts-from-claude-mcp) |
| ChatGPT connector | ChatGPT is your daily assistant | [/chatgpt](/chatgpt) |
| DunSocial CLI | Terminal, CI, or local coding agents without remote MCP | [/cli](/cli) |

All of these drive the **same DunSocial workspace** when you connect the same account. Prefer hosted MCP when the assistant is remote and has no shell. Prefer the CLI when you already have a terminal and want JSON output plus CI exit codes. Prefer Grok chat when that is the window you already have open. Prefer Grok Bot when a named agent should keep the connector across sessions. The connector URL for hosted MCP is the same: `https://api.dunsocial.com/api/mcp`.

Agent overview: [/agents](/agents).

## A practical first session

1. Connect networks in the DunSocial web app (once).
2. Decide Grok chat, Grok Bot, or both.
3. Add the custom connector URL and name it `DunSocial`.
4. Finish browser OAuth: sign in, pick the workspace, grant scopes.
5. Run the read-only verify prompt.
6. Save a short brand memory note if you have not already (tone, product one-liner, words you never use).
7. Draft one post from a real changelog line. Ask Grok to show copy, destinations, time, and timezone.
8. Confirm, then schedule.
9. Open the web calendar and confirm the MCP tag.

That session teaches the loop better than any feature tour. After that, Grok can help with weekly batch drafts while you keep the confirm step — including on persistent Bot agents.

## Common mistakes

- <strong class="!font-semibold">Skipping verify.</strong> If you draft before listing accounts, you may target yesterday's workspace. Always run the read-only list first.
- <strong class="!font-semibold">Pasting tokens into Grok.</strong> The connector uses browser OAuth. If a guide tells you to paste a bearer token or add an Authorization header for DunSocial, stop and use the official [/grok](/grok) or [/grok-bot](/grok-bot) flow instead.
- <strong class="!font-semibold">Mixing up Grok chat and Grok Bot.</strong> Chat uses connector settings. Bot adds the connector once at [grok.com/connectors](https://grok.com/connectors) (New Connector, Custom). Agents still need access to that connector.
- <strong class="!font-semibold">Assuming a persistent Bot skips confirm.</strong> A cloud computer does not publish unattended. Human confirm is required for chat and Bot.
- <strong class="!font-semibold">Scheduling without timezone.</strong> Ask Grok to print the timezone next to the local time. Confirm both.
- <strong class="!font-semibold">Treating Grok as the only calendar.</strong> Open the DunSocial web calendar after the first few MCP schedules so you trust the MCP tag and the time slots. After that, chat can stay primary.
- <strong class="!font-semibold">Forgetting brand memory.</strong> If posts sound generic, save a few memory items (audience, offer, tone, banned phrases) and ask Grok to search memory before drafting. That is what the memory tools are for.

## Why this path fits founders in Grok

If Grok is already where you write launch notes and think through positioning, scheduling from the same chat removes a context switch. DunSocial hosted MCP keeps OAuth, 53 tools, brand memory, and confirm-before-publish on the same USD 20 workspace as the web app and CLI. You add one connector URL, approve a workspace, and keep a human in front of live posts — in Grok chat or on a Grok Bot agent.

## 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.

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

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

### Does human confirm still apply on Grok Bot?

Yes. Persistence does not skip review. Ask the agent to show copy, destinations, time, and timezone, then explicitly confirm before schedule or publish. Do not grant a habit of "just ship it" prompts for live customer accounts.

### Can MCP create social network logins?

No. Connect X, LinkedIn, Instagram, Slack, and other networks in the DunSocial web app. MCP uses the accounts already linked to the workspace you approve in OAuth.

### Grok chat or Grok Bot?

Use Grok chat (this page's connector-settings path) when you are in the everyday Grok window. Use [/grok-bot](/grok-bot) when a named agent on a persistent cloud computer should keep the same DunSocial connector. Both use `https://api.dunsocial.com/api/mcp` and both require human confirm.

## Sources

- [Grok connectors](https://grok.com/connectors)
- [xAI Grok connectors docs](https://docs.x.ai/grok/connectors)

Retrieved 14 September 2026.

---

## About this document

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