Prismic Content MCP

Get active repository context for this MCP server.

Returns repository and API base URL metadata (no secrets) so agents can identify which Prismic repository they are operating on. Recommended first call in a session to confirm repository and auth posture before running read/write workflows.

Get repository refs from Content API root.

Refs are repository-level version pointers (for example master, preview, or release refs), not per-document refs. Use returned ref values with prismic_get_documents or prismic_get_document to read content for that version pointer. Efficiency tip: call once, cache the chosen ref, and pass it explicitly to subsequent read calls to avoid per-call implicit master-ref resolution.

Get repository custom types from Content API root.

Returns content type metadata from the Content API types map as normalized entries with id and label. Typical sequencing: call once, then iterate type ids with prismic_get_documents(type=..., page_size=1) when you only need counts or existence checks.

Get release refs from Content API root.

Returns non-master refs only, equivalent to filtering repository refs by isMasterRef != true. Use these refs with read tools (ref parameter) to inspect release content through Content API. Note: querying documents with a release ref returns a content snapshot at that ref, not only the release "planned items" shown in Prismic UI. Efficiency tip: pick the release ref once and reuse it across all read queries in the same analysis.

List full Custom Type models from Prismic Custom Types API.

Uses GET /customtypes on https://customtypes.prismic.io (override via PRISMIC_CUSTOM_TYPES_API_BASE_URL). Requires:

• PRISMIC_REPOSITORY

• PRISMIC_WRITE_API_TOKEN

Get one Custom Type model and schema summary by ID.

Uses GET /customtypes/{id}. When include_schema_summary=true, returns:

• tab/field breakdown

• field config for each field

• required flags where present in field config

• shared slice choices configured inside Slices fields

This is the recommended verification call after create/update operations.

Insert a new Custom Type model.

Uses POST /customtypes/insert. Pass a full Custom Type JSON model (including id, label, repeatable, and json tabs/fields).

Update an existing Custom Type model.

Uses POST /customtypes/update. Pass the full updated Custom Type JSON model. Typical sequence:

1. prismic_get_custom_type

2. edit model JSON

3. prismic_update_custom_type

4. prismic_get_custom_type to verify schema

List all Shared Slice models from Prismic Custom Types API.

Uses GET /slices.

Get one Shared Slice model by ID.

Uses GET /slices/{id}.

Insert a new Shared Slice model.

Uses POST /slices/insert. Pass a full Shared Slice JSON model.

Update an existing Shared Slice model.

Uses POST /slices/update. Pass the full updated Shared Slice JSON model.

List documents with optional Prismic predicate filtering.

Use ref to read from an explicit Prismic content ref (for example preview/draft refs). When omitted, master ref is used. Depending on repository API visibility settings, reading non-master refs may require PRISMIC_CONTENT_API_TOKEN. Use q for explicit Content API predicates (for example [[at(document.tags,"news")]]). type is a convenience shortcut for [[at(document.type,"<type>")]] and is merged into q. Use orderings for native Content API sort clauses (for example [document.first_publication_date desc]). Use routes for Content API route resolvers to populate the url field (for example [{"type":"page","path":"/:uid"}]). Note: there is no documented Content API q predicate for "published status". A release ref query returns a version snapshot, not only release-delta documents. Efficiency tips:

• For large scans: call prismic_get_refs once and pass ref explicitly.

• For counts/existence checks: set page_size=1 and read total_results.

• Only pass routes when you need populated url fields.

• Paginate with page + next_page for full exports. Codex js_repl tip: codex.tool(...) wraps tool output; read payload from result.Ok.structuredContent.

Get one document by id or by type+uid with optional explicit ref.

Use ref to read a specific preview/release version pointer. Depending on repository API visibility settings, non-master refs may require PRISMIC_CONTENT_API_TOKEN. The document payload has no explicit status field (for example published/draft/in-release). To determine publish state on master, use this sequence:

1. Call prismic_get_refs and capture the master ref.

2. Call prismic_get_document(..., ref=<master_ref>).

3. Call prismic_get_document(..., ref=<release_ref>) as needed.

4. Interpret results:

   • exists on master: published on master

   • missing on master but exists on release ref: not published on master (release-only content) Prefer this over prismic_get_documents when you already have an exact id or type+uid target.

List media assets from Prismic Asset API.

This maps directly to GET /assets query parameters: assetType, limit, cursor, and keyword. Requires PRISMIC_REPOSITORY and PRISMIC_WRITE_API_TOKEN.

Upload media via Prismic Asset API.

Uploads file_path using multipart/form-data to POST /assets. Optional metadata maps to Asset API fields: notes, credits, alt. Requires PRISMIC_REPOSITORY and PRISMIC_WRITE_API_TOKEN. Security: PRISMIC_UPLOAD_ROOT must be set; upload paths must resolve within that directory (traversal and symlink escapes are blocked).

Create/update one document in the Prismic Migration API.

Important behavior:

• This writes to the Migration workflow (Migration UI/release flow).

• New/updated documents may not be visible via Content API master reads immediately (or at all) until they are included in the readable release flow/published in Prismic.

• To read back migrated content before publish, fetch a release ref via prismic_get_releases/prismic_get_refs, then query read tools with that ref (and provide PRISMIC_CONTENT_API_TOKEN when required).

• Use dry_run=true to validate payload/endpoint choice without writing.

Batch create/update documents in the Prismic Migration API.

Important behavior:

• This writes to the Migration workflow (Migration UI/release flow).

• Batch-created/updated documents may not be visible via Content API master reads until release/publish workflow makes them readable.

• For read-back before publish, use a release ref with read tools (ref parameter), plus PRISMIC_CONTENT_API_TOKEN if repo settings require authenticated reads.

• Supports dry_run and fail_fast for safer execution.