Skip to main content
Glama
Sign In
deenesjakoruzh
Spryker Package Search Tool

Spryker Package Search Tool

by vitaliiivanovspryker
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Spryker Package Search Tool

A command-line tool that initializes a Model Context Protocol (MCP) server to provide package search capabilities for Spryker GitHub repositories.

This tool allows you to search Spryker packages or their code contents using natural language queries. It supports filtering by specific GitHub organizations.

✨ Features

  • Search for Spryker packages on GitHub

  • Code-level search across Spryker repositories

  • Support for filtering by organization (spryker, spryker-eco, spryker-sdk, spryker-shop)

  • Runs as an MCP server using stdio transport

Example with Claude Example with Claude for docs

Related MCP server: Spryker Search Tool MCP Server

🚀 Installation

Ensure npm and npx are installed.

git clone
cd spryker-module-finder && npm install

MCP server makes the tool compatible with various AI agents to extend context with Spryker Project context

Tools:

Settings

You can add as many servers as projects, just by configuring them properly using the project name.

{
  "mcpServers": {
      "sprykerPackageSearch": {
          "command": "npx",
          "args": [
              "-y",
              "/FULL_PATH/spryker-module-finder"
          ],
          "env": {
              "GITHUB_PERSONAL_ACCESS_TOKEN":"token"
          }
      }
  }
}

Debug

npx @modelcontextprotocol/inspector npx node src/index.js

Test

npm test
npx eslint . --fix

🧠 Available Tools

search_spryker_packages

Searches for Spryker packages based on a natural language query.

Parameters:

  • query (string, required): The natural language query to search GitHub repositories.

  • organisations (array of strings, optional): List of GitHub orgs to filter by. Example: ["spryker", "spryker-eco", "spryker-sdk", "spryker-shop"]

search_spryker_package_code

Searches for PHP code inside Spryker GitHub repositories.

Parameters:

  • query (string, required): The natural language query to search within code.

  • organisations (array of strings, optional): List of GitHub orgs to filter by. Example: ["spryker", "spryker-eco", "spryker-sdk", "spryker-shop"]

search_spryker_documentation_path

Searches for Spryker documentation links.

Parameters:

  • query (string, required): The natural language query to search Spryker documentation links.

🧩 Architecture

Built with Model Context Protocol SDK

Uses StdioServerTransport for communication

Validates input with zod

Handles GitHub API integration for repository and code search

📄 License

MIT

👥 Authors

Available Tools

3 tools
search_spryker_documentation_pathC

To search Spryker documentation path urls by query

Inputs: query (required).

search_spryker_package_codeB

To search code in Spryker GitHub repositories

Inputs: query (required), organisations.

search_spryker_packagesB

To search the Spryker package repository in Github

Inputs: query (required), organisations.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    B3.2/5.0

    Scored across 3 tools

    Disambiguation4/5

    The three tools have distinct primary targets: documentation paths, package code, and package repository search. However, 'search_spryker_package_code' and 'search_spryker_packages' could be slightly confusing as both involve GitHub repositories, though their descriptions clarify one searches code within repositories and the other searches the package repository itself.

    Naming Consistency5/5

    All tool names follow a consistent snake_case pattern with the verb 'search' followed by a specific noun phrase (spryker_documentation_path, spryker_package_code, spryker_packages). This uniformity makes the tool set predictable and easy to understand.

    Tool Count3/5

    With only 3 tools, the server feels thin for a 'Package Search Tool' that might imply broader functionality like installing or managing packages. While the tools cover key search aspects, the limited count may restrict agent workflows, especially if additional operations like package installation or version checking are needed.

    Completeness3/5

    The tools provide search capabilities across documentation, code, and packages, which aligns with the server's name. However, there are notable gaps: no tools for actions like installing packages, checking package versions, or managing dependencies, which are common in package management contexts. This limits the server to read-only search operations.

    Resources

    Related MCP Connectors

    Related MCP Servers

    • GitHub Chat MCP

      AsyncFuncAI
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that enables analyzing and querying GitHub repositories through the GitHub Chat API, allowing users to index repositories and ask questions about their code, architecture and tech stack.
      2
      90
      MIT

    • code-rag

      kkuppula
      F
      license
      Not graded
      quality
      C
      maintenance
      A semantic code search MCP server that enables natural language queries against your codebase, supporting features like related file discovery and context expansion, all running locally.
      2
      -

    • Magector

      krejcif
      A
      license
      A
      quality
      B
      maintenance
      Technology-aware MCP server for Magento 2 and Adobe Commerce with intelligent indexing and search, enabling AI assistants to search, navigate, and understand codebases via semantic search and domain-specific pattern detection.
      47
      64 npm
      20
      MIT