Concrete CMS ChatGPT Integration
Connecting Concrete CMS to ChatGPT means giving an assistant a narrow, revocable way into your own site, so that asking for a change in plain language actually changes something. This page explains how that connection is made for Concrete CMS specifically, and where it stops.
Where this one stands
Concrete CMS has a REST API, but the shape of a create request is only described in an OpenAPI document that production installations disable. Building against a guessed payload is not something this product does, so it waits for a test installation to read the real schema from.
Which assistants this works with
Any assistant that speaks the Model Context Protocol. That includes ChatGPT and Claude today. You connect your own account — there is no separate subscription to an AI provider through us, and your conversations stay with whichever assistant you already pay for.
Common questions
Do I need an OpenAI API key?
No. You connect the ChatGPT account you already have. Concrete CMS AI Agent is the bridge between that account and your Concrete CMS site; it is not an OpenAI reseller and does not need a key from you.
Can ChatGPT publish to my Concrete CMS site without asking?
No. Work is created unpublished wherever the platform allows it, and publishing is a deliberate, separate step. Never changing a live site without authorisation is a rule the product is built around rather than a setting.
What happens if I revoke access?
The connection stops working immediately. The credential lives on your Concrete CMS installation and is yours to withdraw at any time, without touching anything else on the site.
Getting started with Concrete CMS AI Agent
Concrete CMS AI Agent is not on sale yet. The product page tracks where it stands, and nothing is advertised before it works.