Manage your CMS through REST API, CLI and MCP

Progressive CMS can be managed through REST API, CLI and MCP. Choose the connection that fits your tools:

• REST API for HTTP applications, integrations and custom agents.

• CLI for terminal-based agents and repeatable command-line workflows.

• MCP for compatible assistants using structured CMS tools.

Each connection works within the CMS's permissions and validation rules. Editors can continue in the visual admin while agents prepare changes. For practical guidance, read the agent field guide.

Use the REST API to work directly with Progressive CMS over HTTP. Connect applications and AI agents to manage structured website content.

• Discover content contracts and available operations.

• Read and update pages, articles and media metadata.

• Validate draft revisions and request a preview.

Begin with GET /api/v1/agent/bootstrap using your dedicated account. The response describes the instance and the capabilities available to it. Follow the published schemas and keep the token in private configuration.

Use the command-line interface to work with Progressive CMS from a terminal. It fits developer workflows, operational scripts and agents that also work on project files.

• Inspect content contracts and run diagnostics.

• Validate a theme prepared in the project working tree.

• Use documented publication commands and operational checks.

In a configured CLI environment, start with cms agent bootstrap --json. Use the installed command guidance for your instance, then bring the prepared pages and design to review.

Connect a compatible AI assistant through MCP — Model Context Protocol. It exposes CMS operations as discoverable tools with defined inputs.

• Discover the tools available to the agent's account.

• Inspect the CMS and prepare structured content.

• Validate changes, open a preview and follow the publication workflow.

You choose the assistant and grant access appropriate to its task. The same website remains manageable through REST API, CLI and the visual admin. See the AI-agent workflow.

Progressive CMS uses TypeScript, Node.js and PostgreSQL. The web process serves the public website and admin; a worker handles background tasks. Content, publication, themes, media, navigation, search, forms and access have shared interaction rules.

Use the supported connectors and HTTP/webhook delivery to link services. For detailed practical notes, read the agent field guide.

Content types define fields and validation rules. Structured blocks build page content. A theme contains Liquid templates, components, CSS, JavaScript and settings.

Install and validate the theme as a package. Preview it on real material before activation. CSS, SVG, canvas and WebGL remain tools for the theme author; the project’s design can go beyond a fixed set of screens.

Editing begins in a draft. Validate the prepared revision and preview it before release. Combine related changes in a ChangeSet and preflight them before applying the release. Versions and generation checks protect against overwriting newer work. Viewing a draft does not create a revision or change its author.

User and service-account permissions, audit history, image processing, metadata, sitemaps, forms and search are part of the CMS. The release workflow provides a clear path for keeping the instance up to date.

A project keeps its own theme and structured content on the infrastructure chosen by its owner. Editors can continue in the admin, and agents can return through the CMS’s published contracts. The source code and installable releases are publicly available on GitHub.