# How to Switch from Typefully to DunSocial with MCP (No Missed Posts)

> Switch from Typefully to DunSocial without missing posts: both have MCP servers, so migrate drafts & queue as an agent-to-agent handoff you review.

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

---

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

Typefully has its own MCP server, & so does DunSocial. That means switching from Typefully to DunSocial doesn't need a CSV export or a rebuild from scratch: connect both MCP servers in the same AI client, dump the Typefully queue to Markdown, recreate it as drafts through DunSocial MCP, test one small prompt yourself, then check the calendar the next day.

This guide is for solo founders, writers, & small teams whose Typefully queue lives on the networks DunSocial also covers, & who want a wider publish set (Reddit, Pinterest, YouTube Shorts, Discord, Slack) or a brand memory that survives past the current draft, without losing the writing-first workflow they're used to. Start a [14-day free trial](https://app.dunsocial.com/login) when you're ready to connect accounts & run the test.

## The smart path: Typefully MCP → Markdown → DunSocial MCP

Both tools expose MCP, so this isn't a black-box import. It's a reviewable Markdown dump, a small test run, & human confirmation before anything goes live. The path:

1. **Connect Typefully's official MCP server** at `https://mcp.typefully.com/mcp` in Claude, ChatGPT, or another MCP-capable client. Typefully documents the setup, including OAuth (recommended, sign in with a browser) or an API-key Bearer header for headless setups, in its own [MCP setup guide](https://support.typefully.com/en/articles/13128440-typefully-mcp-server) & [agent overview](https://typefully.com/ai-agents).
2. **Ask the assistant to dump the upcoming queue & drafts into Markdown files.** Typefully's MCP tools cover drafts, the schedule/publish queue, connected accounts, tags, & media, so a full export is one prompt away. One post per file: channel, scheduled time, body, media notes, thread order if needed.
3. **Connect DunSocial MCP** at `https://api.dunsocial.com/api/mcp` in the same client. DunSocial's hosted MCP ships 53 tools & is included in the plan. See [DunSocial MCP](/mcp) for endpoint & scope details.
4. **Point the assistant at those Markdown files** & ask it to create drafts & schedules through DunSocial. Keep human confirm on before publish.
5. **Run a small test prompt yourself** (one or two posts), open the app, then check the calendar the next day before you deepen the cutover.

If you want the side-by-side context first, skim [DunSocial vs Typefully](/compare/dunsocial-vs-typefully) or [Typefully alternatives](/alternatives/typefully), or the broader [best Typefully alternatives for multi-platform publishing](/blog/best-typefully-alternatives-multi-platform) roundup, then come back here for the move itself.

## Who this guide is for (30 seconds)

This cutover is for people whose live Typefully queue sits on networks DunSocial also covers: **X, LinkedIn, Threads, Bluesky, & Instagram** overlap directly; DunSocial adds **Reddit, Pinterest, YouTube Shorts, Discord, & Slack** (TikTok in limited beta). A human confirms before publish, same as Typefully's own model.

**Price while you overlap:** USD 20/mo or USD 192/yr, with a 14-day free trial, 1 seat in the base plan, & extra seats at $8/mo. Full detail on [pricing](/pricing). Typefully's own Starter plan is $12.50/mo flat, with a real free tier & a 14-day trial of its own, genuinely cheaper if you only ever publish to Typefully's network set.

**MCP:** 53 tools, included, endpoint `https://api.dunsocial.com/api/mcp`.

If your Typefully queue is mostly on those overlapping networks & you want the extra destinations or a memory that carries between posts, keep going. Typefully remains the better pick when writing craft, Mastodon, or its lower price are what you actually need. See "When to stay on Typefully" below before you commit to the switch.

## Setup (once)

Do these steps once. After that, the prompts below reuse the same connectors.

### Connect Typefully MCP

In your AI client, add `https://mcp.typefully.com/mcp` as a custom MCP connector. Typefully's server advertises OAuth discovery, so a spec-compliant client opens Typefully in the browser for you to approve access, no key to copy. If your client doesn't support the OAuth flow, use an API key as a Bearer header instead (Typefully → Settings → Integrations). Confirm the assistant can list your connected accounts & see the draft/schedule queue before you trust a bulk dump. Typefully's own notes: [MCP setup guide](https://support.typefully.com/en/articles/13128440-typefully-mcp-server).

