I built Sotion, an AI social content workflow on top of Notion

This is a submission for the Notion MCP Challenge

What I Built

I built Sotion, an AI-powered social content assistant that turns a Notion workspace into an operational content system.

The idea came from a simple problem: a lot of creators, indie hackers, and small teams already keep their best raw material in Notion, but the moment they want to turn those notes into social posts, the workflow breaks. They jump between docs, AI chat tabs, scheduling tools, and social apps. The content gets rewritten multiple times, context gets lost, and publishing becomes manual again.

So I built Sotion to keep that loop in one place.

With Sotion, a user connects their workspace through Notion MCP, adds their preferred AI provider, and then starts chatting in plain language. From there, Sotion can help create a dedicated social media workspace in Notion, organize a content database, draft posts, rewrite existing ideas, check connected publishing accounts, and publish approved text posts to supported platforms.

What makes it useful is that Notion is not treated as a passive note dump. It becomes the system of record for the content workflow.

Core features

• 
  Connect Notion through Notion MCP so Sotion can work directly with the user’s workspace


• 
  Guided onboarding to connect Notion and add an AI provider before entering the app


• 
  Natural-language chat for turning notes, ideas, and drafts into social content


• 
  Dedicated social content workspace in Notion, including a structured database for managing posts


• 
  Multi-model AI support through providers like OpenAI, Claude, OpenRouter, DeepSeek, Moonshot AI, and Z.AI


• 
  Social account connection and readiness checks for publishing workflows


• 
  Human-approved publishing for posts to supported social platforms


• 
  Optional online research sources via MCP integrations like Exa and Tavily
  

Supported social workflow today

Sotion is designed for text-based social publishing. Right now, the app supports:

• Twitter (X)


• LinkedIn


• Threads

Video Demo

Show us the code

GitHub repo: https://github.com/powxenv/sotion

Tech stack:

• TanStack Start


• AI SDK


• Drizzle ORM + Neon


• Better Auth


• Notion MCP


• Deploy on Railway

How I Used Notion MCP

I used Notion MCP to make Sotion work with the same place where ideas already live.

Most social content tools start after the thinking is already done. In my workflow, that thinking usually starts in Notion: rough notes, half-written drafts, launch ideas, product updates, and scattered content angles. I wanted the assistant to step into that environment instead of forcing users to move everything somewhere else first.

With Notion MCP, Sotion can look into the workspace, understand what already exists, and help turn that raw material into something operational.

In practice, this means Sotion can:

• find relevant notes and drafts inside Notion


• create and organize a content database for tracking ideas and posts


• store platform-specific drafts back into Notion


• update statuses and publishing metadata as work progresses


• use Notion as persistent context across sessions instead of starting from zero every time

That changes the product from “AI that writes posts” into “AI that works with your real content system.”

A simple example:

A user can connect Notion, ask Sotion to create a social content workspace, and then continue with prompts like:

• “Turn my product notes into a LinkedIn post”


• “Make an X version of this idea”


• “Plan posts for this week”


• “Save the drafts back to Notion”

Because the assistant can operate directly on the workspace, the output does not disappear into chat history. It becomes part of a living system inside Notion that the user can review, edit, and keep building on.

I also wanted the workflow to stay useful when the answer is not already inside Notion. Sometimes drafting a strong post needs fresh context from the web, whether that is industry news, supporting references, or additional research. For that, Sotion supports additional MCP-powered online sources like Exa and Tavily. When users enable them, Sotion can search the web, open relevant pages, and bring that context into the drafting process, while still keeping Notion as the place where the work is organized and saved.

That was the main thing I wanted to unlock: keeping ideation, drafting, organization, research, and follow-up in one continuous workflow instead of breaking it across disconnected tools.