CastPlan MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bmad_parse_specificationC | Parse a business specification document and generate tasks |
| bmad_update_task_statusC | Update the status of a specific task |
| docs_referenceC | Find and reference relevant documentation for development work |
| docs_updateB | Update documentation after completing development work |
| docs_searchC | Search through project documentation |
| docs_validateC | Validate documentation structure and completeness |
| hooks_triggerC | Trigger a hook event manually |
| hooks_setup_gitB | Setup Git hooks for automated documentation and validation |
| hooks_start_watchingC | Start file system watching for automatic event triggering |
| hooks_stop_watchingB | Stop file system watching |
| initialize_documentation_systemC | Initialize the enhanced documentation automation system for a project |
| track_document_workC | Track the relationship between development work and documentation requirements |
| analyze_document_qualityC | Perform comprehensive quality analysis on documentation with AI insights |
| get_document_treeB | Retrieve the hierarchical document tree structure |
| update_document_lifecycleC | Update the lifecycle state of a document with optional review scheduling |
| generate_documentation_reportC | Generate comprehensive reports on documentation status and quality |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| System Status | Comprehensive status of all CastPlan automation services |
| BMAD Tasks | Current tasks from Business Model & Architecture Documentation |
| BMAD Agents | Available agents for task assignment |
| Task Assignments | Current task assignments to agents |
| Documentation Change History | History of documentation changes |
| Hook Events History | History of hook events processed |
| Hooks Configuration | Current hooks service configuration |
| Enhanced Documentation Status | Current status of all tracked documents with lifecycle states |
| Work-Document Connections | All tracked work-document connections with AI insights |
| System Health Status | Comprehensive health monitoring data including service status and metrics |
| Error Recovery Status | Circuit breaker states, retry statistics, and error patterns |
| Graceful Degradation Status | Current degradation level, disabled features, and service availability |
TDQS
Scored across 16 tools
Most tools have distinct purposes with clear boundaries, such as docs_search for searching and docs_update for updating. However, some overlap exists between analyze_document_quality and generate_documentation_report, as both involve quality assessment, which could cause minor confusion.
The naming follows a consistent snake_case pattern throughout, with clear verb_noun structures like docs_search and hooks_setup_git. A minor deviation is bmad_parse_specification, which uses a prefix (bmad) that breaks the pure verb_noun flow, but overall it remains readable and predictable.
With 16 tools, the count is slightly high but reasonable for a documentation automation system, covering areas like document management, hooks, and analysis. It might feel a bit heavy, but each tool appears to serve a specific function without obvious redundancy.
The tool set provides comprehensive coverage for documentation automation, including CRUD-like operations (search, update, validate), lifecycle management (update_document_lifecycle), analysis (analyze_document_quality), and automation hooks (setup, trigger). No significant gaps are apparent for this domain.