Prismic CLI

AI coding agents are already great at writing code, reading designs, and building components, and Prismic fits naturally into that workflow. The one piece agents couldn't reach on their own was the Prismic-specific work that lived in the UI or in model files, like starting a project, modeling content, or syncing types.

The Prismic CLI gives agents a reliable way to do that work from the terminal, an interface they already know how to use. Ask Claude, Cursor, ChatGPT, or Codex to build with Prismic, and the agent runs official commands to set up the project, model content, and get you to a working local preview. Fewer setup dead ends, less manual clicking, a clearer path from prompt to running project.

What you can do

Ask your agent to:

• initialize a Prismic project in your codebase, with the SDKs and config wired up
• model content and sync types without hand-editing model files
• go from prompt to a working local preview of your first page

How to try it

Point your agent at the docs and tell it what you want. For example:

Set up Prismic in this Next.js project and get me to a working local preview of my first page. Use the Prismic CLI and follow the official docs.

CLI and MCP work together

The CLI and the Prismic MCP cover different jobs. The CLI is the developer surface for project setup, content modeling, sync, and local development. The Prismic MCP is the content surface, where agents read, edit, and manage content. So while you're building, you can use the MCP to populate content and test the pages you develop straight from your agent, instead of hand-filling the editor. Build the project with the CLI, then run content operations with the MCP.

Note: The Prismic CLI replaces the old prismic/prismic-mcp-server for AI-assisted slice coding. If you land on the old GitHub repo, head to the Prismic CLI instead.