Use cases

Use these examples to explore practical workflows for the Prepr MCP server.

Create a content item from an external content source

Use this workflow when your team drafts blog posts, landing pages, or announcements in an external source like Google Drive before publishing them in Prepr.

1. Make sure your AI client can access the source document through a shared link, a connected document source , or a local export.
2. Tell the AI which Prepr content model and locale to use.
3. Ask it to copy only the relevant fields and define which status to put it in and who to assign it to.

Example prompt:

Find the draft article document, Top 20 AI trends in 2026, in my Google Drive, and create a new Post item in Prepr for locale en-GB. Copy the title, intro, and body content, set the workflow stage to Review, and assign it to Mike. If a required field is missing, ask me before creating the item.

Create demo content based on your Prepr schema

Use this workflow when you want to quickly populate a new environment with realistic sample content based on the content models in your Prepr schema.

1. Tell the AI which content models should be populated first.
2. Specify the locale, number of demo items, and the tone or subject matter you want to use.
3. Ask it to inspect the schema so it can generate values that match the required fields and field types.
4. Review the created items and refine them before using them in demos, previews, or QA.

Example prompt:

Review my Prepr schema and create demo content for the Post, Author, and Category models in locale en-US. Create 10 realistic blog posts with matching author profiles and categories. Use complete values for required fields and keep the content suitable for a product demo.

Audit unpublished content

Use this workflow when you want to review content quality before publishing.

1. Ask the AI to check for missing fields, metadata, and asset references.
2. Review the results and decide which items should be updated first.

Example prompt:

Audit my unpublished blog posts. List any drafts that are missing a featured image, SEO title, or author profile.

Update existing content from review feedback

Use this workflow when feedback is stored in a document and needs to be applied to an existing content item.

1. Make sure your AI client can access the feedback document through a shared link, a connected document source , or a local export.
2. Specify the content model, locale, and the fields that may be changed.
3. Ask it to keep important identifiers such as the slug unchanged unless you explicitly request otherwise.

Example prompt:

Review the feedback in this document and update the matching Post item in Prepr for locale en-US. Keep the existing slug, update the body copy and summary, and move the item to Ready for review.

Make recommendations to merge similar articles

Use this workflow when your content library contains overlapping articles and you want help identifying which items should be merged, consolidated, or retired.

1. Ask the AI to compare articles on similar topics across a specific model or section of your content library.
2. Tell it to highlight duplicate themes, overlapping titles, repeated keywords, and outdated or thin content.
3. Ask it to recommend which article should remain the primary item and which ones should be merged, redirected, or archived.

Example prompt:

Review all Post items in my Help Center category and identify articles that cover very similar topics. Recommend which items should be merged, which one should remain as the main article, and which ones should be archived or redirected.

Replace outdated branding information based on a branding style guide

Use this workflow when your company updates product names, tone of voice, terminology, or messaging guidelines and you want to apply them consistently across your content.

1. Make sure your AI client can access the branding style guide through a shared link, a connected document source , or a local export.
2. Tell the AI which content models or sections should be reviewed first.
3. Ask it to find outdated brand terms, inconsistent naming, and messaging that no longer matches the current style guide.
4. Review the proposed changes before applying them across multiple content items.

Example prompt:

Review the branding style guide in this document and compare it with all LandingPage and Post items in locale en-US. Identify outdated product names, old taglines, and inconsistent terminology, then suggest the updates needed to align the content with the new brand guidelines.

Prepare localized content

Use this workflow when you manage more than one locale and want help creating or updating localized entries.

1. Identify the source item and the target locale.
2. Tell the AI whether it should create a new localized item or update an existing one.
3. Ask it to flag any fields that need manual translation or editorial review.

Example prompt:

Review the Dutch version (locale nl-NL) of the existing LandingPage item based on the English source. Check for inconsistencies between the language variants and suggest alternative translations.

Update workflow state across a batch of items

Use this workflow when content operations need to be coordinated across many entries at once.

1. Define a clear filter such as a model, tag, locale, or workflow state.
2. Ask the AI to show the affected items before applying changes.
3. Apply assignment or workflow changes only after confirming the batch looks correct.

Example prompt:

Find all Article items tagged spring-campaign in locale en-US, assign them to Sarah, move them to In review, and show me the list of affected items before applying the changes.

Bulk-create content items for a migration

Use this workflow when content is being migrated from another CMS, a spreadsheet export, or a folder of structured documents.

1. Put the migration source files, mappings, and any transformation notes in a location your AI client can access.
2. Tell the AI which content model and locale to target.
3. Ask it to report missing required fields and mapping problems instead of silently skipping records.
4. Create drafts first, then validate the batch before publishing anything.

Example prompt:

Using the migration data in this folder, create draft Post items in Prepr for locale en-US. Map each source file to one content item, preserve the publish date when available, and report any rows that are missing required fields instead of skipping them silently.

Validate migration output before publishing

Use this workflow after a bulk import to confirm that the created content items are complete and consistent.

1. Ask the AI to inspect only the affected batch or a known list of content items.
2. Have it check for missing fields, missing assets, and unexpected workflow states.
3. Review the exceptions report before running any publish actions.

Example prompt:

Review the Post items created during this migration batch. List any items with missing required fields, missing assets, or an unexpected workflow stage, and do not publish anything yet.

Prepare content operations alongside code changes

Use this workflow when a release includes both implementation work and related content updates.

1. Give the AI access to the relevant repository or release notes.
2. Ask it to compare the implementation or new copy with the corresponding Prepr items.
3. Review the proposed content changes before asking it to apply them.

Example prompt:

Compare the new feature copy in this repository with the corresponding LandingPage items in Prepr. List the content items that need updating and draft the recommended field changes before making any edits.