Got it. The YouTube link you shared works for a Notion Dev Community submission too.
Paste this full, cleaned-up submission draft (edit the parts in [brackets]):
This is a submission for the Notion MCP Challenge
What I Built
I built a CreatorOps Hub in Notion that pulls my dev workflow into one place. It helps me track what I am building in Replit / VS Code, what is deployed (Replit-first, with Google Cloud and Firebase as additional deployment targets), and where I publish updates (DEV and TikTok).
Inside Notion, I organize everything as structured databases so it is easy to demo and keep updated:
- Replit Projects: what I am building and links to the source and live demos
- Deployments: what is live, where it is hosted, and the live URL
- Publish Links: DEV posts and TikTok videos connected to a project or release
- Version History: short release notes so I can see what changed over time
This makes Notion the “control center” for shipping and sharing projects.
Video Demo
Video walkthrough (YouTube): https://www.youtube.com/shorts/bczx1WZKoWc
Show us the code
How I Used Notion MCP
I used Notion MCP as the bridge between my external build environment and my Notion CreatorOps Hub. My goal was to make Notion the place where project, deployment, and publishing data can live as structured entries, so the workspace works like a real dashboard instead of scattered notes.
In this workflow, Notion MCP enables my external tooling to create and update the entries that power the hub, including deployments, release notes, and publish links. That unlocks a repeatable “ship and log” loop where each release has a clear record inside Notion.
Top comments (0)