Payload CMS MCP Server

Most CMS servers hand an agent the content API. This one stays on the development side: it checks the Payload code a model just wrote against 3.0 rules and reports what is wrong with it. Collections, fields, globals and config files each have their own validation path, so a field definition is judged as a field rather than as generic TypeScript. The generation half emits templates for hooks, access control, endpoints, plugins, blocks and migrations, and scaffold_project lays out a whole project after its options pass the same validation. The practical value is narrow and real: a model that has not memorised Payload 3.0 field types finds out immediately, not at build time.