Skip to main content
⚡ The shared content pipeline

Contentpipe

Draft, review, schedule, and publish content across many projects — with your team and your AI agents working the same pipeline, over the same rules.

Contentpipe is the content and marketing planning system behind Workjournal, Skillforests, and Mindcoding. Every idea travels one deliberate route — from a one-line stub to a published article, fanning out into channel promos along the way — and both people and agents move items forward through the exact same state machine.

What it is​

  • A pipeline, not a CMS. Content carries a single status at a time, and that status decides who owns it and what can happen next. Transitions are enforced in the database, so it doesn't matter whether a change comes from the admin UI, the API, or an AI client.
  • Agent-native. AI clients (Claude, ChatGPT) drive the pipeline over the Model Context Protocol using workflow-level tools — never raw table writes — so they can't put content into invalid states.
  • One source of truth. Postgres holds everything. The admin UI, the MCP server, and the promo dispatcher are all just views onto the same schema.

Where to go next​

If you want to…Start here
Understand how content flowsThe publishing pipeline
Read/write data programmaticallyAPI overview
Drive Contentpipe from an AI clientMCP overview
Internal tool, first

Contentpipe is an internal tool with a path to a paid product. These docs describe the system as it runs today — Supabase-backed, MCP-first — not an aspirational future API.