November 2026 Summaries

A Strapi 5 tutorial describes building a Content Publisher plugin that centralizes cross-posting from the Strapi admin to Dev.to, Medium, Bluesky, LinkedIn, and Facebook, while also exposing publishing capabilities through custom Model Context Protocol tools and an AI chat. The plugin maintains hidden tracking records for selected content types through database lifecycle hooks, records platform URLs, and routes all publishing interfaces through a single service that validates publication status, platform settings, credentials, field mappings, and duplicate posts. Administrators configure publishable collection types, field mappings, API credentials, and OAuth connections, while role-based permissions protect admin pages, routes, UI controls, settings, and individual MCP tools. Editors can publish from a searchable plugin table or an injected Content Manager sidebar panel, and public read-only API routes can provide platform links to frontend sites. The AI chat, built with the Vercel AI SDK and Strapi MCP server, restricts available tools according to each editor’s access rights and requires explicit user approval before any irreversible publishing action. The tutorial also highlights testing restricted roles, drafts, token-scoped MCP permissions, approval behavior, and image accessibility requirements for external platforms.