Skip to Content
MCP serverAvailable tools and actions

Available tools and actions

Depending on your user role permissions and the MCP server permissions of the environment, the Prepr MCP server allows an AI client to perform actions using the tools listed below.

Context and discovery

The AI client can inspect environment settings, locale configurations, and content models to safely map out your data layout.

  • get_initial_context - Bootstrap the session with environment metadata, locales, workflow stages, current user, and a schema summary.
  • list_schema- Browse schema definitions.
  • list_locales - See which locales exist in the current environment before reading or changing localized content.
  • list_workflow_stages - Discover the valid workflow stages you can move content through.
  • list_users - Find assignable users before assigning content items.
  • get_current_user - Resolve the currently authenticated user, especially for requests like “assign to me”.

Content management

The AI client can locate, filter, and fetch your existing content. If granted write access, it can also actively build, modify, transition, publish, assign, comment on, or delete items inside Prepr. Deleting always requires explicit confirmation.

  • query_items - Search and filter content items when you need one or more matching candidates.
  • get_item - Fetch a single content item when you already know its exact Content Item ID.
  • create_item - Create one localized content item in a specific model.
  • update_item - Fully update one localized content item while keeping the existing locale payload shape intact.
  • patch_items - Patch supported root-level fields on an existing localized content item without sending a full update payload.
  • publish_items - Publish one or more localized content items now or schedule them for later.
  • unpublish_items - Unpublish one or more localized content items in a specific locale.
  • change_workflow_stage_items - Move one or more content items to a different workflow stage.
  • assign_items - Assign one or more localized content items to a specific user.
  • unassign_items - Remove the assigned user from one or more localized content items.
  • add_comment - Add an editorial comment to a content field on a localized content item.
  • delete_items - Permanently delete an entire content item across all locales, with explicit confirmation.
  • delete_item_locale - Permanently delete one locale from a content item, with explicit confirmation.

Asset management

The AI client can locate, filter, and fetch your existing assets and upload new ones. If granted write access, it can also edit and delete assets and manage asset folders inside Prepr. Deleting always requires explicit confirmation.

  • query_assets - Search and filter assets such as images, videos, audio, documents, and PDFs. Filter by folder with a folder UUID or asset-folder:// URI.
  • get_asset - Fetch a single asset when you already know its exact Asset ID. The response includes metadata, tags, localized custom fields, and the public file URL.
  • upload_asset_from_public_url - Import a public image, audio file, or document URL into Prepr as an asset.
  • create_asset_upload_url - Creates a public image, audio file, or document in Prepr as an asset.
  • upload_asset_from_chatgpt_file - Import ChatGPT attachments and generated files.
  • update_asset - Update an asset’s internal name, description, author, and tags, as well as its localized custom fields of type Text, Integer, Float, Boolean, and Enum. Omitted values are preserved, supplied tags replace the complete tag list, and null clears a custom field.
  • delete_asset - Permanently delete one asset, with explicit confirmation. Prepr may reject the deletion when the asset is in use.
  • create_asset_folder - Create a new asset folder.
  • update_asset_folder - Rename an existing asset folder.
  • delete_asset_folder - Delete an asset folder, with explicit confirmation. The assets in the folder are preserved.

Schema management

If granted Schema → Write access by both your user role and the MCP server permissions of the environment, the AI client can create and change the models, components, enumerations, and fields that make up your schema.

  • get_schema_entity - Inspect individual schema entities, like models and components.
  • create_schema_model - Create a new model in the schema.
  • update_schema_model - Update the settings of an existing model.
  • create_schema_component - Create a new component in the schema.
  • update_schema_component - Update the settings of an existing component.
  • create_schema_enum - Create a new enumeration in the schema.
  • update_schema_enum - Update the values or settings of an existing enumeration.
  • delete_schema_entity - Permanently delete a model, component, or enumeration, with explicit confirmation.
  • create_schema_field - Add a new field to a model or component.
  • update_schema_field - Update the settings of an existing field.
  • move_schema_field - Change the position of a field within a model or component.
  • delete_schema_field - Permanently delete a field from a model or component, with explicit confirmation.

Feedback

The AI client can report problems with the MCP server to Prepr.

  • give_feedback - Report MCP tool issues such as broken behavior, missing capabilities, confusing output, or unclear documentation.
Last updated on