Interactive setup wizard for the AEP MCP Server. Guides new users through gathering Adobe credentials, discovering sandbox names, identity namespace IDs, and merge policy IDs, then writes a ready-to-use orgs.json profile entry. Run this first after cloning the repo.
Specialized agent for CSV data profiling, quality scoring, and ERD generation (Stage 0 of AEP pipeline). Reads all CSV files in a target directory, profiles every field, scores data quality across 6 dimensions, and generates Mermaid Entity-Relationship Diagrams. Uses Python standard library only — no open-source…
Specialized agent for data ingestion into AEP — transforms CSV data to XDM-mapped JSON, uploads via Batch Ingestion API, and monitors batch completion. Handles Stage 6 of the AEP automation pipeline. Loads aep-fundamentals skill for API patterns.
Specialized agent for post-ingestion data validation — queries ingested data from AEP datasets, compares against source CSV records, verifies record counts, checks identity resolution, and produces a validation report. Handles Stage 7 (the final stage) of the AEP automation pipeline. Loads aep-fundamentals skill for…
Specialized agent for creating AEP datasets from deployed schemas (Stage 3 of AEP pipeline). Creates datasets via Catalog API, verifies schema references, and updates deployment manifest. Loads aep-fundamentals skill for API patterns.
Generates a complete Go-live readiness package — Pre-cutover checklist, Go-live checklist, and Post go-live checklist — with team roster (name, email, phone), editable assigned-to and due date, automatic overdue detection, clickable priority management, point of contact per item, and escalation contacts. Conducts a…
Inspects deployed AEP schemas after dataset creation (Stage 4), identifies candidate identity fields, and presents the user with options to select which identities to configure for each schema. NEVER auto-applies identities — always requires explicit user selection.
Specialized agent for designing AJO journey flows end-to-end. Conducts an interactive discovery session to gather use case context, inclusion/exclusion criteria, consent requirements, personalization fields, and channels. Produces a journey design JSON, a step-by-step AJO UI implementation guide, and an HTML flow…
Universal entry point for all development tasks. Classifies tasks into SDLC categories, loads category-specific workflows, gathers context from designs and stories, runs parallel codebase exploration and research, then produces structured implementation contracts before any code is written.
Specialized agent for Stage 5 — enabling Real-Time Customer Profile on AEP schemas and datasets after explicit user approval. NEVER auto-enables Profile. Always asks user which schemas/datasets to enable.
Activation QA agent — validates AJO activation workflow (segments, campaigns, journeys). Handles test case generation (/qa read activation) and execution (/qa run activation) for SEG-, CAM-, and JRN- prefixed tests. Tests segment definitions, campaign configuration, and journey orchestration. Dispatches to…
Platform QA agent — validates the complete AEP platform layer: data model (namespaces, schemas, datasets, identity descriptors, profile enablement) and data ingestion pipeline (Data Prep mappings, batch/streaming ingestion). Handles test case generation (/qa read) and execution (/qa run) for NS-, SCH-, DST-, IDN-…
Specialized agent for XDM schema lifecycle — designs schemas from data analysis results (Stage 1), deploys schemas to AEP Schema Registry (Stage 2), and validates schema composition. Loads xdm-schema-design and aep-fundamentals skills for deep domain knowledge.
Specialized agent for AEP audience segment design and creation. Generates segment design JSON with name, description, business definition, required profile/event attributes, consent requirements, PQL logic, and AEP API creation payload. Creates segments via Adobe MCP (mcpstageadobe-marketing-agent-mcp-widget) and…
★not rated 2 1mo agoA69 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: