pinoox-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PINX_ROOT | No | Alias for PINOOX_ROOT. Same as PINOOX_ROOT. | |
| PINOOX_ROOT | No | Platform or pinx project root directory (absolute path). Required for project introspection tools. |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_docsA | Search official Pinoox documentation by keyword. Returns matching doc paths and GitHub URLs. |
| fetch_docB | Fetch full markdown from github.com/pinoox/docs. |
| list_doc_topicsB | List curated Pinoox documentation topics and paths. |
| project_infoB | Application info: project kind (platform vs single-app pinx), PHP version, pincore/pinx-cli versions, composer packages, apps. |
| list_cli_commandsA | List available php pinoox or pinx commands. Platform uses pinoox list; single-app uses pinx list. |
| list_routesB | List named route actions. Platform: route:actions. Single-app: pinx routes. Supports --json and --validate. |
| list_appsA | List installed apps. Platform: directories under apps/. Single-app: package from root app.php. |
| read_app_manifestB | Read app.php. Platform: apps/{package}/app.php. Single-app: root app.php. |
| read_project_fileC | Read a project file. Platform: apps/, config/. Single-app: Controller/, Model/, routes/, theme/, migrations/, etc. |
| list_config_keysB | Inspect config/*.config.php files and list top-level keys. |
| list_env_keysA | List .env and .env.example variable names (values redacted). |
| list_modelsB | Scan Model/ directories and list model class files. |
| migration_statusB | Show migration status. Platform: migrate:status. Single-app: migrate:st. |
| db_schemaA | Infer table structure from migration PHP files without a live DB connection. |
| read_log_entriesA | Read the last N lines from the Pinoox log file via log:view. |
| project_doctorA | Run pinx doctor --json health check. Single-app pinx projects only. |
| deps_statusB | Composer/npm dependency status. Single-app: pinx deps:st. |
| pinker_statusC | Pinker build cache status. Single-app: pinker:st. Platform: pinker:status. |
| frontend_infoB | Theme/Vite/npm info via pinx fe:info (single-app only). |
| run_cliA | Run a safe read-only php pinoox or pinx command. Destructive commands are blocked. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| create-pinoox-app | Guided workflow for scaffolding a new Pinoox HMVC app |
| pinx-workflow | Day-to-day pinx-cli workflow for single-app projects |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| docs-index | Curated table of contents for official Pinoox docs |
| conventions | Official conventions for AI-assisted Pinoox development |
| Project structure | Read a documentation page by language and path |
| Pinx CLI | Read a documentation page by language and path |
| Router | Read a documentation page by language and path |
TDQS
Scored across 20 tools
Each tool targets a distinct aspect of the Pinoox ecosystem (e.g., db_schema for migrations, list_models for models, read_log_entries for logs). There is no ambiguity; even similar tools like project_info and read_app_manifest have clear scope differences.
All tool names follow a consistent snake_case verb_noun pattern (e.g., list_apps, read_log_entries, search_docs). The naming is predictable and easy to understand.
With 20 tools covering configuration, dependencies, routing, models, migrations, logs, documentation, and CLI commands, the count is well-scoped for a framework-specific server. It covers essential inspection tasks without being bloated.
The tool surface is thorough for read-only inspection of a Pinoox project, covering most common development needs. Minor gaps exist (no tool for writing or modifying project files), but these seem intentional given the server's focus on read-only operations.