@prismicio/mcp-server

PURPOSE: Provide detailed, opinionated guidance to create or update Prismic slice model files using modern best practices, including naming, file placement, allowed fields, shapes, and configuration. USAGE: Use FIRST for any Prismic slice creation or modeling request. Do not use for component or mock implementation. Input Type Selection Rules: - If the user attaches an image, include "image". - If the user attaches code, include "code". - Include "text" ONLY if the prompt contains model-related information (e.g., explicitly describes desired fields/structure, adds nuance, or overrides what is seen in the code/image). - It is acceptable to include multiple input types when each adds model-relevant signal per the rules above. RETURNS: Step-by-step modeling instructions, naming conventions, final Prismic model shapes, comprehensive field shape reference, opinionated modeling guidance, validation and testing steps.

PURPOSE: Generate a model-valid slice mock (mocks.json) and provide guidance for text-only refinements. USAGE: Use when creating or updating slice mocks. RETURNS: A JSON mock covering all variations, plus guidance for text-only refinements.

PURPOSE: Provides slice and field implementation guidance for Prismic slice components. USAGE: Use FIRST when working with any Prismic slice component or field implementation. RETURNS: Prismic Framework-specific field documentation and code examples.

PURPOSE: Creates or updates a Prismic slice model and/or mocks in your project with given valid data, performing local changes to the slice library. USAGE: Use to validate and create/update slice data (model and/or mocks). RETURNS: Success confirmation or detailed validation errors if the data is invalid.

PURPOSE: Adds a slice to a custom type. USAGE: Required path for modifying Prismic slice registrations. Adds/registers/attaches a slice to a custom type and regenerates types. Do not edit custom type JSON files manually; this tool performs validation and follow-up steps. RETURNS: A message indicating whether the slice was added to the type or not, and detailed error messages if it is not.