Spryker is spread across five GitHub organisations and a separate documentation site, which is why finding the module that does a thing takes so long. Asking in plain language and getting the package, the PHP that implements it and the docs page is the shortcut.
A stdio MCP server that searches Spryker's GitHub organisations and public documentation from natural-language queries. Package search, code-level search inside the repositories and a docs.spryker.com search all answer into the same conversation, filterable by organisation.
- Spryker packages found on GitHub from a natural-language query (search_spryker_packages)
- PHP code searched inside Spryker repositories (search_spryker_package_code)
- The public documentation at docs.spryker.com searched from the same place (search_spryker_documentation)
- Filtering by organisation: spryker, spryker-eco, spryker-sdk, spryker-shop and spryker-community
- One server per project, so several Spryker projects can be configured side by side
Npm and npx plus a clone of the repository, and a GitHub personal access token in the server's env — the package and code searches run against the GitHub API.
One command plus a key — npx -y /FULL_PATH/spryker-module-finder, then supply credentials