The work is public.
Magendoo builds its commerce tooling in the open: an MCP server for Magento 2, a set of production Magento modules, PrestaShop compliance modules, and AI development skills — all public on GitHub under github.com/magendooro.
Proof over promises.
Anyone can claim engineering standards. Repositories show them. Our code is public because reading it answers the questions a sales page cannot: how we structure modules, how we test, how we handle edge cases, whether we finish what we start.
If you are evaluating Magendoo, start here. The repos are the portfolio.
Start with MageMCP.
60 typed commerce tools — 18 storefront via GraphQL, 42 admin via REST — backed by 895 automated tests. Integration tests run against a real Magento instance. MIT licensed, written in Python.
What does Magendoo maintain?
25 public repositories. Three groups that matter.
MCP server connecting AI agents to Magento 2 and Adobe Commerce. 60 typed commerce tools — 18 storefront via GraphQL, 42 admin via REST — backed by 895 automated tests.
Claude Code skills for Magento 2 and Adobe Commerce, covering REST and GraphQL workflows. Drop-in agent capabilities for Magento development.
Performance review command for n98-magerun2. Scans a Magento 2 installation and reports what slows it down. The org's most-starred active Magento repo.
Catalog data-quality observability: completeness scoring and filter-blind detection. Finds the product data gaps that make listings invisible — to shoppers and to AI agents.
FAQ and product questions with GEO optimisation — structured Q&A markup built for answer engines, not just search engines.
EU Omnibus Directive (2019/2161) price tracker. Records and displays prior prices for compliant discount display.
EU Base Price display (Grundpreis / PAngV). Per-unit pricing for German and EU market compliance.
EU withdrawal function for Magento 2 (Directive 2023/2673). Online cancellation as the law requires it.
Abandoned cart capture, tracking, and management for Magento 2.
Entity-backed product labels, manual and rule-computed.
Shipping restrictions by zip code and carrier.
Product change webhooks for Magento 2 — push catalog events to external systems.
Store health and insights: digest emails and health alerts for merchants.
Declarative schema support for MySQL ENUM and SET columns.
EU Article 11a withdrawal function for PrestaShop 9.
WinMentor ERP stock sync for PrestaShop 8 and 9.
The org goes back to 2013. Magento 1 tooling — including magento-fulltext-reindex, at 31★ still the most-starred repo, public since 2014 — remains online as history, not as current work. magento-fulltext-reindex
The standards are in the code.
The same rules apply to a free module and a client engagement. MageMCP ships with 895 automated tests across unit and integration suites — integration tests run against a real Magento instance. Modules use declarative schema, typed interfaces, and semantic versioning, with tests, static analysis and coding-standard checks published per module. Nothing is published that we would not deploy.
EU compliance modules — Omnibus, base price, withdrawal — track the directives they implement by number. When the law changes, the module changes.
All of it is built with the same agentic engineering workflow we establish for clients. The repositories are what that workflow produces.
How open source relates to working with us.
The tools are free. The engineering around them is the engagement. An assessment tells you which of these tools your store needs and what custom work remains; an embedded engineer integrates them into your stack and builds what does not exist yet.
Every engagement leaves you with code you own — and where it generalizes, it ends up back in these repositories.
Frequently asked questions
Read the code first.
Twenty-five public repositories. Eleven updated this year. Start with MageMCP.