MCP server for Splynx addon development - provides documentation, scaffolding tools, and guided workflows
This server provides 9 code generation tools for Splynx addon development. Most tools have clear, descriptive names starting with action verbs (generate_*, scaffold_*) and detailed parameter schemas using Zod. Descriptions are generally present and informative (ranging 80-300+ chars). However, there are gaps: output schemas are not formally documented (tools return text content without declaring field structure), error handling lacks recovery guidance, and some parameter descriptions could be more specific about constraints. The tools are well-composed for a scaffolding use case, each generates a distinct artifact, but lack idempotency and confirmation patterns for write-heavy operations.
Generate a config.json file defining the addon's settings UI in Splynx admin panel.
Generate a Yii2 controller PHP file for a Splynx addon with access control and actions.
Generate a HookController.php file that processes incoming hook events from Splynx via STDIN.
Generate an InstallController.php file with specified API permissions, entry points, hooks, additional fields, and payment accounts.
Generate a Yii2 database migration file for creating tables, adding columns, or custom migrations.
Generate a PHP model class for a Splynx addon (API model, ActiveRecord, or custom).
Output schemas not documented. Tools return text content via {type: 'text', text: result} but do not declare what structure the generated code follows or what fields/metadata are included. LLMs cannot reason about downstream usage.
No error handling or recovery guidance. Tools do not validate inputs (e.g., module_name format, feature compatibility), do not catch generation errors, and do not return actionable error messages. If generation fails, the LLM receives nothing but a raw error.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | D | 59 | <=2025-11-25 | v2 |
| 2026-03-09 | F | 47 | - | v1 |
Generate a Twig template view file for displaying data in various formats (table, form, detail, dashboard).
Generate a config/web.php configuration file with authentication, database, and Redis components.
Generate a complete Splynx addon project skeleton with all required files. Returns the full directory tree with file contents ready to be written to disk.
Destructive operations (write to disk, generate config) lack confirmation or dry-run patterns. Tools should support a dry-run mode or require explicit confirmation before generating files. Agents may invoke these tools by mistake.
Parameter constraints not fully specified. Several string parameters (e.g., module_name, addon_name) have format constraints mentioned in descriptions (max 32 chars, lowercase_underscore) but not enforced via Zod .max() or .regex(). LLMs may pass invalid values.
Missing enum constraints for field types. generate_model type parameter accepts 'api|activerecord|sqlite|dataset' but these are not declared as an enum in Zod, they are inferred from description text. Other tools (generate_view, generate_config_json) reference field types similarly.
Default values may cause unintended behavior. generate_install_controller defaults api_permissions, entry_points, hook_events, and additional_fields to empty arrays without documenting what this means. An LLM expecting defaults to be sensible (e.g., at least one entry point) may be surprised.
No guidance on parameter relationships. generate_install_controller has entry_points and hook_events as optional arrays, but does not document whether both are required together, or which combinations are valid (e.g., can you have hooks without entry points?).