Skip to main content
Glama
zeluizr

Adobe Commerce MCP

by zeluizr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Adobe Commerce MCP

No user-submitted related servers found.

    Related Servers

    • Magento 2 GraphQL

      florinel-chis
      F
      license
      A
      quality
      D
      maintenance
      Provides offline search and retrieval of Magento 2 GraphQL API documentation with 8 specialized tools for finding queries, mutations, types, tutorials, and code examples across 350+ locally indexed markdown files.
      8
      9
      -

    • Magento 2 Development MCP

      elgentos
      A
      license
      B
      quality
      C
      maintenance
      Enables AI agents to interact with Magento 2 development environments through comprehensive tools for module management, database operations, cache control, configuration management, and system diagnostics. Supports complete development workflows from module creation to deployment and troubleshooting.
      28
      27 npm
      41
      MIT

    • Magector

      krejcif
      A
      license
      A
      quality
      A
      maintenance
      Technology-aware MCP server for Magento 2 and Adobe Commerce with intelligent indexing and search, enabling AI assistants to search, navigate, and understand codebases via semantic search and domain-specific pattern detection.
      47
      33 npm
      20
      MIT

    • magento-sql-mcp-server

      jigarkkarangiya
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to interact with a Magento 2 or Adobe Commerce MySQL database through 50+ read-only tools for orders, catalog, customers, CMS, configuration, indexers, and diagnostics, with support for local DDEV, Commerce Cloud, and remote/SSH connections.
      44
      4 npm
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A4.1/5.0

    Scored across 10 tools

    Disambiguation4/5

    Each tool has a distinct role: docs search/read pair, two reference lookups (CLI vs Web API), and five generators targeting different artifacts. The only friction is that explain-config-file covers the same file types (di.xml, events.xml, db_schema.xml) that add-plugin, add-observer and add-db-schema generate, but the 'explain before creating' framing keeps the boundary readable.

    Naming Consistency4/5

    All names are kebab-case verb_noun (explain-config-file, add-plugin, search-docs, lookup-webapi), which is predictable. Minor deviation: generators use three different verbs (add-, scaffold-, explain-) rather than one, so a new artifact type could plausibly be named either add- or scaffold-.

    Tool Count5/5

    Ten tools for a large development domain is well-scoped; every tool maps to a real workflow step (research, lookup, generate). No filler or duplicate tools.

    Completeness4/5

    Core module lifecycle artifacts are covered (module skeleton, plugin, observer, controller/routes, db_schema) plus a solid offline docs and reference layer. Gaps remain for other common generators such as crontab.xml, console commands, system.xml admin config, UI components and GraphQL resolvers, though agents can hand-write these from the bundled docs.

    Maintenance

    ActivityNo data
    ResponsivenessNo issues

    Resources