adobe-admin-console-mcp
Related Servers
Alternatives to adobe-admin-console-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceThe first full-featured MCP server for Adobe Experience Platform: 29 tools across schemas, datasets, profiles, segments, query service, and GDPR/CCPA privacy operations. Extends Adobe's read-only beta with production-grade write operations.176 npmApache 2.0
- FlicenseNot gradedqualityCmaintenanceEnables management of system users through a simple sample API, exposed as MCP tools for natural-language interaction.-

clue2app-user-mcpofficial
AlicenseAqualityCmaintenanceExposes user, membership, and role administration tools via MCP, acting as a thin passthrough to a coordinator API with RBAC enforced by the coordinator using caller bearer tokens.8Academic Free v1.1- FlicenseNot gradedqualityDmaintenanceEnables Adobe Experience Platform and AEM content operations through a shared tool registry, exposing health checks, fragment search, sandbox management, dataset queries, and content fragment fetching via MCP and web interfaces.-
- FlicenseNot gradedqualityDmaintenanceEnables querying and managing an employee directory through MCP tools and resources, including listing, searching, adding, updating, and deleting employees.-
- FlicenseCqualityCmaintenanceEnables managing Polizei (Polisafe) Admin/RBAC API resources such as users, roles, permissions, scopes/tenants, invitations, OAuth clients, and profiles through MCP tools.551-
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: listing users, getting user details, listing product profiles, assigning licenses, and removing licenses. There is no overlap or ambiguity in their intended functions.
All tool names follow a consistent 'adobe_' prefix with a verb_noun pattern: list_users, get_user, list_product_profiles, assign_license, remove_license. The naming is uniform and predictable.
With 5 tools, the server is well-scoped for its purpose of managing Adobe admin console users and licenses. Each tool serves a necessary function, and the count is within the ideal 3-15 range.
The tool set covers the core license management lifecycle: read users, read profiles, assign and revoke licenses. Minor gaps exist such as no user creation or deletion, but these may be outside the server's intended scope, so the coverage is nearly complete.