Tell your agent exactly what safe means.
These prompts work with Codex, Claude, Cursor, custom agents, and other MCP clients. Replace the angle-bracket placeholders with your project values. Begin read-only, review a preview, then authorize a draft.
A reliable prompt structure
Read-only project discovery
Confirm the connection and understand the content model before allowing any write.
Use the configured Safe Strapi MCP server. 1. List available projects. 2. List component schemas for <project-name>. 3. Find the page with slug <page-slug>. 4. Inspect its dynamic-zone component order and content hash. Do not create, update, delete, or publish anything.
Update copy on a safe draft
Clone a page and patch one known component without touching the source.
Use Safe Strapi for project <project-name>. Find and inspect <page-slug>. Preview a clone that changes the title field on component index <index> to: "<new-title>" Show the source hash, operation hash, proposed slug, and exact changed paths. Do not write until I approve the preview.
Insert a component from JSON
Validate supplied JSON against the live project schema, then place it precisely.
Use Safe Strapi for project <project-name>. Inspect <page-slug> and fetch the schema for <component-uid>. Validate this JSON against that schema: <json-payload> Preview a cloned draft that inserts it after component index <index>. Preserve every field on every existing component. Do not write yet.
Move, duplicate, or replace a block
Use explicit zero-based indexes so repeated component types never become ambiguous.
Inspect <page-slug> in <project-name> and show the current indexed component order. On a cloned draft only: - move component index <from-index> after index <target-index> - duplicate component index <duplicate-index> at the end - replace component index <replace-index> with <component-json> Preview the sequential result first. If any selector is ambiguous or invalid, stop and explain it.
Protect a 100+ component page
Make several targeted changes while explicitly checking that unrelated fields survive.
Inspect the complete <page-slug> page in <project-name> and capture its source hash. Preview these operations in order on a clone: 1. Patch component #50 with <changes>. 2. Move component #80 after component #10. 3. Insert <component-json> after component #25. Use explicit indexes and a stable idempotency key. After creation, re-fetch the draft, validate it, compare it with the source, and confirm that every field outside the approved changes is preserved. Re-fetch the source and prove its hash is unchanged. Never publish.
Create a review-ready campaign draft
Turn a content brief into a named draft that editors can review in Strapi.
Use Safe Strapi to create a review draft from <source-page> in <project-name>. Brief: <campaign-brief> First inspect the page and relevant component schemas. Propose the smallest set of component operations and preview them. Use clone slug <review-slug> and title suffix " (Content Review)". After I approve, create the draft, validate it, compare it with the source, and return a concise review summary. Do not publish.
Respond safely to a conflict
Never force a stale operation through after another editor or agent changes content.
Continue the Safe Strapi operation only if the current source and draft hashes match the last inspected hashes. If you receive SOURCE_CHANGED or DRAFT_CHANGED, stop, inspect again, and show what changed before proposing a new preview. If you receive WRITE_OUTCOME_UNKNOWN, do not retry the create automatically. Never reuse an idempotency key for different operations.
Let an AI client read this guide
Give your agent the raw guide URL and ask it to choose the safest matching workflow. The Markdown version contains tool rules, placeholders, and every prompt without page chrome.
Read https://safe-strapi-mcp.metehankasapp.workers.dev/prompts.md Choose the safest matching Safe Strapi workflow for my request. Start read-only and do not write until you show me a preview.
Discovery metadata is also available at /llms.txt.