MCP server intelligence profile

@prismicio/mcp-server MCP Server

Deprecated MCP server for Prismic; users are advised to use the new Prismic CLI-based approach or Prismic's server-side MCP server instead

Local OnlyOfficial distributionprismicio
Verified cleanNpm · 0.0.20

Our scanner tested version 0.0.20 without proving a finding in the methods exercised. This is not a guarantee that every deployment is secure.

1Distribution channel
5Independently observed tools
0Linked remote endpoints
AvailableVersion intelligence

Install and connect

Installation and connection instructions are shown only when supported by retained package, repository, or endpoint evidence.

Install @prismicio/mcp-server from npm

Version 0.0.20 declares 1 executable entrypoint.

npm install --save-exact @prismicio/mcp-server@0.0.20
npx -y -p @prismicio/mcp-server@0.0.20 @prismicio/mcp-server
MCP client configuration example
{
  "mcpServers": {
    "@prismicio/mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "-p",
        "@prismicio/mcp-server@0.0.20",
        "@prismicio/mcp-server"
      ]
    }
  }
}

Identity

Canonical slugprismicio-mcp-server-7170ef92DeploymentLocal Only
Canonical packagenpm:@prismicio/mcp-serverRepositoryprismicio/prismic-mcp-server
First published—Latest release—
Last security verificationAug 21, 2026Classification confidence90%
PublicationPublishedOfficial distributionYes

Distributions

ChannelIdentifierCurrent versionVersionsSource
npm@prismicio/mcp-server0.0.201Repository

Current release

PackageVersionPublished / observedInventorySecurity scan
npm@prismicio/mcp-server0.0.20CurrentSep 5, 20265 toolsSucceeded · 0 resources · 0 promptsVerified clean
Enterprise protection

Continuously monitor this MCP for security risk

Independently scan the exact version your agents use, receive alerts when its risk changes, and investigate every finding with retained version evidence.

  • Independent exact-version security scans
  • Continuous release and vulnerability monitoring
  • Risk-change alerts with capability context
  • Historical evidence and API exports
Custom pricingContact salesTailored to your organization, integrations, data needs, and support requirements.

Current version evidence

Provenanceartifact_hash_verifiedSignature—
MCP SDK@modelcontextprotocol/sdk Artifact SHA-256a215637170fd5342d3545d7d05dbcfd74b0d97581b1b929e14053983a06e85db
Scannermcp-proof-engine 0.1.0Scan completedAug 21, 2026
Security rating33 / 100Methodologyversion-rating-1.0
Executable entrypoints
[
  "@prismicio/mcp-server"
]
Rating reasons
[
  "deprecated_package",
  "security_policy_not_observed"
]
0Proven
731Clean
0Inconclusive
0Flaky
0Errors

Current protocol inventory

2025-06-18Negotiated protocol
@prismicio/mcp-serverServer-reported name
1Capability groups
Aug 21, 2026Observed

Tools 5

