Scaffolds a new Payload project or adds Payload to an existing Next.js or TanStack app
Payload CMS tools that run in the terminal 25
Sorted by what a command writes to: your source code, the content in your database, or nothing at all, as with the linters and live security probes.
Governance checks and ESLint rules for Payload project structure, access code and hooks
Automated code transforms that move a Payload project past breaking changes
Idempotent seed runner that fills a Payload database with ordered, cross-referenced content
CLI and registry that installs wired Payload blocks into Next.js projects
Migrates WordPress posts, pages, media, SEO and redirects into Payload
Migrates WordPress sites to Payload from a WXR export file
Shared lint, test and quality configs that keep Payload projects consistent
Converts WordPress WXR exports into Astro, Next.js, Payload or Pruvious projects
CLI and terminal UI to create and manage multi-tenant Payload sites from one backend
Lets AI agents and scripts read, edit and sync Payload content from the command line
Reusable Cursor coding-agent rules for Bun, commits, TypeScript and clean code
Command-line SEO checks and REST sync for Payload content, built for AI agents
Audits a Payload instance for data leaks by probing collections and GraphQL anonymously
Static linter that flags access control and security mistakes
Command-line access to Payload collections, globals and documents for AI agents
Installs a block-based page builder and CMS into an existing Next.js app
Command-line client for managing Payload documents, media and auth from a terminal
Runs create, update, delete and upsert on Payload collections from the terminal
Claude Code skills and Figma knowledge modules for plugins and design-to-code work
About these packages
This tag gathers every tool with a command-line entry point, whatever its category. Before you run one, know what it writes to.
- Source code: Create App and Codemod for new projects and upgrades, Components and Basepl for ready-made blocks and fields, Collection Registry for generated types and clients
- Content in your database: WP to and WP Migrate Core for WordPress imports, Dummy for seed data, Collection CLI and PCMS CLI for direct edits
- Content, through an AI agent: Content CLI, Payload CLI and SEO CLI
- Nothing, only a report: Doctor lints access control, Security probes a running site for data readable without login, Compiler Check flags client-side imports
Dummy's seed units are idempotent, so running them twice is safe. Try the WordPress importers against a staging database first.
Starter generators with a CLI are listed under templates, and the CLI category is the narrower list of scaffolding and content tools.



