Discover before acting
List pages, sections, layouts, menus, and shortcodes so the client works with real identifiers and current configuration.
Model Context Protocol
CMS Max MCP Server
Give an AI client current, tenant-scoped tools for understanding and managing a CMS Max website.
Connect through the website's authenticated Streamable HTTP endpoint, inspect the live tool schemas, read the current site state, preserve rollback context, and make deliberate content or configuration changes.
- Tenant-scoped
- Schema-described
- Read and write tools
- Rate-limited
- Revocable access
DiscoverReadPlanChangeVerify
Ground AI work in the live website
The server supplies current context and actions. The operating process supplies judgment.
An MCP client can inspect the available tools and the tenant's current website state instead of relying on a stale summary. Teams still decide the goal, evidence, approvals, rollback plan, and quality standard.
Read the complete object
Retrieve content, CSS, scripts, SEO settings, layout relationships, or theme values before deciding what should change.
Verify after the write
Read the object back, inspect the public page, exercise interactive states, and retain a useful rollback record.
Connection setup
Connect the MCP client to the intended CMS Max website domain.
The token and endpoint belong to one tenant. Client configuration formats vary, so use the client's current Streamable HTTP instructions with the CMS Max values below.
- 01
Create an API client
In the website administration, open Settings, then API, and generate a token for the integration.
- 02
Store the token as a secret
Keep the bearer token out of public source, browser code, prompts, screenshots, documentation, and shared files.
- 03
Configure Streamable HTTP
Set the MCP endpoint to the website domain plus
/mcpand supply the token through the Authorization header. - 04
Inspect the live tool list
Let the client read current names, descriptions, JSON input schemas, and read-only annotations before calling a tool.
- Endpoint
https://your-site.example/mcp- Transport
- Streamable HTTP
- Authorization
Bearer <API_CLIENT_TOKEN>- Content type
application/json- Accepted response
application/json, text/event-stream- Session methods
POST,GET, andDELETE
Current tool families
Operate the website through focused, described capabilities.
The server returns the live tool list to the client. Available tools can evolve with CMS Max; the categories below reflect the current platform implementation.
Manage page content and settings
List, read, create, update, archive, and restore pages, including HTML, CSS, scripts, SEO fields, visibility, layout, and breadcrumbs.
Soft deletion preserves a restoration path.Work with reusable site regions
List and read sections, create or edit supported custom HTML sections, delete eligible sections, and restore saved revisions.
System and block-based sections remain protected where required.Understand page frames and slots
List layouts and templates, inspect slots, create custom layouts, assign supported sections, clear slots, and delete eligible unused custom layouts.
The content slot is reserved for page content.Manage menu locations and items
Read nested menus, create or edit items, connect them to CMS pages, move them within the hierarchy, and remove items or locations deliberately.
Page-linked items follow page URL changes.Discover dynamic website components
List installed shortcodes and request current parameter definitions, valid option values, placement rules, and ready-to-use examples.
Raw shortcode syntax belongs in saved content.Read and update shared brand settings
Inspect colors, fonts, assignments, and button styles, then change only the intended global values through the supported configuration tool.
Theme updates affect the site globally.Request boundary
Every request resolves the tenant before the tool touches website data.
The website domain establishes tenant context. CMS Max then validates the tenant API-client token, applies the MCP rate limit, dispatches the requested tool, and returns a structured result.
01Tenant domainResolve website
02API authenticationValidate token
03Rate limitControl request loop
04Tool handlerRun scoped operation
05Structured responseReturn result
Recommended operating loop
Make the agent prove its context, change, and result.
- 01
Inventory
List the relevant objects and identifiers, inspect relationships, and confirm the public URL or site-wide impact.
- 02
Snapshot
Read the complete current object and retain a rollback record before any content or configuration write.
- 03
Change narrowly
Send only the intended fields, preserve unrelated state, and keep secrets or sensitive data out of content.
- 04
Read back and test
Compare the saved state, inspect the public result, test links and controls, and document the release evidence.
Safety and rollback
Know which actions are reversible and which require extra care.
Tool descriptions and validation protect important boundaries, but the client still needs a release discipline proportional to the scope of the change.
- Page deletion
- Archives the page and supports restoration if its URL remains available.
- Section editing
- Supported custom sections retain restorable revisions when they are saved.
- Section deletion
- Permanently removes an eligible section after it is detached; capture the full state first.
- Theme configuration
- Applies across the website; verify colors, fonts, and buttons on representative pages.
- Navigation changes
- Can affect every page using the menu location; inspect the nested tree and destination URLs.
- Credentials
- Remain secrets outside page content and can be revoked from the website administration.
AI-assisted website operations
Use MCP where live context and controlled action materially improve the work.
Audit and improve page systems
Inventory pages, compare metadata and structures, prepare reviewed source, publish targeted changes, and verify public rendering.
Carry a shared design system forward
Read theme settings, layouts, sections, and existing page patterns before extending the visual language.
Build connected content clusters
Review page hierarchy, crawl settings, titles, descriptions, links, structured data, and supporting resources.
Maintain customer paths
Read nested menus and page relationships, add page-linked items, repair destinations, and verify the resulting journey.
Keep operational guides current
Update public pages from verified repository or partner evidence while preserving rollback snapshots and reference links.
Make verification part of the work
Read back the live object, check metadata and schema, test interactions, load images, and retain concise QA notes.
CMS Max MCP FAQ
Questions about connecting AI clients to CMS Max.
Use the current tool list and client documentation as the authority for available configuration and capabilities.
What is the CMS Max MCP endpoint?
The endpoint is the CMS Max website domain followed by /mcp, for example https://your-site.example/mcp. It uses authenticated Streamable HTTP.
How does an MCP client authenticate?
Create an API client and token in the website administration, store the token as a secret, and send it as a bearer credential to the tenant's MCP endpoint.
Can one token manage multiple CMS Max websites?
No. The website domain resolves the tenant and CMS Max validates the token against that tenant. Use credentials created for the intended website.
Which CMS Max tools are available through MCP?
The current server exposes supported tools for pages, reusable sections, layouts, menus, shortcodes, and theme configuration. The client should call the live tool-list method because capabilities can evolve.
Does MCP make every AI change automatically safe?
No. MCP supplies scoped tools, descriptions, validation, authentication, and structured results. Teams still need evidence, approvals, secret handling, narrow writes, rollback snapshots, and public verification.
Can MCP help an agent remember the website?
MCP lets the agent retrieve current website state when needed, which is more reliable than depending on a stale summary. Persistent planning or memory still depends on the AI client's own capabilities and operating process.
Connect an AI-ready website
Pair CMS Max platform context with an operating process your team can trust.
Plan the tenant, token, client, approved tasks, rollback strategy, validation, human review, and long-term ownership together.
Building Relationships with Web Developers and Marketing Agencies that want better results
The world's fastest and most SEO friendly website code.