Skip to main content
Glama
stubbedev

Adobe Experience Assets Dev MCP

by stubbedev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Adobe Experience Assets Dev MCP

No user-submitted related servers found.

    Related Servers

    • AEM Assets MCP Server

      SatoshiInoue
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables interaction with Adobe Experience Manager (AEM) Assets through the Author API. It allows users to browse folders, search for assets, retrieve detailed asset information, and perform bulk metadata updates using natural language.
      1
      -

    • AEM MCP Server

      udaykumarbpatel
      A
      license
      Not graded
      quality
      D
      maintenance
      A comprehensive Model Context Protocol server for Adobe Experience Manager that provides 35+ REST/JSON-RPC API methods for complete content, component, asset, and template management. Enables AI-powered AEM automation through natural language interfaces with support for page operations, component CRUD, asset management, and publishing workflows.
      MIT

    • Frame.io V4 MCP

      yong6330
      F
      license
      A
      quality
      B
      maintenance
      Enables discovering and invoking all 97 published Frame.io V4 API operations through a searchable catalog, covering accounts, projects, folders, files, comments, shares, metadata, webhooks, and more using OAuth credentials. It also performs complete local multipart uploads, including chunked PUTs and upload status checks.
      5
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 17 tools

    Disambiguation5/5

    Each tool has a distinct purpose: the seven explain tools cover different topics (auth, error handling, etc.), context tools are clearly get/set/reset, presets have get (singular) and list (plural), and planning, validation, category, and search are all unique. No two tools appear to do the same thing.

    Naming Consistency4/5

    Most tools use a consistent snake_case verb_noun pattern with an 'aem_' prefix (e.g., aem_explain_auth, aem_set_context). However, three tools (list_categories, load_category, search_aem_assets_api) lack the 'aem_' prefix, creating a minor inconsistency.

    Tool Count4/5

    At 17 tools, the count is slightly above the ideal range of 3-15 but still reasonable for a server covering explanations, planning, context, presets, categories, and search. It feels appropriately scoped for its purpose.

    Completeness2/5

    The server is heavily focused on explanatory, planning, and meta-tools (context, presets, categories) but lacks any actionable tools to perform actual AEM Assets operations (e.g., list assets, upload, delete). This leaves agents unable to execute tasks, representing a significant gap.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources