Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
WPZYLOS_FRAMEWORK_ROOTYesThe root path of the WPZylos framework.

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

CapabilityDetails
tools
{
  "listChanged": true
}
prompts
{
  "listChanged": true
}
resources
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
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.

list_packagesA

List all WPZylos framework packages with their descriptions, layers, and class counts. Use to understand what the framework offers.

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.

recommend_packageA

Given a task description, recommend the best WPZylos framework package(s) to use. Prevents reinventing logic.

inspect_fileB

Analyze a PHP file and extract its classes, methods with full signatures, properties, constants, imports, and docblocks. Use before modifying any file.

search_frameworkA

Search across all framework packages for classes or methods by name. Returns matching classes with their package, FQCN, and method signatures.

list_stubsB

List all available code generation stub templates. Shows stub names and their replaceable tokens.

get_stub_contentA

Get the raw content of a specific stub template. Use to understand the template structure before generating code.

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.

generate_providerB

Generate a ServiceProvider class. Providers register services in the container and boot hook integrations.

generate_modelA

Generate an Eloquent-style Model class with fillable, casts, and table name.

generate_middlewareC

Generate a Middleware class implementing MiddlewareInterface for the HTTP pipeline.

generate_controllerB

Generate a REST/HTTP Controller class for handling requests.

generate_eventB

Generate an Event class for the event dispatcher system.

generate_listenerC

Generate a Listener class that handles dispatched events.

generate_commandB

Generate a CLI Command class for WP-CLI or Symfony Console.

generate_posttypeB

Generate a Custom Post Type registration class.

generate_taxonomyC

Generate a Custom Taxonomy registration class.

generate_shortcodeB

Generate a Shortcode class with render method.

generate_settingsC

Generate a Settings Page class with sections and fields.

generate_menuB

Generate an Admin Menu Page class.

generate_jobC

Generate a background Job class for queued processing.

generate_ruleB

Generate a custom Validation Rule class implementing RuleInterface.

generate_serviceC

Generate a Service class for business logic.

validate_plugin_structureB

Validate a WPZylos plugin folder structure against framework conventions. Checks for required files, directories, namespace consistency, and config setup.

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.

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.

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.

detect_incomplete_implementationsA

Find TODO, FIXME, HACK, XXX comments, empty method bodies, and placeholder returns across plugin code.

inspect_project_summaryB

Get a comprehensive summary of a WPZylos plugin project: providers, routes, models, services, controllers, and framework usage.

scaffold_crud_moduleB

Generate a complete CRUD module: Model, Migration, Controller, ServiceProvider, and route registration. Returns all files needed for a database-backed resource.

scaffold_cpt_moduleA

Generate a complete Custom Post Type module: CPT registration class, Taxonomy (optional), MetaBox (optional), Admin Columns (optional), and ServiceProvider.

scaffold_rest_moduleB

Generate a REST API module: Controller, Middleware, FormRequest, route file, and provider. Includes authentication and validation scaffolding.

scaffold_settings_pageB

Generate a complete admin settings page module: Settings class, Menu registration, ServiceProvider, and view template.

suggest_refactoringA

Analyze a PHP file and suggest refactoring opportunities: extract methods, reduce complexity, improve framework usage, split large classes.

explain_boot_sequenceA

Explain the WPZylos framework boot sequence and how a plugin initializes. Returns the 8-phase boot flow with code examples.

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.

build_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.

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.

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.

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.

generate_migrationC

Generate a database migration file with proper column definitions. Specify table name and fields with types, and get a complete migration class.

generate_testA

Generate a PHPUnit test file for an existing class. Creates test methods for each public method in the target class.

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.

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.

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).

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.

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.

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.

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.

woo_scaffold_shipping_methodB

Generate a WooCommerce Shipping Method class with calculate_shipping(), init_form_fields(), and ServiceProvider registration.

woo_scaffold_emailB

Generate a custom WooCommerce Email class with trigger(), get_content_html(), get_content_plain(), and ServiceProvider.

woo_scaffold_widgetB

Generate a WooCommerce/WordPress Widget class with form(), update(), and widget() methods.

woo_scaffold_product_tabB

Generate a custom WooCommerce product data tab (admin) with fields and save logic, or a frontend product page tab.

woo_validate_integrationB

Validate a plugin's WooCommerce integration: HPOS compatibility declaration, feature compatibility, proper hook usage, WC dependency check, template override safety.

woo_scaffold_rest_extensionB

Generate a WooCommerce REST API extension controller that adds custom endpoints under the WC REST API namespace.

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.

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.).

gutenberg_scaffold_block_patternA

Generate a WordPress block pattern registration. Block patterns are pre-designed block layouts users can insert.

gutenberg_scaffold_block_styleA

Register custom block style variations for existing core or custom blocks (e.g., rounded image, shadowed card).

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.

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.

i18n_validateB

Scan plugin for internationalization issues: untranslated user-facing strings, missing text domains, incorrect __() usage, mixed text domains, and translation function best practices.

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.

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.

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.

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.

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.

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).

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.

scaffold_ajax_handlerC

Generate a WordPress AJAX handler with nonce verification, capability check, PHP handler class, JS caller, and ServiceProvider registration.

