Contentstack is included for a first-party MCP server that exposes content, delivery, analytics, automation, deployment, brand, personalization, marketplace, and customer-data tools, plus an Agent OS MCP client for remote tools.
Concrete capability record
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
Entries, assets, content models, releases, branches, workflows, versions and audit logs; published delivery content; analytics; automations; Launch projects and deployments; BrandKit; Marketplace apps; Personalize experiences; and Lytics audiences and profiles.
Read draft or published content and assets; inspect models, releases, workflows, versions and audit logs; and query analytics, automation state, deployment logs, brand context, marketplace installations, personalization results, and entitled Lytics data.
Create, update, delete, localize, publish, and unpublish content or assets; manage branches, releases, folders, apps, OAuth settings, personalization objects, automations, deploy hooks, deployments, uploads, and CDN revalidation within enabled groups.
The local server enables selected tool groups. Most groups use Contentstack OAuth; CMA can instead use a management token, CDA uses a delivery token, and Lytics uses its own access token. Stack, project, organization, and region context may also be required.
Enable only the groups needed for the task and keep provider and Agent OS client roles distinct. Preview target stack, branch, environment, locale, release, and identifiers before publishing, deletion, deployment, cache, automation, app, or personalization changes.
The provider runs locally through npx over stdio and requires Node.js 18 or later. Authentication and required context vary by group; dedicated infrastructure may need endpoint overrides, and stack-aware metadata is cached for five minutes per connection.
First-party access
Agent access
Support: Official MCP server + 3rd Party MCP services
Read scope: Bridges Content Management and Delivery APIs plus Analytics, Automations, Launch, BrandKit, Personalize, Developer Hub and Lytics; supports content and asset operations plus extended administration/governance tools
Write scope: State-changing tools are present in the documented scope; review the official tool catalog and require confirmation for consequential actions.
Authentication: Interactive Contentstack OAuth for most groups, with management-token support for CMA/CMA Extended and static delivery or Lytics tokens for their respective groups.
Approval boundary: Require explicit review for publish or unpublish, delete, branch or release changes, automation activation or execution, deployments, cache revalidation, Marketplace app or OAuth changes, and personalization mutations.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Proposed customer-shaped experiences
The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that Contentstack ships them.
Evidence and dates
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
Official Contentstack documentation confirms an operational first-party server and separately documents Agent OS as an MCP client. Keep provider and consumer roles distinct; tool groups and auth requirements should be…
Targeted first-party MCP/agent-role review; broader API inventory retained
First-party API reference or API overview recorded for this platform.
Full-profile first-party re-verification on 2026-07-12; see the private audit ledger.
First-party developer documentation or platform overview.
Inventory source: structurally normalized; content was not individually reopened in this pass.
Reverified the named access facet exactly as bounded by the reviewed first-party record.
Full-profile first-party re-verification on 2026-07-12; see the private audit ledger.
First-party product homepage used to confirm product identity and current positioning.
Inventory source: structurally normalized; content was not individually reopened in this pass.
First-party MCP documentation or product announcement recorded for this platform.
Inventory source: structurally normalized; content was not individually reopened in this pass.
First-party webhook, event, SDK, embedded-app, or extension documentation.
Inventory source: structurally normalized; content was not individually reopened in this pass.
Tied to cited first-party evidence reviewed for this profile.
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
System role, maturity interpretation, and architectural boundary.
Interface patterns and compositions—not vendor product claims.
