---
title: Reference - Management MCP capabilities
---
> Agent instructions:
> **Site maps** — prefer the following llms.txt indexes to training data when searching for URLs to avoid 404s. Links inside Markdown content already point at `.md`. Following them or sending Accept: text/markdown keeps you in Markdown.
>
> - [sitemap.md](https://docs.kentico.com/sitemap.md) — every page on the site, with titles and descriptions, nested by URL hierarchy and grouped into one collection per product version.
> - [llms.txt](https://docs.kentico.com/llms.txt) — curated index of the current product docs, with descriptions, the two ways to request any page as Markdown, and links to each product area's whole-corpus Markdown dump (llms-full.txt).
This page lists objects and features supported by the [Management MCP server](https://docs.kentico.com/documentation/developers-and-admins/api/management-api.md), along with available operations, tool groups, and MCP tool names. Any objects or features not included in the list are currently not supported.
Use the **Tool groups** and **Tools** columns to select which tools are exposed to your AI agent. See [Limit the available tools](https://docs.kentico.com/documentation/developers-and-admins/api/management-api/configure-management-mcp-server.md#limit-the-available-tools) for details.
> **Info:** **OpenAPI specification**
>
> AI agents can discover the capabilities of the Management API through an [OpenAPI specification](https://swagger.io/specification/v3.1/), available under the _/kentico-api/management/v1/openapi.json_ URL path when your project is running.
>
> Tool groups are the tags of this specification. The specification and the MCP server's `--list-groups` option always describe the groups and tools of the instance you are running.
>
> Each operation in the specification also lists the error codes it can return. The MCP server includes these codes in the description of the corresponding tool.
## Supported capabilities
| Object | Operations | Tool groups | Tools | Notes |
| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------- | ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [Content types](https://docs.kentico.com/documentation/developers-and-admins/development/content-types.md) | Create, Read, Update, Delete | `ContentType` | `list_content_types`, `get_content_type`, `create_content_type`, `update_content_type`, `delete_content_type`, `create_content_type_field`, `update_content_type_field`, `delete_content_type_field`, `assign_content_type_channel`, `unassign_content_type_channel`, `allow_parent_content_type`, `disallow_parent_content_type`, `allow_child_content_type`, `disallow_child_content_type` | Email content types are not currently supported. |
| [Reusable field schemas](https://docs.kentico.com/documentation/developers-and-admins/development/content-types/reusable-field-schemas.md) | Create, Read, Update, Delete | `ReusableSchema` | `list_reusable_schemas`, `get_reusable_schema`, `create_reusable_schema`, `update_reusable_schema`, `delete_reusable_schema`, `create_reusable_schema_field`, `update_reusable_schema_field`, `delete_reusable_schema_field` | |
| [Content items](https://docs.kentico.com/documentation/business-users/content-hub/content-items.md) | Create, Read, Update, Delete, Move, Unpublish | `ContentItem` | `list_content_items`, `get_content_item`, `get_content_item_variant`, `get_content_item_variant_metadata`, `create_content_item`, `create_content_item_variant`, `update_content_item`, `update_content_item_variant`, `delete_content_item_variant`, `move_content_item`, `unpublish_content_item_variant` | Translating a content item means creating its language variant with `create_content_item_variant`. Field values are not copied from other language variants.
Supports [AI content marking](https://docs.kentico.com/documentation/developers-and-admins/api/management-api/use-management-mcp-server.md#ai-content-marking) of text fields. |
| [Pages](https://docs.kentico.com/documentation/business-users/website-content.md) | Create, Read, Update, Delete, Move, Unpublish | `WebPage` | `list_web_pages`, `get_web_page`, `get_web_page_language_variant`, `create_web_page`, `create_web_page_language_variant`, `create_web_page_folder`, `create_web_page_folder_language_variant`, `update_web_page_language_variant`, `update_web_page_tree_node`, `delete_web_page_language_variant`, `move_web_page`, `unpublish_web_page_language_variant`, `get_web_page_allowed_content_types` | [Page preset templates](https://docs.kentico.com/documentation/developers-and-admins/development/builders/page-builder/page-templates-for-page-builder.md) are not supported.
Translating a page means creating its language variant with `create_web_page_language_variant`. Field values and Page Builder content are not copied from other language variants.
Supports [AI content marking](https://docs.kentico.com/documentation/developers-and-admins/api/management-api/use-management-mcp-server.md#ai-content-marking) of text fields. |
| [Content hub folders](https://docs.kentico.com/documentation/business-users/content-hub/content-hub-folders.md) | Create, Read, Update, Delete, Move | `ContentFolder` | `list_content_folders`, `get_content_folder`, `create_content_folder`, `update_content_folder`, `move_content_folder`, `delete_content_folder` | |
| [Assets](https://docs.kentico.com/documentation/business-users/content-hub/content-item-assets.md) | Upload | `Asset` | `upload_asset` | Asset uploads require files to be placed in a configured upload directory before the AI agent can reference them. See [Configure asset uploads](https://docs.kentico.com/documentation/developers-and-admins/api/management-api/configure-management-mcp-server.md#configure-asset-uploads) for details on directory configuration. |
| Channels | Create, Read, Update, Delete | `Channel` | `list_channels`, `get_channel`, `create_channel`, `update_channel`, `delete_channel`, `list_channel_scopes`, `create_channel_scope`, `update_channel_scope`, `delete_channel_scope`, `list_email_senders`, `get_email_sender`, `create_email_sender`, `delete_email_sender` | |
| [Workspaces](https://docs.kentico.com/documentation/developers-and-admins/configuration/users/role-management/workspaces.md) | Create, Read, Update, Delete | `Workspace` | `list_workspaces`, `get_workspace`, `create_workspace`, `update_workspace`, `delete_workspace` | |
| [Languages](https://docs.kentico.com/documentation/developers-and-admins/configuration/languages.md) | Create, Read, Update, Delete | `Language` | `list_languages`, `get_language`, `create_language`, `update_language`, `delete_language` | Manages languages used for live-site content, including their fallback languages. Does not manage the languages of the administration interface, see [Admin UI localization](https://docs.kentico.com/documentation/developers-and-admins/customization/admin-ui-localization.md). |
| [Consents](https://docs.kentico.com/documentation/developers-and-admins/data-protection/consent-management.md) | Create, Read, Update, Delete | `Consent` | `list_consents`, `get_consent`, `create_consent`, `update_consent`, `delete_consent` | Consent agreements are not supported and are only intended to be given or revoked by contacts. Deleting a consent also deletes the agreements recorded for it. |
| [Forms](https://docs.kentico.com/documentation/business-users/digital-marketing/forms.md) | Create, Read, Update, Delete | `Form` | `list_forms`, `get_form`, `create_form`, `update_form`, `delete_form`, `list_form_available_field_types`, `get_form_field_type`, `create_form_field`, `update_form_field`, `delete_form_field` | See [Form management details](#form-management-details) for more information. |
| [Taxonomies and tags](https://docs.kentico.com/documentation/developers-and-admins/configuration/taxonomies.md) | Create, Read, Update, Delete, Move | `Taxonomy`, `Tag` | `list_taxonomies`, `get_taxonomy`, `create_taxonomy`, `update_taxonomy`, `delete_taxonomy`, `list_tags`, `get_tag`, `create_tag`, `update_tag`, `delete_tag`, `move_tag`, `move_tags` | The `Taxonomy` group manages taxonomies, the `Tag` group manages the tags within them. Enable both to work with taxonomies and their tags. |
| [Page Builder](https://docs.kentico.com/documentation/developers-and-admins/development/builders/page-builder.md) components | Create, Read, Update, Delete | `PageBuilder`, `WebPagePageBuilder` | `get_page_builder_configuration`, `get_page_builder_page_template_configuration`, `get_page_builder_available_editable_areas`, `get_page_builder_widget`, `get_page_builder_section`, `get_page_builder_page_template`, `add_page_builder_section`, `remove_page_builder_section`, `add_page_builder_widget`, `remove_page_builder_widget`, `update_page_builder_section_properties`, `update_page_builder_widget_properties`, `update_page_builder_page_template_properties`, `change_page_builder_page_template`, `get_page_builder_components`, `get_page_builder_page_templates` | The `PageBuilder` group provides the components and page templates registered in the project. The `WebPagePageBuilder` group edits the Page Builder configuration of a specific page. Enable both to build pages.
Supports [AI content marking](https://docs.kentico.com/documentation/developers-and-admins/api/management-api/use-management-mcp-server.md#ai-content-marking) of widget properties. |
| [Custom modules](https://docs.kentico.com/documentation/developers-and-admins/customization/object-types.md#define-the-data-class) | Create, Read, Update, Delete | `Module` | `list_modules`, `get_module`, `create_module`, `update_module`, `delete_module` | System (non-custom) modules are read-only, and cannot be updated or deleted. |
| [Module classes](https://docs.kentico.com/documentation/developers-and-admins/customization/object-types.md#define-and-model-the-data-class) and [UI forms](https://docs.kentico.com/documentation/developers-and-admins/customization/object-types.md#define-editing-forms) | Create, Read, Update, Delete | `ModuleClass` | `list_module_classes`, `get_module_class`, `create_module_class`, `update_module_class`, `delete_module_class`, `create_module_class_column`, `update_module_class_column`, `delete_module_class_column`, `list_module_class_ui_forms`, `get_module_class_ui_form`, `create_module_class_ui_form`, `update_module_class_ui_form`, `delete_module_class_ui_form`, `create_module_class_ui_form_field`, `update_module_class_ui_form_field`, `delete_module_class_ui_form_field`, `create_module_class_ui_form_category`, `update_module_class_ui_form_category`, `delete_module_class_ui_form_category` | See [Module class management details](#module-class-management-details) for more information. |
| [Member roles](https://docs.kentico.com/documentation/developers-and-admins/development/registration-and-authentication/member-roles.md) | Read | `MemberRole` | `list_member_roles`, `get_member_role` | Retrieved data currently does not include custom fields added to member roles. |
| [UI form components](https://docs.kentico.com/documentation/developers-and-admins/customization/extend-the-administration-interface/ui-form-components.md) and [data types](https://docs.kentico.com/documentation/developers-and-admins/customization/field-editor/data-types.md) | Read | `FormComponent`, `DataType` | `list_admin_ui_form_components`, `get_admin_ui_form_component`, `list_data_types`, `get_data_type` | The `FormComponent` group provides the admin UI form components used to edit fields of content types, reusable field schemas, and module classes. For the fields of Form Builder forms, see the `Form` group. |
## Form management details
Tools from the `Form` group manage [forms](https://docs.kentico.com/documentation/business-users/digital-marketing/forms.md) and their fields. Compared to the **Forms** application in the administration, the Management MCP server tools have the following limitations:
### Form management
- `create_form` requires a display name. If the code name is not specified, the system derives it from the display name. New forms are created without fields.
- Form code names can only contain alphanumeric characters and underscores (`_`), with a maximum length of 92 characters. This is stricter than the code name validation in the administration. Existing forms with other code names can still be read.
- `update_form` can change the display name, code name, [submit button text](https://docs.kentico.com/documentation/business-users/digital-marketing/forms/create-and-edit-forms.md#set-the-submit-button-text), and the [Overwrite existing contact information with submitted data](https://docs.kentico.com/documentation/business-users/digital-marketing/forms/create-and-edit-forms.md#configure-form-properties-and-behavior) option. The names of the form's class and database table are generated automatically and are read-only.
- Renaming a form also renames the class generated for the form. The database table that stores the form's submissions keeps its original name.
- To display a form on a page, use the `WebPagePageBuilder` and `PageBuilder` tool groups to add and configure the Form widget. The behavior after a visitor submits the form (a message or a redirect) is set in the widget's properties.
### Form layout
- [Form sections](https://docs.kentico.com/documentation/developers-and-admins/development/builders/form-builder/form-sections.md) cannot be added, moved, configured, or removed.
- `create_form_field` adds new fields to the end of the form (the last zone of the last section).
- `update_form_field` can move a field using the `position` property. Positions are counted across all sections of the form in the order the fields are rendered, so a field can be moved into a different section. However, fields cannot be moved into an empty zone. A position at the boundary of two zones always places the field at the start of the next zone, so the last position of any zone other than the last one cannot be reached.
- `get_form` does not return information about sections and zones. Each field only has a position within the whole form.
### Field properties
- You can set the following properties of fields: name, label, required flag, tooltip, explanation text, placeholder, default value, and the properties specific to the field type.
- `get_form` returns all fields of the form, including their validation rules, visibility conditions, and smart field flag. These properties are **read-only**.
- [Field validation](https://docs.kentico.com/documentation/business-users/digital-marketing/forms/create-and-edit-forms.md#field-validation) rules cannot be added, changed, or removed. This applies to both the built-in and [custom validation rules](https://docs.kentico.com/documentation/developers-and-admins/development/builders/form-builder/form-builder-validation-rules.md).
- [Field visibility](https://docs.kentico.com/documentation/business-users/digital-marketing/forms/create-and-edit-forms.md#field-visibility) conditions cannot be set. Fields cannot be hidden, for example, to stop collecting data without deleting the field.
- Fields cannot be configured as [smart fields](https://docs.kentico.com/documentation/business-users/digital-marketing/forms/use-smart-fields-in-forms.md).
- [Contact attribute mapping](https://docs.kentico.com/documentation/business-users/digital-marketing/forms/create-and-edit-forms.md#createandeditforms-contactmapping) is not supported. The mapping is not included in `get_form` and cannot be set. Renaming a field removes the field's existing mapping, same as in the Form Builder.
- A property that the Form Builder hides because of the values of other properties keeps its value and can't be changed. On create, it keeps its default value. On update, it keeps its current value. A call that sends a different value fails. Sending the value the property already holds is allowed, so you can send back the properties you read. Visibility is checked against the values the field will hold after the call. To change a hidden property, also send the values that make it visible. A property that is shown only by another hidden property is also hidden.
- Renaming a field also renames its database column. The submitted values are preserved.
### Field types
- Fields can only use the field types returned by `list_form_available_field_types`. Use `get_form_field_type` to get the schema of the properties specific to a field type.
- The available field types are a subset of the field types offered by the [Form Builder](https://docs.kentico.com/documentation/developers-and-admins/development/builders/form-builder.md):
- [Featured fields](https://docs.kentico.com/documentation/business-users/digital-marketing/forms/create-and-edit-forms.md#add-fields) are not available. You can add a basic field of the same type, but without the preconfigured contact mapping and validation rules of the featured field. The visibility of featured fields cannot be managed.
- [Custom form components](https://docs.kentico.com/documentation/developers-and-admins/development/builders/form-builder/form-components.md) whose [properties](https://docs.kentico.com/documentation/developers-and-admins/development/builders/form-builder/form-components/form-component-properties.md) use legacy Form Builder editing components (the `EditingComponent` attribute) are not available. Only field types whose properties use [admin UI form components](https://docs.kentico.com/documentation/developers-and-admins/customization/extend-the-administration-interface/ui-form-components.md) can be added. Existing fields of such types are still returned by `get_form`.
- Field types excluded from the form by component filters are not available, same as in the Form Builder.
- The type of an existing field cannot be changed. To change the field type, delete the field and add it again.
- If the field type of an existing field is no longer registered in the project, or if the field's validation rules or visibility condition cannot be read, the field can only be deleted.
### Form submissions
- [Form submissions](https://docs.kentico.com/documentation/business-users/digital-marketing/forms/manage-form-submissions.md) are not exposed. The tools cannot read, delete, export, or count the submitted data.
- Deleting a form or field also deletes all submission data stored in the form or field.
### Autoresponders and automation
- [Autoresponders](https://docs.kentico.com/documentation/business-users/digital-marketing/forms/create-and-edit-forms.md#autoresponders) and [automation processes](https://docs.kentico.com/documentation/business-users/digital-marketing/forms/create-and-edit-forms.md#automation-processes) triggered by forms cannot be configured and are not included in `get_form`.
- Management of [form submission notifications](https://docs.kentico.com/documentation/business-users/digital-marketing/forms/create-and-edit-forms.md#form-submission-notifications) is not supported.
### Delete forms and fields
- Ask for approval before calling the delete tools.
- `delete_form` deletes the form, the form's class, and the database table with all submissions.
- `delete_form_field` deletes the field's database column with all submitted values, and removes validation rules and visibility conditions of other fields that depend on the deleted field.
- Unlike the administration, the tools do not ask for confirmation or show where the form is used. `delete_form` also does not refuse to delete forms used in automation processes. Such processes remain in the system and reference a form that no longer exists.
### Generated form classes
The tools only change the form field definition in the database. After creating or changing forms or fields, check if the project contains [generated code files for forms](https://docs.kentico.com/documentation/developers-and-admins/api/generate-code-files-for-system-objects.md). If it does, regenerate them and rebuild the project:
```cmd title="Regenerate form classes"
dotnet run -- --kxp-codegen --type "Forms" --skip-confirmation
```
## Module class management details
The `ModuleClass` tool group manages the [data classes](https://docs.kentico.com/documentation/developers-and-admins/customization/object-types.md#define-and-model-the-data-class) of modules and their [UI forms](https://docs.kentico.com/documentation/developers-and-admins/customization/object-types.md#define-editing-forms).
- Class database columns do not have their own _list_ and _get_ tools. `get_module_class` returns the class together with all of its columns. Similarly, `get_module_class_ui_form` returns the UI form together with all of its fields.
- Classes owned by system modules cannot be created, updated, or deleted. You can still [add custom columns](https://docs.kentico.com/documentation/developers-and-admins/customization/object-types/extend-system-object-types.md) to system classes, create new UI forms, and add fields to the built-in UI forms.
- Management of data records stored in custom classes (i.e., custom object types) is currently not supported.
### UI form categories
- `get_module_class_ui_form` returns the form's `categories`, each with its `name`, `caption`, `tooltip`, `collapsible`, `collapsedByDefault`, and `position` among categories. Each field returns its `categoryName` and its `position` within its group. Fields under a category whose name cannot be read return `categoryName` as `null`.
- A field's group is its category, or the fields placed ahead of the first category when `categoryName` is `null`. The `position` of fields is zero-based and counted within the group on create, update, and read. On forms without categories, this is the same as the position within the whole form.
- Category names must be unique across both the categories and the fields of the form, and cannot match the name of a class column. If `name` is omitted on create, it is derived from the caption.
- Categories are addressed by name. After renaming a category with `update_module_class_ui_form_category`, use the new name in subsequent calls. Renaming also updates the `categoryName` of the category's fields.
- `create_module_class_ui_form_category` appends the category after existing categories unless `position` is set. It does not move any fields into the new category. To move fields, set their `categoryName` with `update_module_class_ui_form_field`. Fields moved without `position` are appended to the category, so move them in display order.
- `create_module_class_ui_form_field` places a field without `categoryName` at the end of the fields ahead of the first category, unless `position` is set.
- `update_module_class_ui_form_field` moves a field to another category through `categoryName`, or ahead of the first category when set to `null`. A field moved to another group without `position` is appended to that group.
- Changing the `position` of a category with `update_module_class_ui_form_category` moves the category together with all of its fields, including system fields.
- `delete_module_class_ui_form_category` keeps the category's fields on the form. They join the preceding category, or the fields ahead of the first category if there is none. Delete the fields separately with `delete_module_class_ui_form_field` to remove them from the form.
- `create_module_class_ui_form` accepts inline `categories` together with `fields`. Fields join an inline category by setting its `name` as their `categoryName`. The order of the arrays determines the layout, so `position` is not accepted for inline categories and fields. Give inline categories an explicit `name` when fields reference them, because names derived from captions are not predictable.