search_spryker_packagesLABSCO SUMMARY
Spryker source and docs answered in one place.
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.
What it is
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.
What you get
- 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
Requirements
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.
Setup effort
Build from source — git clone https://github.com/spryker-community/package-search-mcp.git
USE CASES
01
Finding the module that does the thing
A natural-language query returns matching Spryker packages, so you name the behaviour rather than guessing at a module name.
02
Reading how it is actually implemented
Code-level search runs inside the Spryker repositories, so the answer is the PHP itself rather than a description of it.
03
Checking the documented behaviour
The same question can be put to docs.spryker.com, which is what settles whether something is intended or incidental.
04
Keeping the search inside one part of the ecosystem
Pass the organisations you care about — spryker-eco or spryker-shop, for instance — and results from the rest stay out of the way.
3 tools
Listed in project docs. Your client may show a different list.
search_spryker_package_codesearch_spryker_documentationBEFORE YOU INSTALL
What to know first
Tools you get
3 tools named in the project's documentation.
Requires
- npm and npx
- A clone of the repository
- GITHUB_PERSONAL_ACCESS_TOKEN in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
git clone https://github.com/spryker-community/package-search-mcp.git
cd package-search-mcp && npm installMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"sprykerPackageSearch": {
"command": "npx",
"args": [
"-y",
"<YOUR_FULL_PATH>/package-search-mcp"
],
"env": {
"GITHUB_PERSONAL_ACCESS_TOKEN": "<YOUR_GITHUB_PERSONAL_ACCESS_TOKEN>"
}
}
}
}<YOUR_FULL_PATH> is the absolute path of the folder you cloned into, so the argument points at your package-search-mcp checkout, and <YOUR_GITHUB_PERSONAL_ACCESS_TOKEN> is a GitHub personal access token.
