A
licenseC
qualityD
maintenanceA SitecoreMCP version that can be used in enterprises
100
385 npm
Apache 2.0
sitecore-personalize-mcp
Related Servers
Alternatives to sitecore-personalize-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides AI agents with direct read/write access to Sitecore CMS through 100+ tools across Item Service, GraphQL, and PowerShell APIs.385 npmApache 2.0
- AlicenseNot gradedqualityAmaintenanceMCP server for Sitecore that provides tools to interact with Sitecore via GraphQL, Item Service API, and Sitecore PowerShell Extensions, enabling content and security management.385 npm53Apache 2.0
- AlicenseBqualityDmaintenanceMCP server for Salesforce Interaction Studio that enables listing and managing datasets, campaigns, segments, and performance stats via natural language.2210 npmMIT
- FlicenseNot gradedqualityCmaintenanceA Model Context Protocol server that exposes personal data tools for Spotify listening history, movie ratings, and GitHub repos, enabling natural language queries from MCP clients.1-
- FlicenseNot gradedqualityCmaintenanceAn MCP server that puts your Genesys Cloud org under AI control, enabling natural language creation of queues, skills, users, wrap-up codes, and Architect IVR flows with Mermaid diagrams.-
TDQS
A3.7/5.0
Scored across 17 tools
Disambiguation3/5
The core resources (flow, audience, guest, dataset, event) are clearly separated, but flow and experience overlap heavily: experience_list/get are documented as exact equivalents of flow_list/get with a subtype pre-applied. This duplication is explained, but an agent could reasonably select either path for the same operation.
Naming Consistency5/5
All tools follow a consistent sitecore_personalize_<resource>_<action> snake_case convention, such as flow_list, audience_get, guest_upsert, and event_send. The action verbs are predictable and there are no mixed casing or naming styles.
Tool Count4/5
17 tools is at the upper edge but reasonable for a server spanning flows, experiences, audiences, guests, datasets, and events. The experience_list/get convenience duplicates add slight bloat, but most tools map to a distinct domain operation.
Completeness3/5
The guest lifecycle is well covered with get, upsert, delete, search, and data extension handling, and flows support listing, retrieving, status changes, and execution. However, audiences have create and read but no update/delete, flows cannot be created or updated beyond status, and datasets are read-only, leaving notable lifecycle gaps.
Maintenance
ActivitySlowing
ResponsivenessNo issues