Marketer MCP tool reference and other information
This topic provides detailed information about the tools available in the Sitecore Marketer MCP server and how they are used to perform actions in SitecoreAI. It also includes supporting resources to help you understand capabilities, troubleshoot issues, and find answers to common questions.
Use this section to explore available tools, review additional guidance, and resolve issues when working with the Marketer MCP server.
Tool reference
All tools in the Sitecore Marketer MCP server are enabled by default. We recommend keeping them enabled to ensure full functionality. Each tool corresponds to an endpoint in the Agent API, which the server uses to perform actions in SitecoreAI.
The following tables list the available tools, grouped by use case:
Site management
| Tool | Description |
|---|---|
list_sites | Retrieves a list of available sites with their basic information including name, display name, and URL. |
get_site_information | Retrieves the details of a specific site by its ID. |
get_site_id_from_item | Retrieves the site ID associated with a specific item ID. |
get_all_pages_by_site | Retrieves a list of pages for a specific site, including each page's ID and path. |
get_all_languages | Retrieves all languages available in the system. |
Page management
| Tool | Description |
|---|---|
create_page | Creates a new page using the specified template under the parent page. |
add_language_to_page | Adds a new language version for an existing page. |
add_component_on_page | Adds a component to a specific placeholder on a page. |
get_components_on_page | Retrieves components on a page. Provide a variantId to retrieve the components for a specific personalization or A/B/n test variant. To find available variant IDs, use list_page_flows.If variantId is not provided, the tool returns components for the page. |
set_component_datasource | Sets or clears the datasource for a component on a page. Provide variantId to update the datasource for the specific personalization or A/B/n test variant. To find available variant IDs, use list_page_flows.If variantId is not provided, the change applies to the page. |
search_site | Searches for all pages in a specific site using a search term that matches page titles and content. |
get_page_path_by_live_url | Retrieves the page item path that corresponds to a live URL on a website. |
get_page_screenshot | Retrieves a base64-encoded screenshot of a page. Provide variantId to retrieve a screenshot for a specific personalization or A/B/n test variant. To find available variant IDs, use list_page_flows.If variantId is not provided, the screenshot shows the page. |
get_page_html | Retrieves the HTML content of a page. Provide variantId to retrieve the HTML content of a specific personalization or A/B/n test variant. To find available variant IDs, use list_page_flows.If variantId is not provided, the tool returns HTML content of the page. |
get_page_preview_url | Retrieves a URL for previewing a page. Provide variantId to retrieve the preview URL of a specific personalization or A/B/n test variant. To find available variant IDs, use list_page_flows.If variantId is not provided, the tool returns the preview URL of the page. |
get_page_template_by_id | Retrieves the details of a specific page template, including its fields and settings. |
get_page | Retrieves the details about a page by its ID and language code. |
get_allowed_comps_by_ph | Retrieves the components that can be added to a placeholder on a page. Provide variantId to retrieve the allowed components for a specific personalization or A/B/n test variant. To find available variant IDs, use list_page_flows.If variantId is not provided, the tool returns the allowed components for the page. |
Content management
| Tool | Description |
|---|---|
create_content_item | Creates a new content item using the specified template and field values. |
update_content | Updates an existing content item, including its fields and language. |
delete_content | Deletes a content item and optionally all of its child items. Warning The language query parameter is not currently in use. The entire content item is deleted regardless of its value. |
get_content_item_by_path | Retrieves the details of a content item by specifying its path in the content tree. |
get_content_item_by_id | Retrieves the details of a specific content item by specifying its ID. |
list_avail_insertopts | Retrieves a list of content templates that can be inserted as child items under the specified parent item. |
update_fields_on_item | Updates the fields on a content item. |
Component management
| Tool | Description |
|---|---|
list_components | Retrieves a list of components available for a specific site. |
get_component | Retrieves the details of a specific component, including its ID, name, and datasource options. |
create_component_ds | Creates a new datasource item for a specific component using the provided data field values. |
search_component_ds | Searches for available datasources that can be used with a specific component. |
Asset management
| Tool | Description |
|---|---|
search_assets | Searches for digital assets such as videos, images, and documents using query terms, file types, or tags. |
get_asset_information | Retrieves the details of a specific digital asset by specifying its ID. |
update_asset | Updates the metadata and properties of an existing digital asset, such as alt text, description, and tags. |
Personalization
Personalization must be enabled for the SitecoreAI tenant before using these tools. See how to manage personalization for a site using analytics identifiers.
| Tool | Description |
|---|---|
get_perso_ver_by_page | Retrieves all personalization variants defined for a specific page. |
create_perso_version | Creates a new personalization variant of a page for a specific audience using a condition. |
create_perso_version_multi | Creates a new personalization variant of a page for a specific audience using one or multiple conditions. |
get_perso_cond_tmpls | Retrieves all available condition templates for personalization. |
get_perso_cond_tmpl_by_id | Retrieves a condition template by ID including its parameters for creating a personalization variant on a page. |
update_perso_version | Updates the audience name, variant name, and targeting rules of a personalization variant. |
hide_component_perso_default_page | Hides a component on the default page variant. Personalization must already exist on the page before you use this tool. A default page variant exists only after page variants have been created to personalize a page. |
Brand kits
| Tool | Description |
|---|---|
list_brandkits | Retrieves all available brand kits, including their names, IDs, brands, companies, and status. |
get_brandkit_by_id | Retrieves the full details of a brand kit by ID, including its sections and associated fields (subsections). |
Briefs
These tools are typically used as part of a conversational brief creation flow driven by the LLM, but they can also be used individually if needed.
| Tool | Description |
|---|---|
list_brief_types | Retrieves all available brief types, including their names, labels, and IDs. |
list_briefs | Retrieves all available briefs, with optional sorting and filtering by status, creator, and brief type. |
generate_brief_draft | Generates a new brief draft for review based on the selected brand kit and brief type. The draft is not saved until create_brief_from_draft is used. |
create_brief_from_draft | Creates and saves a new brief from a previously generated brief draft. |
generate_brief_revision | Generates a revised brief draft for review based on updated instructions. The existing brief is not changed until update_brief_from_revision is used. |
update_brief_from_revision | Updates and saves an existing brief from a generated brief revision. |
get_brief_type_by_id | Retrieves the details of a brief type by ID, including its field definitions and audit metadata. |
get_brief_by_id | Retrieves a specific brief by its ID, including its fields, type reference, and audit metadata. |
Experiments
Personalization must be enabled for the SitecoreAI tenant before using these tools. See how to manage personalization for a site using analytics identifiers.
| Tool | Description |
|---|---|
create_component_ab_test | Creates a new A/B/n test for a page component using site, page, component details, variants, and goals. |
update_ab_test | Update an existing A/B/n test by modifying variants, targeting rules, or settings. |
Flow definitions
| Tool | Description |
|---|---|
list_page_flows | Retrieves all flow definitions for a page, including A/B/n tests and personalizations, with structure, variants, and configurations. |
set_component_variant | Sets up a variant for a specific A/B/n test or personalization by copying, hiding, or swapping the original component. |
reset_component_variant | Removes any applied personalization or A/B/n test variant set up, such as copy, hide, or swap, from a component and restores it to its original state. Provide a variantId to reset the specific personalization or A/B/n test variant. To find available variant IDs, use list_page_flows.For personalization only, if variantId is not provided, the component on the default page variant is reset. |
get_flow_definition | Retrieves a flow definition, either A/B/n test or personalization, with structure, variants, and configuration. |
get_flow_variant_by_id | Retrieves the details of a specific A/B/n test or personalization variant, including datasource and components. |
Example prompts
The Sitecore Marketer MCP server enables you to perform common marketing and content tasks using natural language prompts.
The Marketer MCP server is only reliable for the supported use cases listed here. Responses outside this scope have not been validated by Sitecore and might be inaccurate.
The following examples demonstrate how to interact with the server across different use cases.
Site management
- List all available sites in my tenant.
- Get information about the Habitat site.
- Show all or specific pages for the Habitat site.
Page management
- Search for pages containing a specific term like Spring Sale in the title.
- Create a landing page in the Habitat site.
- Add a French language version to the homepage.
- Get the HTML content for the Contact us page.
Content management
- Create a new blog post about AI trends under the technology section.
- Update the hero text on the homepage to Welcome to Innovation.
- List all available templates I can use for new content.
Component management
- Add a hero component to the homepage main placeholder.
- List all components available for the Habitat site.
- Show me components I can add to the sidebar placeholder.
Asset management
- Update alt text for all images tagged with hero.
- Find assets related to the spring campaign.
- Get details for the brand logo asset.
Personalization
- Create a personalization version for returning customers on the homepage.
- List all personalization versions for the product page.
- Update the audience of the Returning Visitor Variant to track visits over 10 times
Brand kits
- List all brand kits available in the organization.
- Retrieve the Powerful brand kit.
Briefs
- List all available brief types.
- Generate a brief for a new product launch campaign for Easter.
- Get a summary of the objective of the June Marketing Brief - 15 EUR Budget.
Experiments
- Create an A/B test for the Banner component on the home page.
- Change the goal of the A/B/n test added to the Banner component.
- Add a new test variant for the Banner component on the home page.
Flow definitions
- List all available A/B/n tests on the home page.
- Get information about the personalization flow on the home page.
- Configure Variant B of the A/B test to swap the original component with a signup banner.
Other technical information
This section describes how the Sitecore Marketer MCP server enforces security, and operates from a technical perspective.
Technical specifications
The following table outlines key technical details of the Marketer MCP server:
| Trait | Description |
|---|---|
| Protocol | Uses JSON-RPC 2.0 based API format. |
| Hosting | Hosted on Cloudflare Workers for edge performance and scalability. |
| API format | OpenAPI REST endpoints with JSON responses. |
| Monitoring | Observability and audit trails for performance tracking. |
Security and compliance
The Marketer MCP server enforces security and compliance controls to ensure safe and auditable operations:
- Tenant-aware operations with automatic isolation.
- Short-lived tokens with secure refresh.
- Role-based access that follows existing Sitecore permissions.
- Audit logging for every operation and data access.
- Rate limiting to protect system stability (50 requests per 10 seconds).
Capabilities and limitations
The Marketer MCP server extends Sitecore APIs with automation while maintaining strict access and security boundaries:
- Tenant handling - automatically detects tenant context.
- Token management - manages authentication tokens for secure sessions.
- Smart orchestration - combines multiple API calls into simplified actions.
- Data consistency - validates and standardizes data.
- Access boundaries - restricted to the user’s tenant; no cross-tenant or elevated access.
- Security controls - enforces Sitecore’s existing role-based permissions.
- Audit and compliance - tracks all operations for transparency and traceability.
Troubleshooting
This section helps you identify and resolve common issues when using the Marketer MCP server.
Access and permissions issues
If you can’t sign in, see the tools you expect, or get an Access denied message:
- Make sure you’re signed in with the correct organization and tenant.
- If prompted to sign in repeatedly, your session may have expired so you'll have to sign in again.
- Verify that your user role includes access to the required tools or actions
- If the issue persists, contact your administrator to review your permissions.
Resource parameter is required error
If you encounter a Resource parameter is required error during OAuth authentication:
-
The authorization URL may be missing the required
resourcequery parameter. -
Append the following parameter to the authorization URL:
-
Open the updated URL in a new browser window to continue authentication.
Tools not appearing
If you can’t see the expected Marketer MCP tools or integrations after connecting:
- Confirm you are signed in to the correct tenant.
- Verify with your administrator that your role includes access to the tools.
- Refresh the connection or restart your MCP client.
Connection or timeout errors
If the Marketer MCP server is slow to respond or fails to connect:
- Wait a few seconds and try again (rate limits may apply: 50 requests per 10 seconds).
- Check your internet connection and VPN status.
- Ensure the MCP endpoint URL is allowed by your firewall or proxy.
When to contact support
If the issue persists, collect relevant details (error message, tenant, and action performed) and create a support case.
FAQs
This section answers the most frequently asked questions about the Marketer MCP.
Do I need a Sitecore account to use the Marketer MCP server?
Yes. You need valid Sitecore credentials with the right permissions for your organization and tenant. The server respects existing access controls and user roles.
What is required to get started?
You need access to a Sitecore environment with the Marketer MCP server enabled, valid credentials, and an MCP-compatible AI client such as Claude or Cursor.
How does the server work with the Agent API?
The server connects to the Agent API to perform actions in Sitecore. When an AI agent receives a prompt, it converts it into structured requests that the Agent API executes.
Who can use the Marketer MCP server?
Marketers, content authors, developers, partners, and AI systems that connect to Sitecore through supported MCP clients.
Do I need technical skills to use the server?
No. The server lets marketers manage pages, content, and personalization through natural-language commands instead of code or API calls.
Can I still use the Sitecore interface?
Yes. The server adds another way to work in Sitecore but does not replace the traditional interface. You can switch between both at any time.
Is the Marketer MCP server secure?
Yes. It uses OAuth 2.0 authentication through Sitecore Identity, with tenant isolation, short-lived tokens, and audit logging for all actions.
Does the Marketer MCP server store or expose my data or credentials?
No. The server acts as a secure bridge between your AI tool and the Agent API. It does not permanently store your content, prompts, or passwords, and AI clients never see your credentials or use your data for model training.
Can any user perform any action?
No. Users can only perform actions permitted by their Sitecore roles and permissions.
What if the AI makes a mistake or applies the wrong change?
Always review important updates before publishing. The server operates within your permissions, so existing approval and review steps still apply.