Adobe Experience Assets Dev MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_categoriesA | List available AEM Assets integration categories and whether each is currently loaded. |
| aem_set_contextB | Set session-level AEM integration defaults to improve routing and request blueprint accuracy across tools. |
| aem_get_contextA | Get current session-level AEM integration defaults. |
| aem_reset_contextA | Reset session-level AEM integration defaults to safe baseline values. |
| load_categoryB | Load one tool category. Categories: uploads, folders, assets, metadata, search, renditions. Call this immediately once user intent is clear. |
| search_aem_assets_apiA | Hybrid search for AEM Assets operations with intent weighting, synonym expansion, and optional semantic reranking. |
| aem_list_operation_presetsA | List strict AEM integration presets that reduce implementation guesswork: bulk_migration, nightly_delta_sync, cms_publish_sync. |
| aem_get_operation_presetA | Return a strict, opinionated implementation preset with ordered steps, mapped MCP tools, safeguards, and anti-patterns. |
| aem_validate_integration_planB | Preflight validator for AEM integration plans. Checks required steps, safeguards, policy controls, unknown steps, and coverage against strict presets. |
| aem_explain_authA | Explain authentication and headers commonly required for AEM Assets API integrations. |
| aem_explain_paginationA | Explain practical pagination for Query Builder APIs, including p.limit/p.offset loops and p.guessTotal usage. |
| aem_explain_hierarchy_data_accessA | Explain fast data retrieval strategies for deeply nested DAM folder hierarchies, and when to use Query Builder versus folder traversal. |
| aem_plan_efficient_upload_metadata_syncC | Return an efficiency-first staged plan for upload + metadata pipelines, with concurrency and retry guidance. |
| aem_explain_upload_flowA | Explain the direct binary upload flow for AEM Assets Cloud Service with integration sequencing. |
| aem_explain_metadata_syncB | Explain robust metadata synchronization strategy for AEM Assets integrations. |
| aem_explain_error_handlingA | Explain common AEM Assets integration errors and practical retry/mitigation guidance. |
| aem_explain_implementation_playbookA | Provide an end-to-end implementation playbook for AEM integrations (search, upload, metadata sync, renditions, and resiliency). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/stubbedev/adobe-experience-dev-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server