Brainstorm in conversation, create a content task, draft the first version in GitCMS, and send it to review before anything goes live. The model works inside your workflow instead of bypassing it.
Brainstorm
Shape angle, audience, and CTA before you ask for a draft.
Create a content task
Keep notes, scope, and workflow state attached to the work.
Draft inside the chat
GitCMS opens the editor inside ChatGPT or Claude.
Review before publish
The same human approval flow still decides what ships.
Setup
The connector URL is the same for both providers. GitCMS documents ChatGPT and Claude today because those are the tested setup paths.
Open ChatGPT Settings and turn on Developer Mode.
Go to Settings > Apps and click Create.
Paste following GitCMS connector URL.
https://mcp.gitcms.blog/sseClick Connect, sign in with GitHub, and allow access.
Start a chat and choose GitCMS from your tools.
MCP requires a licensed GitCMS site. Preview mode does not unlock the connector.
How it works
We're moving teams away from copy-pasting AI drafts into a CMS after the fact a task-first workflow where brainstorming, drafting, and review stay connected.
GitCMS keeps the editor, schema, and review path in the same place the model is working.
Brainstorm first. When the angle is clear, create a content task. That gives the model a real piece of editorial work to draft against instead of a floating prompt with no workflow context.
.gitcms defines collections, fields, and paths. CONTENT.md is loaded automatically as site writing guidance. The model gets the context it needs without you having to restate it every time.
AI does not bypass your workflow. Drafts stay attached to content tasks, review stays visible, and Git remains the source of truth underneath the whole process.
Preview the site on the web first. When you are ready to draft in ChatGPT or Claude, license the site to unlock MCP and publishing.