MCP Server: Sylius Admin API
Claude Code plugin with an MCP server for Sylius 2.2: manage products, variants, categories, SEO, countries, zones and shipping methods. Separate servers for stage and prod, product wizard as a skill.
Sylius Admin: Claude Code Plugin with MCP Server
This documentation always describes the latest published version.
Overview
claude-plugin-syliusadmin is a Claude Code plugin. It ships an MCP server (Model Context Protocol) through which Claude manages the catalog of a Sylius 2.2 shop and the related shop configuration: products, variants and prices, categories, attributes, options, images, content and SEO, countries, zones, shipping methods and tax categories. It also includes a skill that guides you through creating a product. The plugin is the successor of claude-mcp-shopwareadmin; Shopware is no longer used in the underlying shop.
Claude handles catalog maintenance directly in the shop, without copy-paste and without switching to the browser. Each server structurally serves only one environment (stage or prod), and a fixed allowlist keeps it restricted to the catalog and shop configuration.
Deliberately not included are orders, customers, promotions and admin user management. "Shipping" means the shipping configuration, not dispatching individual orders.
graph LR
A["Claude Code"] --> B["syliusadmin-stage-mcp"]
A --> C["syliusadmin-prod-mcp"]
A --> D["Skills: setup, sylius-produkt-wizard"]
B --> E["Sylius stage Admin API"]
C --> F["Sylius prod Admin API"]
Documentation
| Page | Content |
|---|---|
| Installation | Install the plugin, setup skill, manual installation, uninstall |
| Configuration | Environment variables, .env for stage and prod, admin user, stage key, image upload |
| Tool Reference | All 55 tools with parameters and rules |
| Usage | Product wizard, example requests, working with stage and prod |
| Security and Privacy | Credentials, allowlist, delete protection, upload restriction, data flows |
| Troubleshooting | Common problems, solutions and FAQ |
| Technical Details | Plugin layout, request flow, directory structure, dependencies |
Features
| Feature | Description |
|---|---|
| Catalog | Create and change products, variants, categories (taxons), attributes and options, including channel prices |
| Content and SEO | Name, slug, description, meta fields and SEO fields via the translations field; Claude writes the texts in the conversation |
| Images | Upload local files or register CDN images by URL, for products and categories |
| Shop configuration | Countries, zones, shipping methods, shipping categories and tax categories |
| Plugin data | Marketplace links (create, change, delete) and input field definitions (read-only) |
| Product wizard | Skill /syliusadmin:sylius-produkt-wizard with a guided dialog for simple and configurable products |
| Stage/prod separation | Two servers with their own .env, no environment parameter per tool call |
| Safeguards | Path allowlist, no deleting except marketplace links, activation guard, restricted file upload |
| Protocol | MCP compliant, stdio transport |
Requirements
| Requirement | Version | Notes |
|---|---|---|
| Claude Code | current | with plugin support |
| Python | 3.12 or newer | for the venv and the server |
| Sylius | 2.2 | Admin API (/api/v2/admin/) reachable |
| Sylius admin user | dedicated user | with role ROLE_API_ACCESS, see Configuration |
| Optional shop plugins | - | sylius-seo-suite-pro, sylius-cdn-product-images, sylius-marketplace-redirect, sylius-product-custom-inputs for the respective features |
Granular admin roles exist only in Sylius Plus. In the Community Edition every admin user is technically a full admin. The restriction to the catalog is enforced by the server itself through a path allowlist, not by Sylius.
License
MIT License - Markus Michalski
Support
Repository: github.com/markus-michalski/claude-plugin-syliusadmin
Issues: GitHub Issues