Sitecore Marketer MCP: Available Tools and How to Integrate with Claude Code in VS Code

In my previous blog, I discussed Sitecore MCP and its architecture. In this one, I'll cover the tools available in the Sitecore Marketer MCP and how a developer can integrate the Sitecore Marketer MCP with Visual Studio Code using Claude Code.

Sitecore MCP uses the Sitecore Agentic AI API to interact between AI assistants and Sitecore's marketing tools. This integration allows AI not only to access read-only APIs but also to perform actions such as creating or editing content and managing components, A/B testing, and personalization, all without manual interaction.

By default, all the Marketer MCP tools are enabled, but you can manage them and choose the ones you want to use. Each tool calls an endpoint of the Agent API that the MCP uses to perform actions in Sitecore. These tools carry explicit confirmation and approval gates, and they maintain proper logging and security.

Available tools in Sitecore Marketer MCP

Here is the full set of Sitecore MCP Connector tools (56 in total as of date), grouped by function.

Sites & Pages

list_sites — List all sites with name and target hostname
get_site_information — Get site information by site ID
get_site_id_from_item — Get the site ID from an item ID
get_all_pages_by_site — Get all pages for a site
search_site — Search site pages by title
create_page — Create a new page
get_page — Get page details by ID and language
get_page_template_by_id — Get a page template, including available fields
get_page_html — Get a page's HTML content
get_page_path_by_live_url — Resolve a page path from a live URL
get_page_preview_url — Get the preview URL for a page
get_page_screenshot — Get a screenshot of a page
get_all_languages — Get all available languages in the system
add_language_to_page — Add a language version to a page

Components (on pages)

list_components — List all components for a site
get_component — Get component details, including datasource requirements
get_components_on_page — Get all components on a page
add_component_on_page — Add a component to a page
get_allowed_comps_by_ph — Get allowed components by placeholder
list_avail_insertopts — List available insert options for an item

Datasources

create_component_ds — Create a component datasource
set_component_datasource — Set the datasource for a component on a page
search_component_ds — Search component datasources

Content Items

create_content_item — Create a content item
get_content_item_by_id — Get a content item by ID
get_content_item_by_path — Get a content item by path
update_content — Update a content item
update_fields_on_item — Update fields on a content item
delete_content — Delete a content item

Assets

search_assets — Search assets by name, type, or tags
get_asset_information — Get asset information by ID
update_asset — Update asset information

A/B Testing

create_component_ab_test — Create an A/B test for a component (requires user confirmation)
update_ab_test — Update an existing A/B test
set_component_variant — Configure a variant component for an A/B test (requires user confirmation)
reset_component_variant — Reset a component's variant to its default state
get_flow_definition — Get the definition of an A/B test or personalization flow
get_flow_variant_by_id — Get a specific variant and its variant components
list_page_flows — List all flows (A/B tests and personalizations) on a page

Personalization

create_perso_version — Create a personalization version (single-condition audience)
create_perso_version_multi — Create a personalization version (multi-condition audience)
update_perso_version — Update a personalization version's info and audience
get_perso_ver_by_page — Get all personalization versions for a page
hide_component_perso_default_page — Hide a component on the default personalization variant
get_perso_cond_tmpls — Get available personalization condition templates
get_perso_cond_tmpl_by_id — Get a personalization condition template by ID

Brand Kits & Briefs

list_brandkits — List summaries of all available Brand Kits
get_brandkit_by_id — Get the full content of a single Brand Kit
list_briefs — List all Briefs (with optional filtering)
get_brief_by_id — Get a single Brief by ID
list_brief_types — List all Brief Types available for generation
get_brief_type_by_id — Get a single Brief Type by ID
generate_brief_draft — Generate a brief draft (requires user confirmation)
create_brief_from_draft — Create a brief from a draft (requires draft generation first)
generate_brief_revision — Regenerate a brief using a selected Brand Kit and Brief Type
update_brief_from_revision — Apply a revision to a brief (requires user approval)

How to integrate Sitecore Marketer MCP with Claude Code

Prerequisites

Visual Studio Code with the Claude Code extension enabled.
Access to the Sitecore Marketer MCP server (https://marketer.sitecorecloud.io/mcp/marketer-mcp-prod).
Ensure your organization's Claude Code has the necessary permissions enabled.

Step-by-step instructions

Step 1. Open Claude's connector settings and add a new custom connector, using the Marketer MCP server URL: https://marketer.sitecorecloud.io/mcp/marketer-mcp-prod

Step 2. Click Add. The Marketer MCP now appears under your list of connectors.

Step 3. Click Connect to launch the authorization page in your browser.

Step 4. In the Marketer MCP server authorization request dialog, click Allow Access.

Step 5. Select the organization and tenant you want to use when interacting with the MCP server.

Step 6. When prompted, click Open Claude to complete the setup. You are now connected to the Marketer MCP server in Claude.

Step 7. Verify the connection. To verify the connection, enter a simple prompt such as: List all available sites. If the connection is successful, the server returns a list of sites for your tenant. You can do this from Claude Desktop or from Claude Code Extention in VS Code.

Json format output

{
"sites": [
{
"id": "423db736-1d95-4154-9cbb-**********",
"name": "corporate-website",
"targetHostname": "",
"rootPath": "6c2e9283-f87a-4db6-a63e-**********"
}
]
}

How to use

Launch the Claude Code extension and use a prompt like Create an item with the name [Item Name] based on the template [Template Name] at the path [Path]. It will automatically call the create_content_item tool and create the content, generating the corresponding JSON payload for the Agent API.

{
"itemId": "36b29e9d-b7e3-47c3-83c2-********",
"name": "LoanStatsSection",
"path": "/sitecore/layout/Renderings/Project/<SiteCollection>/<Site>/LoanStatsSection",
"templateId": "04646a89-996f-4ee7-878a-********",
"version": 1
}

You can also use a prompt such as Add the component [Component Name] inside the placeholder [Placeholder Name] on the page [Page Name]. This triggers the add_component_on_page tool, which generates the appropriate JSON payload for the request.

{
"componentItemName": "Stats Component",
"componentRenderingId": "04646a89-996f-4ee7-878a-********",
"fields": {},
"language": "en",
"pageId": "36b29e9d-b7e3-47c3-83c2-********",
"placeholderPath": "headless-main"
}

Conclusion

The Sitecore Marketer MCP turns everyday marketing and content tasks into simple, natural-language prompts, and its 56 tools cover the full lifecycle, from sites and pages to components, datasources, content items, assets, A/B testing, personalization, and briefs. Because each tool maps to an Agent API endpoint and runs behind confirmation gates, logging, and existing Sitecore permissions, you get the speed of automation without giving up control. Integrating it with Claude Code in Visual Studio Code brings all of this directly into your development workflow, so you can create and manage Sitecore content from the same place you write your code. Set it up once, start with a few read-only prompts to build confidence, and gradually work your way up to the tools that make changes.