LoginSign Up
← Back to all sparks
D

DatoCMS

INFRA · APIS
Velocity0.0

DatoCMS is opening the CMS to agents while hardening the media pipeline.

headless-cmsmcpagent-accessmedia-pipelinevisual-editingdeveloper-experience
◆Current state
Two bodies of work sit side by side. The dated entries through spring covered developer onboarding - OAuth project linking, an npx CLI that works without setup, plugin scaffolds in the starter kits, a raised CMA limit - plus automatic antivirus scanning on every Media Area upload. The undated stream since then has been agent access and editing surface: DatoCMS Agent Skills, a Remote MCP Server, Visual Editing and its sidebar previews, a media editor covering video, and responsive images that size themselves across every SDK.
◆Where it's heading
DatoCMS is making the CMS addressable by something other than a human in the dashboard. Agent Skills and the Remote MCP Server give agents a defined way in; the CLI and CMA work over the preceding months removed the setup rituals that made programmatic access awkward; Visual Editing pulls the editing surface out to where content is rendered. The media pipeline is being hardened on a parallel track - antivirus by default, asset collection permissions, focal points, video frame selection - which is the part that turns up in enterprise procurement. Neither thread has slowed.
◆Prediction
With Agent Skills and MCP shipped, the natural follow-up is scoping and permissions for agent access - the equivalent of asset collection permissions applied to what an agent may read or write - since DatoCMS has already built the roles machinery to hang it on.

◆Recent moves

  1. 3mo ago

    CLI: `npx datocms` now Just Works

    The npx datocms CLI now runs without the setup steps that used to precede it. One of several entries clearing the friction between a developer and a working project - the groundwork that made the later agent and MCP access practical.

    View source ↗
  2. 4mo ago

    CMA limit raised for Developer Plan

    The Content Management API limit goes up for Developer Plan projects. A quota change rather than a feature, but it lands on the plan tier where programmatic use starts.

    View source ↗
  3. 4mo ago

    CLI: Easier (and safer) project linking with OAuth

    Project linking moves to OAuth, replacing copy-pasted API tokens with a browser flow. It removes a credential-handling step that every new project used to require, and it is safer by default rather than by configuration.

    View source ↗
  4. 4mo ago

    Starter kits now ship with a plugin scaffold

    Starter kits ship with a plugin scaffold, so extending the CMS starts from a working template instead of a blank directory. It is a small push on the plugin ecosystem that the sidebar-tab fix later made more visible to editors.

    View source ↗
  5. 4mo ago

    Automatic antivirus scanning for all Media Area uploads

    ⚡ SPARK

    Every Media Area upload is scanned automatically, with infected files quarantined and purged from the CDN, status badges in the dashboard, a meta.antivirus field on the CMA, and webhooks on status change. It is the anchor of the media-hardening thread that asset permissions and the media editor continue.

    View source ↗
  6. 4mo ago

    Configurable `hue` property on Visual Editing

    A configurable hue property on Visual Editing overlays. Cosmetic, though it arrives at the start of the Visual Editing run that later extended into sidebar previews.

    View source ↗