Dev Project Coordinator
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CPC_KNOWLEDGE_BASE | No | Set to a custom KnowledgeBase directory (useful if the clone is public and your project JSON should stay private). |
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": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_projectsB | List all Xcode projects being tracked |
| get_project_statusC | Get the current status and details of a specific project |
| search_code_patternsC | Search for code patterns across all projects |
| add_projectC | Add a new Xcode project to track |
| update_project_statusC | Update the status or notes for a project |
| get_project_timelineB | Get status timeline and duration for a project |
| get_activity_heatmapC | Show project activity heat map for recent days |
| get_technology_trendsB | Analyze technology usage across all projects |
| get_project_healthB | Get health scores and recommendations for all projects |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
The tools mostly target distinct concerns: project CRUD, status, code search, timeline, activity heatmap, technology trends, and health. There is slight potential confusion among get_project_status, get_project_timeline, and get_project_health because they all report project state from different angles, but descriptions make the distinctions reasonably clear.
All tool names follow a consistent snake_case verb_noun pattern: list_projects, get_project_status, add_project, update_project_status, search_code_patterns, etc. No mixed casing or inconsistent verb styles are present.
Nine tools is well-scoped for a project coordination server. Each tool covers a meaningful operation without obvious redundancy or excessive granularity.
The surface covers creation, listing, status updates, code search, timeline, activity, trends, and health analytics. A delete/archive/remove-project operation appears to be the main lifecycle gap, but core workflows are otherwise well supported.