WPZylos MCP Server
OfficialSupports WooCommerce extension development with tools for scaffolding payment gateways, shipping methods, emails, widgets, product tabs, and REST API extensions, along with a hook knowledge base.
Provides tools for WordPress plugin development, including scaffolding, code generation, validation, and analysis.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@WPZylos MCP Server scaffold a new plugin"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
WPZylos MCP Server
Intelligent framework-aware context layer for AI-powered WordPress plugin development with WPZylos + WooCommerce support.
55 tools · 12 resources · 9 prompts · 48-hook WooCommerce knowledge base
Quick Start
npm install && npm run build{
"mcpServers": {
"wpzylos": {
"command": "node",
"args": ["D:/laragon/www/wpzylos/wpzylos-mcp/dist/index.js"],
"env": { "WPZYLOS_FRAMEWORK_ROOT": "D:/laragon/www/wpzylos" }
}
}
}Related MCP server: Code-MCP
Tools (55)
Discovery & Inspection (8)
Tool | Description |
| Point MCP at a plugin project |
| List all framework packages |
| Deep-dive into any package |
| Task-based package recommendation |
| Analyze any PHP file |
| Search classes/methods across all packages |
| List code generation templates |
| Read a stub template |
Code Generation (18)
Tool | Generates |
| Any of 42 stubs |
| ServiceProvider |
| Model |
| Middleware |
| REST Controller |
| Event |
| Listener |
| CLI Command |
| Custom Post Type |
| Custom Taxonomy |
| Shortcode |
| Settings Page |
| Admin Menu |
| Background Job |
| Validation Rule |
| Service |
| Database Migration |
| PHPUnit Test |
Validation & Analysis (8)
Tool | Checks |
| Folder structure compliance |
| Nonces, capabilities, escaping, SQL |
| Hook prefixing |
| PSR-4 namespace verification |
| WordPress plugin header fields |
| Raw WP functions |
| TODO/FIXME, empty methods |
| Coding pattern detection |
Scaffolding (5)
Tool | Generates |
| Complete new plugin |
| Model + Migration + Controller + Provider + Routes |
| CPT + Taxonomy + MetaBox + Columns + Provider |
| Controller + Middleware + Routes + Provider |
| Settings + Menu + View + Provider |
Inspection & Refactoring (8)
Tool | Purpose |
| Full plugin inventory |
| Hook → callback mapping |
| Class dependency analysis |
| ServiceProvider inventory |
| Text search in plugin |
| Code quality suggestions |
| 7-phase boot flow |
| Flat API reference |
WooCommerce Development (8)
Tool | Purpose |
| Search 48-hook WC knowledge base |
| WC_Payment_Gateway + process_payment + refund |
| WC_Shipping_Method + calculate_shipping |
| WC_Email + trigger + templates |
| WP_Widget + form/update/widget |
| Admin or frontend product tab |
| HPOS, dependency check, deprecations |
| WC REST API v3 controller |
Resources (12)
URI | Description |
| Framework architecture |
| Framework rules |
| 7-phase boot flow |
| Package deps |
| All packages |
| Plugin folder structure |
| Stub templates |
| Security checklist |
| Testing conventions |
| Documentation index |
| WC hook reference |
| WC development guide |
Prompts (9)
Prompt | Workflow |
| New plugin from scratch |
| Framework compliance audit |
| Add feature to existing plugin |
| Add Custom Post Type |
| Add REST API endpoints |
| Add admin settings page |
| Debug hook issues |
| Convert traditional plugin |
| Build WooCommerce extension |
Architecture
src/
├── core/ (types, cache, config)
├── engine/ (file-analyzer, package-registry, docs-indexer, stub-registry)
├── tools/
│ ├── generation-tools.ts (16 generators)
│ ├── validation-tools.ts (6 validators)
│ ├── scaffolding-tools.ts (6 scaffolders)
│ ├── advanced-tools.ts (11 advanced tools)
│ └── woocommerce-tools.ts (8 WooCommerce dev tools)
└── index.ts (server + 8 core tools + 12 resources + 9 prompts)License
MIT
Available Tools
83 toolsbuild_from_blueprintA
Generate an ENTIRE WPZylos plugin from a comprehensive blueprint specification. Produces all files: entry, bootstrap, PluginContext, models, controllers, migrations, routes, providers, views, and config. The ultimate one-shot generation tool.
Inputs: name (required), slug (required), namespace (required), prefix (required), +9 more.
detect_framework_violationsA
Detect code that uses raw WordPress functions instead of framework abstractions. Finds add_action, register_post_type, wp_enqueue_script, etc. that should use WPZylos packages.
Inputs: path (required).
detect_incomplete_implementationsA
Find TODO, FIXME, HACK, XXX comments, empty method bodies, and placeholder returns across plugin code.
Inputs: path (required).
explain_boot_sequenceA
Explain the WPZylos framework boot sequence and how a plugin initializes. Returns the 8-phase boot flow with code examples.
Inputs: no named parameters.
generate_commandB
Generate a CLI Command class for WP-CLI or Symfony Console.
Inputs: rootNamespace (required), className (required), extraTokens.
generate_controllerB
Generate a REST/HTTP Controller class for handling requests.
Inputs: rootNamespace (required), className (required), extraTokens.
generate_eventB
Generate an Event class for the event dispatcher system.
Inputs: rootNamespace (required), className (required), extraTokens.
generate_from_stubA
Generate a PHP class from any framework stub template. Reads the stub, applies token replacements, and returns the generated code. Covers all 42 stub types: provider, model, controller, middleware, migration, event, listener, subscriber, posttype, taxonomy, shortcode, widget, metabox, menu, settings, rest, ajax, cron, command, cast, enum, exception, factory, filter, action, interface, job, mail, notification, observer, policy, render, resource, rule, scope, seeder, service, test, trait, block, columns.
Inputs: stub (required), namespace (required), className (required), extraTokens.
generate_jobC
Generate a background Job class for queued processing.
Inputs: rootNamespace (required), className (required), extraTokens.
generate_listenerC
Generate a Listener class that handles dispatched events.
Inputs: rootNamespace (required), className (required), extraTokens.
generate_middlewareC
Generate a Middleware class implementing MiddlewareInterface for the HTTP pipeline.
Inputs: rootNamespace (required), className (required), extraTokens.
generate_migrationC
Generate a database migration file with proper column definitions. Specify table name and fields with types, and get a complete migration class.
Inputs: rootNamespace (required), tableName (required), fields (required), action.
generate_modelA
Generate an Eloquent-style Model class with fillable, casts, and table name.
Inputs: rootNamespace (required), className (required), extraTokens.
generate_posttypeB
Generate a Custom Post Type registration class.
Inputs: rootNamespace (required), className (required), extraTokens.
generate_providerB
Generate a ServiceProvider class. Providers register services in the container and boot hook integrations.
Inputs: rootNamespace (required), className (required), extraTokens.
generate_ruleB
Generate a custom Validation Rule class implementing RuleInterface.
Inputs: rootNamespace (required), className (required), extraTokens.
generate_serviceC
Generate a Service class for business logic.
Inputs: rootNamespace (required), className (required), extraTokens.
generate_settingsC
Generate a Settings Page class with sections and fields.
Inputs: rootNamespace (required), className (required), extraTokens.
generate_shortcodeB
Generate a Shortcode class with render method.
Inputs: rootNamespace (required), className (required), extraTokens.
generate_taxonomyC
Generate a Custom Taxonomy registration class.
Inputs: rootNamespace (required), className (required), extraTokens.
generate_testA
Generate a PHPUnit test file for an existing class. Creates test methods for each public method in the target class.
Inputs: filePath (required), rootNamespace (required), testType.
get_stub_contentA
Get the raw content of a specific stub template. Use to understand the template structure before generating code.
Inputs: name (required).
gutenberg_scaffold_blockA
Generate a complete Gutenberg block: block.json, edit.js, save.js, index.js, editor.scss, style.scss and PHP registration. For server-side rendered blocks, use gutenberg_scaffold_dynamic_block instead.
Inputs: rootNamespace (required), blockName (required), blockTitle (required), textDomain (required), +4 more.
gutenberg_scaffold_block_patternA
Generate a WordPress block pattern registration. Block patterns are pre-designed block layouts users can insert.
Inputs: rootNamespace (required), patternName (required), patternTitle (required), textDomain (required), +2 more.
gutenberg_scaffold_block_styleA
Register custom block style variations for existing core or custom blocks (e.g., rounded image, shadowed card).
Inputs: rootNamespace (required), targetBlock (required), styleName (required), styleLabel (required), +2 more.
gutenberg_scaffold_dynamic_blockA
Generate a dynamic (server-side rendered) Gutenberg block. The block uses a PHP render callback instead of save.js — ideal for blocks that show live data (recent posts, queries, etc.).
Inputs: rootNamespace (required), blockName (required), blockTitle (required), textDomain (required), +2 more.
gutenberg_scaffold_sidebar_pluginA
Generate a Gutenberg editor sidebar plugin (PluginSidebar). Adds a custom panel in the block editor for plugin-specific settings, meta fields, or controls.
Inputs: rootNamespace (required), pluginName (required), pluginTitle (required), textDomain (required), +1 more.
gutenberg_validate_blockA
Validate a Gutenberg block: check block.json schema, required files (edit.js/save.js or render.php), attribute definitions, and text domain usage.
Inputs: path (required).
i18n_scaffold_potB
Generate a translation setup: .pot file header, load_textdomain registration, and wp_set_script_translations for JS. Provides the complete i18n setup for a WPZylos plugin.
Inputs: rootNamespace (required), textDomain (required), pluginSlug (required).
i18n_validateB
Scan plugin for internationalization issues: untranslated user-facing strings, missing text domains, incorrect __() usage, mixed text domains, and translation function best practices.
Inputs: path (required), textDomain (required).
inspect_conventionsA
Detect coding conventions used in a plugin: naming style, docblock style, type hint usage, directory structure patterns. Use before generating code to match existing style.
Inputs: path (required).
inspect_dependency_graphA
Analyze class-to-class dependencies within a plugin. Shows use/import statements, constructor injection, and method type hints to map which classes depend on which.
Inputs: path (required).
inspect_fileB
Analyze a PHP file and extract its classes, methods with full signatures, properties, constants, imports, and docblocks. Use before modifying any file.
Inputs: filePath (required).
inspect_hook_mapA
Map ALL hooks registered by a WPZylos plugin. Returns every add_action, add_filter, wpAction, wpFilter, action, filter call with callback, file, and line. Critical for debugging hook issues.
Inputs: path (required).
inspect_packageA
Deep-dive into a specific WPZylos framework package. Returns every class, interface, trait with full method signatures, properties, constants, and docblocks. Use before using a package.
Inputs: name (required), refresh.
inspect_project_summaryB
Get a comprehensive summary of a WPZylos plugin project: providers, routes, models, services, controllers, and framework usage.
Inputs: path (required).
inspect_providersA
List all ServiceProviders in a plugin with their register() and boot() methods, bindings, and hook registrations. Shows which providers are registered in config/services.php.
Inputs: path (required).
list_all_methodsA
List every public method across all WPZylos framework packages in a flat, searchable format. Returns class, method, parameters, and return type. Use as a quick API reference.
Inputs: package, filter.
list_packagesA
List all WPZylos framework packages with their descriptions, layers, and class counts. Use to understand what the framework offers.
Inputs: refresh.
list_stubsB
List all available code generation stub templates. Shows stub names and their replaceable tokens.
Inputs: refresh.
multisite_scaffold_network_adminB
Generate a WordPress Multisite network admin page: menu registration, capability checks, settings form, and ServiceProvider. For plugins that need network-wide settings.
Inputs: rootNamespace (required), pageName (required), pageSlug (required), pageTitle (required), +1 more.
multisite_scaffold_site_optionA
Generate a network-wide site option manager: getter, setter, default values, per-site override support, and ServiceProvider. Uses get_site_option/update_site_option with per-site fallback.
Inputs: rootNamespace (required), className (required), optionKey (required), options (required).
multisite_validateB
Validate a plugin's Multisite compatibility: network activation support, correct option functions, super_admin checks, network_admin_menu registration, and plugin_action_links filtering.
Inputs: path (required).
recommend_packageA
Given a task description, recommend the best WPZylos framework package(s) to use. Prevents reinventing logic.
Inputs: task (required).
scaffold_admin_noticeA
Generate a WordPress admin notice: dismissible, persistent (user meta), conditional (screen/capability), with proper escaping and styling.
Inputs: rootNamespace (required), noticeName (required), noticeType (required), message (required), +4 more.
scaffold_ajax_handlerC
Generate a WordPress AJAX handler with nonce verification, capability check, PHP handler class, JS caller, and ServiceProvider registration.
Inputs: rootNamespace (required), actionName (required), textDomain (required), requireLogin, +1 more.
scaffold_cpt_moduleA
Generate a complete Custom Post Type module: CPT registration class, Taxonomy (optional), MetaBox (optional), Admin Columns (optional), and ServiceProvider.
Inputs: rootNamespace (required), postTypeName (required), slug (required), withTaxonomy, +4 more.
scaffold_cron_jobB
Generate a WordPress Cron job: scheduled event, custom interval, handler class, activation/deactivation hooks for schedule management.
Inputs: rootNamespace (required), jobName (required), interval (required), textDomain (required), +1 more.
scaffold_crud_moduleB
Generate a complete CRUD module: Model, Migration, Controller, ServiceProvider, and route registration. Returns all files needed for a database-backed resource.
Inputs: rootNamespace (required), resourceName (required), tableName (required), fields (required).
scaffold_customizerB
Generate WordPress Customizer panel, section, and controls with sanitization, live preview JS, and ServiceProvider.
Inputs: rootNamespace (required), panelName (required), panelId (required), textDomain (required), +1 more.
scaffold_custom_tableB
Generate a custom database table with dbDelta() migration, CRUD model class using $wpdb, activation hook, and uninstall cleanup.
Inputs: rootNamespace (required), tableName (required), columns (required), textDomain (required).
scaffold_dashboard_widgetB
Generate a WordPress admin Dashboard Widget with configurable content, AJAX refresh, and optional configuration form.
Inputs: rootNamespace (required), widgetId (required), widgetTitle (required), textDomain (required), +2 more.
scaffold_meta_boxA
Generate a WordPress meta box: registration, render callback, save handler with nonce/capability checks, and field definitions.
Inputs: rootNamespace (required), metaBoxId (required), title (required), postTypes (required), +3 more.
scaffold_pluginB
Generate a complete new WPZylos plugin with all required files: entry file, bootstrap, PluginContext, Activator, Deactivator, Uninstaller, composer.json, config files, and directory structure. Based on the wpzylos-scaffold template.
Inputs: name (required), slug (required), namespace (required), prefix (required), +6 more.
scaffold_rest_moduleB
Generate a REST API module: Controller, Middleware, FormRequest, route file, and provider. Includes authentication and validation scaffolding.
Inputs: rootNamespace (required), resourceName (required), endpoints (required), withAuth.
scaffold_settings_pageB
Generate a complete admin settings page module: Settings class, Menu registration, ServiceProvider, and view template.
Inputs: rootNamespace (required), pageName (required), menuTitle (required), sections (required).
scaffold_shortcode_uiB
Generate an enhanced WordPress shortcode with admin UI (TinyMCE button), attribute panel, and frontend rendering class.
Inputs: rootNamespace (required), shortcodeName (required), textDomain (required), attributes (required), +1 more.
scaffold_test_suiteB
Generate a PHPUnit test suite for a WPZylos plugin: bootstrap file, base test case, sample unit test, phpunit.xml configuration.
Inputs: rootNamespace (required), pluginSlug (required), testType, targetClass.
scaffold_transient_cacheA
Generate a Transient caching helper class with get, set, remember, forget, flush pattern, and group-based invalidation.
Inputs: rootNamespace (required), prefix (required), className, defaultTtl.
scaffold_update_checkerB
Generate a self-hosted plugin update checker: checks a remote JSON endpoint for new versions, integrates with WordPress plugin update API.
Inputs: rootNamespace (required), pluginSlug (required), updateUrl (required), textDomain (required).
scaffold_wp_cli_commandB
Generate a WP-CLI command class with arguments, synopsis, progress bar support, and ServiceProvider registration.
Inputs: rootNamespace (required), commandName (required), textDomain (required), description (required), +2 more.
search_frameworkA
Search across all framework packages for classes or methods by name. Returns matching classes with their package, FQCN, and method signatures.
Inputs: query (required), type.
search_in_projectA
Search for text patterns, class names, function calls, or any string across all files in the targeted plugin project. Returns matching lines with file, line number, and context.
Inputs: path (required), query (required), extensions, maxResults.
set_project_targetA
Set the target WordPress plugin project path. Validates it is a WPZylos plugin and caches the target. Must be called before using project-specific tools.
Inputs: path (required).
suggest_refactoringA
Analyze a PHP file and suggest refactoring opportunities: extract methods, reduce complexity, improve framework usage, split large classes.
Inputs: filePath (required).
validate_composer_autoloadA
Verify PSR-4 autoload mappings in composer.json match actual file/directory structure. Detects mismatched namespaces, missing directories, and files in wrong locations.
Inputs: path (required).
validate_hook_usageA
Validate correct hook usage: wpAction/wpFilter for WordPress core hooks (never prefixed), action/filter for custom hooks (always prefixed). Detects raw add_action/add_filter that should use HookManager.
Inputs: path (required).
validate_plugin_headerA
Validate the WordPress plugin file header. Checks for required fields (Plugin Name, Version, Description, License) and recommended fields (Text Domain, Requires PHP, Requires at least).
Inputs: path (required).
validate_plugin_structureB
Validate a WPZylos plugin folder structure against framework conventions. Checks for required files, directories, namespace consistency, and config setup.
Inputs: path (required).
validate_rest_schemaA
Validate WordPress REST API endpoints in a plugin: check route registration, permission callbacks, sanitize/validate callbacks, response schema, and namespace consistency.
Inputs: path (required), namespace.
validate_security_complianceB
Scan plugin PHP files for security violations: missing nonce verification, missing capability checks, unescaped output, raw SQL without prepare(). Based on WPZylos RULES.md security requirements.
Inputs: path (required).
woo_scaffold_block_integrationA
Generate a standalone WooCommerce Blocks IntegrationInterface class. Use when you need the PHP integration layer without scaffolding the full checkout/cart block extension.
Inputs: rootNamespace (required), integrationName (required), integrationSlug (required), textDomain (required), +1 more.
woo_scaffold_cart_block_extensionB
Generate a WooCommerce Cart Block extension component for adding custom content to the block-based cart (e.g., upsells, notices, custom fees).
Inputs: rootNamespace (required), extensionName (required), extensionSlug (required), textDomain (required), +1 more.
woo_scaffold_checkout_blockA
Generate a WooCommerce Checkout Block extension: React component for checkout, IntegrationInterface PHP class, and block.json. For extending the block-based checkout with custom fields or UI.
Inputs: rootNamespace (required), extensionName (required), extensionSlug (required), textDomain (required), +1 more.
woo_scaffold_emailB
Generate a custom WooCommerce Email class with trigger(), get_content_html(), get_content_plain(), and ServiceProvider.
Inputs: rootNamespace (required), className (required), emailId (required), title (required), +1 more.
woo_scaffold_payment_gatewayB
Generate a WooCommerce Payment Gateway class, ServiceProvider, and registration hook. Includes all required methods: init_form_fields(), process_payment(), admin panel setup.
Inputs: rootNamespace (required), gatewayName (required), gatewayId (required), title (required), +1 more.
woo_scaffold_product_tabB
Generate a custom WooCommerce product data tab (admin) with fields and save logic, or a frontend product page tab.
Inputs: rootNamespace (required), tabName (required), tabId (required), tabLabel (required), +2 more.
woo_scaffold_rest_extensionB
Generate a WooCommerce REST API extension controller that adds custom endpoints under the WC REST API namespace.
Inputs: rootNamespace (required), resourceName (required), restBase (required), endpoints.
woo_scaffold_shipping_methodB
Generate a WooCommerce Shipping Method class with calculate_shipping(), init_form_fields(), and ServiceProvider registration.
Inputs: rootNamespace (required), className (required), methodId (required), title (required).
woo_scaffold_widgetB
Generate a WooCommerce/WordPress Widget class with form(), update(), and widget() methods.
Inputs: rootNamespace (required), className (required), widgetId (required), title (required).
woo_search_hooksA
Search the WooCommerce hook knowledge base. Find actions and filters by name, category, or keyword. Categories: cart, checkout, orders, products, payment, shipping, email, admin, rest-api, lifecycle.
Inputs: query, category, type.
woo_validate_integrationB
Validate a plugin's WooCommerce integration: HPOS compatibility declaration, feature compatibility, proper hook usage, WC dependency check, template override safety.
Inputs: path (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 83 tools
Most tools have distinct purposes as described, but the high number (83) and similar verb prefixes like 'scaffold_' and 'generate_' create potential for confusion. However, descriptions clearly differentiate each tool's target (e.g., plugin vs module vs block).
The naming follows a consistent verb_noun pattern in snake_case, but the variety of prefixes (gutenberg_, multisite_, woo_, i18n_) introduces subdomain-specific conventions that deviate from a single uniform style.
83 tools is on the high side, but given the broad scope of the WPZylos framework—covering generation, inspection, validation, and scaffolding for many WordPress facets—the count is justified. Still, it may overwhelm agents.
The tool surface is remarkably complete, covering generation, inspection, validation, and scaffolding for plugins, CRUD, REST, Gutenberg, WooCommerce, Multisite, i18n, security, and more. No obvious gaps in the framework's intended domain.
Related MCP Connectors
Security-first WordPress MCP server. 129 tools for Claude, ChatGPT, Gemini. Free on wp.org.
Manage WordPress blogs and WooCommerce shops from Claude, ChatGPT, Cursor and other MCP apps.
Contextual prompts and agent skills for 140+ AI platforms.
Enterprise memory, search, and context for frontier AI. 38 tools for business intelligence.
Related MCP Servers
- AlicenseCqualityDmaintenanceEnables AI agents to manage WordPress sites with 190+ tools for content management, theme/plugin customization, file system operations, WooCommerce, and complete site control through natural language.10028 npm55MIT
- FlicenseBqualityNot gradedmaintenanceTurns AI assistants into full-stack software engineers with 36 tools for cognitive reasoning, code validation, project scaffolding, and AI/IDE configuration generation across 130+ programming languages, databases, and frameworks.3513 npm-
- AlicenseNot gradedqualityDmaintenanceEnables WordPress content management through the Model Context Protocol, allowing AI agents to create, read, update, and delete posts, metadata, taxonomies, and terms, as well as interact with Gutenberg blocks.1GPL 2.0
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to manage WooCommerce stores, including products, orders, customers, categories, coupons, attributes, variations, order notes, refunds, reports, payment gateways, meta data, reviews, settings, data, posts, and system status through natural language.MIT