Experimental Module: This module is experimental and not stable. There is no backward compatibility promise.
Connect your Spryker application to AI assistants through the Model Context Protocol (MCP).
composer require spryker-sdk/ai-dev --dev
docker/sdk console transfer:generateRegister the console commands in your ConsoleDependencyProvider. The class_exists() guards keep the project bootable on environments where the dev dependency is absent (e.g. production):
use SprykerSdk\Zed\AiDev\Communication\Console\AiToolSetupConsole;
use SprykerSdk\Zed\AiDev\Communication\Console\McpServerConsole;
protected function getConsoleCommands(Container $container): array
{
if (class_exists(McpServerConsole::class)) {
$commands[] = new McpServerConsole();
}
if (class_exists(AiToolSetupConsole::class)) {
$commands[] = new AiToolSetupConsole();
}
}The previously documented
GenerateAgentsFileConsole,GenerateSkillsConsole, andGeneratePromptsConsolecommands are outdated. Their functionality is delivered through the Claude plugin (see below) andai-dev:setup— do not wire them.
Connect to AI assistants:
Claude Code
claude mcp add spryker-project -- $(pwd)/docker/sdk console ai-dev:mcp-server -qClaude Desktop - Add to claude_desktop_config.json:
{
"mcpServers": {
"spryker-ai-dev": {
"command": "/path/to/your/project/docker/sdk",
"args": ["console", "ai-dev:mcp-server", "-q"]
}
}
}This repository also ships a Claude Code plugin — spryker-ai-dev-sdk — that bundles Spryker-aware skills (e.g. propel-schema, data-import, code-review, cypress-e2e-test, codecept-functional, static-validation, yves-atomic-frontend, ai-dev-setup) and a spryker-code-reviewer agent. Source layout:
.claude-plugin/marketplace.json— marketplace manifest (spryker-plugins-official).plugins/spryker-ai-dev-sdk/.claude-plugin/plugin.json— plugin manifest.plugins/spryker-ai-dev-sdk/skills/<name>/SKILL.md— individual skills.plugins/spryker-ai-dev-sdk/agents/*.md— bundled subagents.
Inside Claude Code:
/plugin marketplace add spryker-sdk/ai-dev
/plugin install spryker-ai-dev-sdk@spryker-plugins-official
After install, restart the Claude Code session for the new skills and agents to appear. Verify with /plugin (Claude Code lists installed plugins) and by invoking a user-facing skill such as /ai-dev-setup.
Useful while developing skills or agents in this repo without publishing first.
-
Launch Claude Code with the plugin loaded directly from this checkout:
claude --plugin-dir /absolute/path/to/vendor/spryker-sdk/ai-dev/plugins/spryker-ai-dev-sdk
The path must point at the plugin directory (the one containing
.claude-plugin/plugin.json), not at the repository root. -
Verify the plugin is loaded with
/pluginand by invoking a user-facing skill such as/ai-dev-setup. -
After editing a
SKILL.mdor an agent definition, restart the session — skill frontmatter is parsed at load time and is not hot-reloaded.
Reference: Discover plugins — Claude Code docs.
Prompts are auto-generated from the Spryker Prompt Library on first run. To regenerate:
docker/sdk console ai-dev:generate-promptsFor detailed setup, configuration, and extension points:
Use MCP Inspector to test your MCP server:
npx @modelcontextprotocol/inspector docker/sdk console ai-dev:mcp-server -qWe welcome contributions to improve this experimental module.
- Fork the repository
- Create a feature branch
- Make your changes following Spryker coding standards
- Submit a pull request with a clear description of your changes
Please report issues through the GitHub issue tracker with:
- Clear description of the problem
- Steps to reproduce
- Expected vs actual behavior
- Environment details (PHP version, Spryker version, etc.)
Prerequisites
- Docker SDK
^1.71.0 - PHP
^8.3
Setup for Development
composer install
vendor/bin/phpstan analyze
vendor/bin/phpcs --standard=phpcs.xmlThis module is released under the Spryker Evaluation License Agreement. See LICENSE file for details.