scaffold_cron_jobB

Generate a WordPress Cron job: scheduled event, custom interval, handler class, activation/deactivation hooks for schedule management.

scaffold_admin_noticeA

Generate a WordPress admin notice: dismissible, persistent (user meta), conditional (screen/capability), with proper escaping and styling.

scaffold_custom_tableB

Generate a custom database table with dbDelta() migration, CRUD model class using $wpdb, activation hook, and uninstall cleanup.

scaffold_meta_boxA

Generate a WordPress meta box: registration, render callback, save handler with nonce/capability checks, and field definitions.

scaffold_update_checkerB

Generate a self-hosted plugin update checker: checks a remote JSON endpoint for new versions, integrates with WordPress plugin update API.

validate_rest_schemaA

Validate WordPress REST API endpoints in a plugin: check route registration, permission callbacks, sanitize/validate callbacks, response schema, and namespace consistency.

scaffold_wp_cli_commandB

Generate a WP-CLI command class with arguments, synopsis, progress bar support, and ServiceProvider registration.

scaffold_customizerB

Generate WordPress Customizer panel, section, and controls with sanitization, live preview JS, and ServiceProvider.

scaffold_transient_cacheA

Generate a Transient caching helper class with get, set, remember, forget, flush pattern, and group-based invalidation.

scaffold_shortcode_uiB

Generate an enhanced WordPress shortcode with admin UI (TinyMCE button), attribute panel, and frontend rendering class.

scaffold_test_suiteB

Generate a PHPUnit test suite for a WPZylos plugin: bootstrap file, base test case, sample unit test, phpunit.xml configuration.

scaffold_dashboard_widgetB

Generate a WordPress admin Dashboard Widget with configurable content, AJAX refresh, and optional configuration form.

Prompts

Interactive templates invoked by user choice

NameDescription
create_pluginGuided workflow for creating a new WordPress plugin using the WPZylos framework
audit_pluginAudit an existing WPZylos plugin for framework compliance, security, and code quality
add_featurePlan and implement a new feature in an existing WPZylos plugin
add_cptAdd a Custom Post Type with taxonomy, metabox, and admin columns
add_rest_apiAdd REST API endpoints to an existing WPZylos plugin
add_settings_pageAdd an admin settings page to a WPZylos plugin
debug_hookDebug why a WordPress hook is not working in a WPZylos plugin
convert_to_frameworkConvert a traditional WordPress plugin to use WPZylos framework
woo_create_extensionGuided workflow for building a WooCommerce extension using WPZylos framework
gutenberg_create_blockGuided workflow for creating a Gutenberg block using WPZylos framework
multisite_setupGuided workflow for adding WordPress Multisite support to a WPZylos plugin
add_cli_commandGuided workflow for adding a WP-CLI command to a WPZylos plugin
add_custom_tableGuided workflow for adding a custom database table to a WPZylos plugin
setup_testsGuided workflow for setting up PHPUnit tests in a WPZylos plugin

Resources

Contextual data attached and managed by the client

NameDescription
architecture-overviewWPZylos framework architecture overview — package layers, boot flow, isolation model
architecture-rulesWPZylos framework rules — security, naming, activation, hook prefixing, PHP-Scoper safety
packages-registryFull registry of all WPZylos framework packages with descriptions, layers, and dependency map
scaffold-structureExpected WPZylos plugin folder structure — entry file, bootstrap, config, app, resources, routes, tests
stubs-listAll available code generation stub templates with names and tokens
dependency-graphWPZylos package dependency graph — which packages depend on which
boot-sequenceWPZylos 8-phase boot sequence: Entry → Activation → Bootstrap → Foundation → Security/HTTP → Database → Routing/Queue → CLI
security-checklistWPZylos security checklist: nonces, capabilities, escaping, SQL safety, file validation
testing-guideWPZylos testing conventions: PHPUnit setup, test organization, mocking, assertions
docs-indexIndex of all WPZylos framework documentation files with categories
woocommerce-hooksWooCommerce hook reference: 48 essential actions and filters organized by category (cart, checkout, orders, products, payment, shipping, email, admin, rest-api, lifecycle)
woocommerce-guideWooCommerce development guide: extension types, HPOS compatibility, best practices for building WC integrations with WPZylos
gutenberg-guideGutenberg block development guide: static blocks, dynamic blocks, block patterns, styles, sidebar plugins, and build setup
i18n-guideWordPress internationalization guide: translation functions, text domains, .pot/.po/.mo files, JS translations
multisite-guideWordPress Multisite development guide: network activation, site options, network admin pages, super admin capabilities, switch_to_blog safety
wc-blocks-guideWooCommerce Blocks development guide: Checkout Block extensions, Cart Block extensions, IntegrationInterface, and build setup
framework-cookbookComplete API cookbook for ALL 25 WPZylos packages with real code examples: Container, Routing (web/REST/AJAX), Database, QueryBuilder, Model, Migrations, Security, Hooks, Events, Views, Validation, Config, I18n, Mail, Notification, Queue, Scheduler, Assets, Logger, and more

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/WPDiggerStudio/wpzylos-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server