Model Context Protocol server for Spryker Package Search
Model Context Protocol server for Spryker Package Search. The package search mcp mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 3 defined tools rather than through you.
A command-line tool that initializes a Model Context Protocol (MCP) server to provide spryker search capabilities for Spryker GitHub repositories.
Everything the assistant can do here goes through one of these:
search_spryker_packages — Searches for Spryker packages based on a natural language querysearch_spryker_package_code — Parameters: - query (string, required): The natural language query to search within codesearch_spryker_documentation — Parameters: - query (string, required): The natural language query to search Spryker documentation@modelcontextprotocol/inspector on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
You will need 2 environment variables: GITHUB_PERSONAL_ACCESS_TOKEN, FULL_PATH. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
This sits in the knowledge and memory group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Package Search MCP's toolset — search_spryker_packages, search_spryker_package_code, search_spryker_documentation — is a fair guide to whether it matches your workflow. It is maintained by spryker-community; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| search_spryker_packages | Searches for Spryker packages based on a natural language query. |
| search_spryker_package_code | Parameters: - query (string, required): The natural language query to search within code. |
| search_spryker_documentation | Parameters: - query (string, required): The natural language query to search Spryker documentation. |
{
"mcpServers": {
"sprykerPackageSearch": {
"command": "npx",
"args": [
"-y",
"/FULL_PATH/spryker-module-finder"
],
"env": {
"GITHUB_PERSONAL_ACCESS_TOKEN":"token"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| GITHUB_PERSONAL_ACCESS_TOKEN | Credential the server authenticates with. | Yes |
| FULL_PATH | Filesystem location the server is allowed to use. | Optional |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.