Spryker Search Tool MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_PERSONAL_ACCESS_TOKEN | Yes | A GitHub Personal Access Token used to search Spryker repositories and code. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_spryker_packagesB | To search the Spryker package repository in Github |
| search_spryker_package_codeB | To search code in Spryker GitHub repositories |
| search_spryker_documentationC | To search in Spryker documentation by query |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool targets a distinct source: packages (repositories), code within repositories, and documentation. No overlap in purpose.
All tools follow a clear 'search_spryker_<noun>' pattern with consistent snake_case and verb placement.
Three tools is well-scoped for a search-focused server, covering the key domains without unnecessary bloat.
The tool surface covers the primary searchable resources in the Spryker ecosystem: packages, code, and documentation. No obvious gaps.