Skip to main content
Glama
Sign In
@prismicio/mcp-server

@prismicio/mcp-server

Official
by prismicio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote
IMPORTANT

This package is no longer recommended for building Prismic websites with AI. Follow the new Prismic CLI-based approach instead:Build with AI in Prismic.

For Prismic content management through MCP, use Prismic’s server-side MCP server: Prismic MCP documentation.

@prismicio/mcp-server

npm version npm downloads Github Actions CI Codecov Conventional Commits License

Prismic Model Context Protocol (MCP) Server.

Install

{
	"mcpServers": {
		"prismic": {
			"command": "npx",
			"args": ["-y", "@prismicio/mcp-server@latest"]
		}
	}
}

Related MCP server: Echo MCP Server

Documentation

To discover what's new on this package check out the changelog. For full documentation, visit the official Prismic documentation.

Contributing

Whether you're helping us fix bugs, improve the docs, or spread the word, we'd love to have you as part of the Prismic developer community!

Asking a question: Open a new topic on our community forum explaining what you want to achieve / your question. Our support team will get back to you shortly.

Reporting a bug: Open an issue explaining your application's setup and the bug you're encountering.

Suggesting an improvement: Open an issue explaining your improvement or feature so we can discuss and learn more.

Submitting code changes: For small fixes, feel free to open a pull request with a description of your changes. For large changes, please first open an issue so we can discuss if and how the changes should be implemented.

For more clarity on this project and its structure you can also check out the detailed CONTRIBUTING.md document.

License

Copyright 2013-2025 Prismic <contact@prismic.io> (https://prismic.io)

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

Available Tools

5 tools
add_slice_to_custom_typeA

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.

Inputs: sliceMachineConfigAbsolutePath (required), sliceDirectoryAbsolutePath (required), customTypeDirectoryAbsolutePath (required).

how_to_code_sliceA

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.

Inputs: sliceMachineConfigAbsolutePath (required), projectFramework (required), stylingSystem (required), modelAbsolutePath (required), +1 more.

how_to_mock_sliceA

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.

Inputs: sliceMachineConfigAbsolutePath (required), sliceDirectoryAbsolutePath (required), userIntent (required).

how_to_model_sliceA

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.

Inputs: sliceMachineConfigAbsolutePath (required), sliceName (required), isNewSlice (required), contentRequirements (required), +1 more.

save_slice_dataB

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.

Inputs: sliceMachineConfigAbsolutePath (required), sliceAbsolutePath (required), data (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.8/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct aspect of Prismic slice work: registration, coding guidance, mocking guidance, modeling guidance, and saving model/mock data. No two tools overlap in purpose.

    Naming Consistency3/5

    Two naming patterns exist: 'how_to_*' for guidance tools and verb_noun for action tools (add_slice_to_custom_type, save_slice_data). While readable, the mix of patterns reduces consistency.

    Tool Count5/5

    Five tools is appropriate for a focused server on Prismic slice management, covering key development tasks without being excessive or insufficient.

    Completeness4/5

    The tool set covers the main workflows for Prismic slice development: adding to custom types, guidance for coding/mocking/modeling, and saving data. Minor gaps like missing delete or list operations are acceptable given the server's assisting role.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Resources

    Related MCP Connectors

    Related MCP Servers

    • Echo MCP Server

      somacaru
      F
      license
      Not graded
      quality
      D
      maintenance
      A simple demonstration MCP server that provides an echo tool and resource for learning how to build MCP servers. Serves as a starting point and template for creating custom MCP server implementations.
      1
      -

    • make-mcp

      D1DX
      A
      license
      Not graded
      quality
      F
      maintenance
      This MCP server provides integration with Make.com (formerly Integromat) for workflow automation. It is now deprecated and replaced by Make's official cloud MCP.
      164 npm
      4
      MIT