Cendia includes a Model Context Protocol server for working with CMS content, releases and schema reconciliation. This is an administrative integration: its tools can write drafts, change release bindings and publish content. It is not a read-only search of this documentation.
Availability and authentication
Cendia:EnableMcp controls registration of the server and its HTTP endpoints; the current
default is enabled. The implementation uses stateless HTTP transport and requires the CMS
Administrator role on the mapped endpoints.
A delivery API key is not an administrator credential. The host's authentication configuration must provide an authenticated principal with the required role. A client must support that authentication arrangement as well as the transport. Do not assume a generic MCP client can reuse a browser's CMS login, or that a public OAuth connection flow is supplied.
The CMS currently calls MapMcp() without an explicit route prefix. Verify the resolved endpoint
in your host before configuring a client; do not assume that it is /mcp. This is an integration
detail to confirm for your deployed release.
What the tools can do
| Area | Tool methods | Effect |
|---|---|---|
| Read | Content read tools | Resolve content and its release context |
| Drafts | SaveDraft, DeleteDraft |
Create or remove release drafts |
| Bindings | SetContentBinding, SetStructureBinding, SetDeleteBinding |
Select release content, move pages or mark deletions |
| Releases | CreateRelease, ListReleases, ListReleaseBindings |
Prepare and inspect a release |
| Publish | PublishRelease |
Publish the release to the live site |
| Schema | CreateSchemaRelease, IngestDescriptor, ListPendingFields |
Work with schema releases and pending fields |
These are .NET tool method names; use the server's tool discovery response for the exact names and argument schemas exposed to your client.
A reviewable authoring workflow
- Connect to an evaluation environment with an authorized administrator account.
- List releases and inspect the target item and its culture before writing.
- Create a clearly named content release and retain its ID.
- Save a draft using stable field IDs and the JSON storage shapes defined by the content type.
- Set the release's content binding to the intended draft version. A saved draft and a selected release version are separate concepts.
- Inspect the release bindings and preview the release in the CMS.
- Resolve validation or reconciliation tasks and obtain the normal editorial review before publishing.
Checkpoint: the preview contains your intended change while public delivery still contains the previous published version.
Publication is a separate action
PublishRelease changes the live site. Its forceDespiteOpenTasks argument can bypass the
open-task check; normal reviewed publication uses false. An automation should never infer
permission to publish from permission to prepare a draft.
Schema tools also require care: ingesting a descriptor does not deploy your application's C# types, templates or frontend components. Coordinate application deployment and schema release review. See Content types and the Upgrading guides.
Integration readiness
Before enabling an unattended client, verify the endpoint, authentication and logout behavior, tool discovery, draft writes, release preview and denied access for a non-administrator. Keep credentials outside prompts and source control. Record the release ID so a person can review the actual proposed changes.