@prismicio/mcp-server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| 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:
RETURNS: Step-by-step modeling instructions, naming conventions, final Prismic model shapes, comprehensive field shape reference, opinionated modeling guidance, validation and testing steps. |
| 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. |
| 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. |
| 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. |
| 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/prismicio/prismic-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server