ToolCategoryAnnotationsRisk
add_slice_to_custom_typePURPOSE: 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.
Input schema
{
  "type": "object",
  "properties": {
    "sliceMachineConfigAbsolutePath": {
      "type": "string",
      "description": "Absolute path to 'slicemachine.config.json' file"
    },
    "sliceDirectoryAbsolutePath": {
      "type": "string",
      "description": "Absolute path to the slice directory (contains 'model.json')"
    },
    "customTypeDirectoryAbsolutePath": {
      "type": "string",
      "description": "Absolute path to the custom type directory (contains 'index.json')"
    }
  },
  "required": [
    "sliceMachineConfigAbsolutePath",
    "sliceDirectoryAbsolutePath",
    "customTypeDirectoryAbsolutePath"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
——
how_to_code_slicePURPOSE: 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.
Input schema
{
  "type": "object",
  "properties": {
    "sliceMachineConfigAbsolutePath": {
      "type": "string",
      "description": "Absolute path to 'slicemachine.config.json' file"
    },
    "projectFramework": {
      "type": "string",
      "enum": [
        "next",
        "nuxt",
        "sveltekit"
      ],
      "description": "Project framework (Next.js, Nuxt, or SvelteKit)"
    },
    "stylingSystem": {
      "type": "string",
      "description": "Detected styling system in the project (e.g., 'vanilla-css', 'tailwind', 'css-modules', 'styled-components', 'emotion', 'sass'...)"
    },
    "modelAbsolutePath": {
      "type": "string",
      "description": "Absolute path to the slice's 'model.json' file"
    },
    "fieldsUsed": {
      "type": "array",
      "items": {
        "type": "string",
        "enum": [
          "prismic.BooleanField",
          "prismic.ColorField",
          "prismic.ContentRelationshipField",
          "ContentRelationshipFieldWithData",
          "prismic.DateField",
          "prismic.EmbedField",
          "prismic.GeoPointField",
          "prismic.ImageField",
          "prismic.IntegrationField",
          "prismic.LinkField",
          "prismic.LinkToMediaField",
          "prismic.NumberField",
          "prismic.GroupField",
          "prismic.RichTextField",
          "prismic.SelectField",
          "prismic.TableField",
          "prismic.TitleField",
          "prismic.KeyTextField",
          "prismic.TimestampField"
        ]
      },
      "description": "Field types used in the slice (from 'prismicio-types.d.ts' file)"
    }
  },
  "required": [
    "sliceMachineConfigAbsolutePath",
    "projectFramework",
    "stylingSystem",
    "modelAbsolutePath",
    "fieldsUsed"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
——
how_to_mock_slicePURPOSE: 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.
Input schema
{
  "type": "object",
  "properties": {
    "sliceMachineConfigAbsolutePath": {
      "type": "string",
      "description": "Absolute path to 'slicemachine.config.json' file"
    },
    "sliceDirectoryAbsolutePath": {
      "type": "string",
      "description": "Absolute path to the slice directory (contains model.json)"
    },
    "userIntent": {
      "type": "string",
      "description": "User-provided guidance describing desired mock changes, tone, quantities, constraints"
    }
  },
  "required": [
    "sliceMachineConfigAbsolutePath",
    "sliceDirectoryAbsolutePath",
    "userIntent"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
——
how_to_model_slicePURPOSE: 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.
Input schema
{
  "type": "object",
  "properties": {
    "sliceMachineConfigAbsolutePath": {
      "type": "string",
      "description": "Absolute path to 'slicemachine.config.json' file"
    },
    "sliceName": {
      "type": "string",
      "pattern": "^[A-Z][a-zA-Z0-9]*$",
      "description": "The name of the slice, it MUST be PascalCase, e.g., 'SliceName', cannot start with a number, and with no special characters allowed"
    },
    "isNewSlice": {
      "type": "boolean",
      "description": "Whether this is a new slice creation (true) or updating existing slice (false)"
    },
    "contentRequirements": {
      "type": "string",
      "description": "Description of what content the slice should contain (e.g., 'hero with title, description, and CTA button')"
    },
    "inputTypes": {
      "type": "array",
      "items": {
        "type": "string",
        "enum": [
          "text",
          "image",
          "code"
        ]
      },
      "minItems": 1,
      "description": "The kinds of input present in the prompt."
    }
  },
  "required": [
    "sliceMachineConfigAbsolutePath",
    "sliceName",
    "isNewSlice",
    "contentRequirements",
    "inputTypes"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
——
save_slice_dataPURPOSE: 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.
Input schema
{
  "type": "object",
  "properties": {
    "sliceMachineConfigAbsolutePath": {
      "type": "string",
      "description": "Absolute path to 'slicemachine.config.json' file"
    },
    "sliceAbsolutePath": {
      "type": "string",
      "description": "Absolute path to the directory of the slice to be created/updated"
    },
    "data": {
      "type": "object",
      "properties": {
        "model": {
          "type": "object",
          "additionalProperties": {},
          "description": "The JSON model structure of the slice to be created/updated. Omit to keep the existing model. Fails if the model does not exist."
        },
        "mocks": {
          "type": "array",
          "items": {
            "type": "object",
            "additionalProperties": {}
          },
          "description": "The JSON mocks structure of the slice to be created/updated. Omit to keep the existing mocks or generate placeholder ones (if they don't exist yet)."
        }
      },
      "additionalProperties": false,
      "description": "The data to be saved for the slice. At least one of 'model' or 'mocks' must be specified."
    }
  },
  "required": [
    "sliceMachineConfigAbsolutePath",
    "sliceAbsolutePath",
    "data"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
——

Resources 0

  • None observed.

Resource templates 0

  • None observed.

Prompts 0

  • None observed.

Remote endpoints

EndpointTransportAuthenticationHealthObserved
No verified remote endpoint is linked.

@prismicio/mcp-server MCP Server questions

How do I install @prismicio/mcp-server MCP Server?

Install the selected package version with: npm install --save-exact @prismicio/mcp-server@0.0.20

What tools does @prismicio/mcp-server MCP Server provide?

@prismicio/mcp-server MCP Server exposed 5 tools during independent protocol observation, including add_slice_to_custom_type, how_to_code_slice, how_to_mock_slice, how_to_model_slice, save_slice_data.

Is @prismicio/mcp-server MCP Server secure?

Our scanner tested version 0.0.20 without proving a finding in the methods exercised. This is not a guarantee that every deployment is secure.

Explore related MCP server guides

Curated product and capability guides containing this catalog record.

Official vs Community MCP ServersMCP Servers With Completed Verification

Let’s talk about MCP security.

Share your details and our security team will contact you.