### Start DunSocial & connect accounts

[Log in or start the trial](https://app.dunsocial.com/login), then connect the overlapping networks in the DunSocial app first. MCP needs those accounts in place before it can create drafts against the right channels.

### Connect DunSocial MCP

In DunSocial, open Settings → MCP & add `https://api.dunsocial.com/api/mcp`. Approve the workspace scopes your assistant needs. Posts created through MCP are tagged with source "MCP" in the app, which makes the migration trail easy to audit. Details & tool coverage: [MCP page](/mcp). Prefer the CLI? The same workspace also works with the [DunSocial CLI](/cli).

### Save brand voice

Before you bulk-recreate, set AI Memory & a Voice Preset. This is the part Typefully doesn't have an equivalent for: its writing assistant learns from your past posts inside a single draft session, but nothing persists as reusable facts the way DunSocial's Memory does. Set it once here so the test prompt proves voice & scheduling, not just that a draft appeared.

## Migration checklist

Work the list in order. The test step & the next-day check are what keep you from double-posts & gaps.

### 1. Dump Typefully queue to Markdown

With Typefully MCP connected, paste the **dump Typefully queue to Markdown** prompt below. Ask for the next 14 days (or whatever window covers your live schedule). Aim for a folder like `./typefully-export/` with one Markdown file per post: channel, ISO scheduled time, body text, media URLs or "needs re-upload," & thread order if applicable. Do not delete or edit anything in Typefully during the dump.

### 2. Review the Markdown (human gate)

Skim every file. Keep, drop, or rewrite. Prioritize posts on networks DunSocial covers (X, LinkedIn, Threads, Bluesky, Instagram, Reddit, Pinterest, YouTube Shorts, Discord, Slack, TikTok beta). If you post to Mastodon from Typefully, leave those items there, since DunSocial doesn't support Mastodon. Note media that needs a fresh upload into DunSocial. This is your first real gate: the assistant exported the queue; you decide what's worth recreating.

### 3. Test the prompt (before the full queue)

Paste the **test migrate one or two posts** prompt. It should create drafts for the first two posts only, match channel & time as closely as DunSocial supports, & tell you exactly what to open in the app. Do not publish yet. Open DunSocial, review those drafts, & confirm the schedule & voice look right. If the test fails, fix voice, media, or channel mapping before you scale.

### 4. Recreate the rest via DunSocial MCP

When the test looks good, paste the **migrate the rest after test passes** prompt. Prefer draft plus schedule over publish-now. Attach media through DunSocial's media flow when URLs alone aren't enough. Keep human confirmation on. Ask the assistant for a short summary of what it created & what it left on Typefully (Mastodon items, for instance).

### 5. Pick a handover date & avoid doubles

Choose a cutover day. New work lands in DunSocial from that point. Cancel the matching Typefully items that shouldn't fire. A short overlap is fine if you're deliberate about which calendar owns each post.

### 6. Check the next day

The morning after: open the DunSocial calendar (& Typefully if it's still live). Confirm yesterday's test or early cutover posts went out once, previews matched, & nothing failed silently. Only then deepen the cutover.

### 7. Cancel Typefully last

After the next-day check passes & the DunSocial calendar matches your intent, cancel or downgrade Typefully. Export any analytics you still want to keep first. Cancelling earlier is how people create gaps.

## Copy-paste prompts

Use these as written. Adjust the date window or folder name if you need to, but keep the "drafts first / no publish without confirmation" constraints.

### Dump Typefully queue to Markdown

<CodeSnippet
	label="prompt"
	highlight={false}
	code={`Using Typefully MCP, list my connected accounts and every scheduled post and draft for the next 14 days. For each post write a Markdown file in \`./typefully-export/\` with channel, scheduled time (ISO), body text, media URLs or "needs re-upload", and thread order if applicable. Do not delete or edit anything in Typefully.`}
/>

### Test migrate one or two posts

<CodeSnippet
	label="prompt"
	highlight={false}
	code={`Using DunSocial MCP and the files in \`./typefully-export/\`, take the first two posts only. Create drafts in my DunSocial workspace (do not publish now). Match channel and time as closely as supported. Tag or note source as migrated-from-Typefully. Then tell me exactly what to open in the DunSocial app to review.`}
/>

### Migrate the rest after test passes

<CodeSnippet
	label="prompt"
	highlight={false}
	code={`Using DunSocial MCP and every file in \`./typefully-export/\`, create drafts (prefer draft + schedule over publish-now). Match channel and time for platforms DunSocial covers (X, LinkedIn, Threads, Bluesky, Instagram, Reddit, Pinterest, YouTube Shorts, Discord, Slack, TikTok beta). Skip any Mastodon-only posts. Summarize what you created and what you left for Typefully. Do not publish without my confirmation.`}
/>

## Where Typefully still wins

Fairness matters more than the pitch here. Stay on Typefully, or keep it alongside DunSocial, when:

- **Writing is the whole job.** Typefully's editor & thread-writing workflow are better than DunSocial's. If threads are all you do, use Typefully.
- **Price is the deciding factor.** Typefully's Starter plan is $12.50/mo flat against DunSocial's $20/mo, with a genuine free tier Typefully offers & DunSocial doesn't.
- **You post to Mastodon.** DunSocial doesn't support it; Typefully does, alongside X, LinkedIn, Threads, Bluesky, & Instagram.

None of these are wrong reasons to stay. The switch makes sense specifically when the extra networks (Reddit, Pinterest, YouTube Shorts, Discord, Slack) or a memory that persists across drafts are what you're missing, not because Typefully does anything badly.

## After the switch

Once the calendar is yours again, DunSocial is set up for how founders & writers already work: Daily Ideas for the next posts, Memory & Voice Presets so drafts stay on-brand across every platform (not just the one you're currently drafting for), & MCP so you can keep shipping from Claude, ChatGPT, or Cursor without bouncing into extra tabs. The same 53 MCP tools that helped you migrate stay available for everyday drafting & scheduling.

If you haven't started yet, open the [trial](https://app.dunsocial.com/login), connect your overlapping accounts, & run the three prompts above in order. Pricing & seat details are on [pricing](/pricing). Broader product questions live in the [FAQ](/faq).

## FAQ

### Can I import Typefully's queue automatically?

Yes, in a reviewable way: Typefully MCP → Markdown → DunSocial MCP. That's an agent-to-agent handoff with human gates at each step, not a silent import.

### Does DunSocial support Mastodon?

No. If Mastodon is part of your Typefully queue, keep publishing those posts from Typefully & migrate the rest. DunSocial's platform set is X, LinkedIn, Instagram, Threads, Bluesky, Reddit, Pinterest, YouTube Shorts, Discord, & Slack (TikTok in limited beta).

### Is Typefully's writing editor better than DunSocial's?

Typefully's editor & thread-writing workflow are genuinely stronger for pure text-first writing, since that's Typefully's whole focus. DunSocial's composer is built around adapting one idea across more destinations at once, plus a brand memory the AI reads from instead of working only off the current draft.

### Is DunSocial MCP included?

Yes. Hosted MCP with 53 tools for posts, drafts, memory, media, workspaces, & personalization is included at USD 20/mo or USD 192/yr. Endpoint: `https://api.dunsocial.com/api/mcp`. Typefully's own MCP server (`https://mcp.typefully.com/mcp`) is well documented too, & the two are close to parity on the agent-access question itself.

### Can I review AI or MCP posts before they go live?

Yes. Human confirmation before publish is how DunSocial works, the same as Typefully. Prefer creating drafts (& scheduled drafts) during migration, then approve in the app.

## Sources

- Typefully: [Give AI Agents Social Media Skills](https://typefully.com/ai-agents), [MCP setup guide](https://support.typefully.com/en/articles/13128440-typefully-mcp-server)
- DunSocial vs Typefully facts (pricing, platforms, MCP): `apps/landing/src/lib/content/competitors.ts`

Retrieved 25 September 2026.

---

## About this document

This is the Markdown representation of https://www.dunsocial.com/blog/switch-from-typefully-to-dunsocial. 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