gsd-mcp-server
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| gsd_stateA | Get current GSD project state (phase, milestone, next steps) |
| gsd_progressA | Show what step to run next in the GSD lifecycle |
| gsd_new_projectA | Initialize a new GSD project (run once per project) |
| gsd_new_milestoneC | Start a new milestone |
| gsd_map_codebaseB | Analyze existing codebase with parallel explore agents |
| gsd_discuss_phaseB | Capture implementation decisions before planning a phase |
| gsd_list_phasesA | List all phases from the roadmap |
| gsd_plan_phaseC | Research and create task plans for a phase |
| gsd_execute_phaseB | Execute all plans for a phase in parallel waves |
| gsd_verify_workC | Verify phase work against goals via conversational UAT |
| gsd_quickC | Execute ad-hoc task with GSD guarantees |
| gsd_debugB | Systematic debugging with persistent state across context resets |
| gsd_spikeC | Rapidly spike an idea with throwaway experiments |
| gsd_sketchC | Rapidly sketch UI/design ideas with HTML mockups |
| gsd_complete_milestoneC | Archive completed milestone and prepare for next version |
| gsd_add_todoA | Capture idea or task as todo from current conversation |
| gsd_check_todosB | List pending todos |
| gsd_shipA | Create a PR from completed phase work |
| gsd_add_phaseA | Add new phase to end of current milestone |
| gsd_insert_phaseA | Insert urgent work as decimal phase between existing phases |
| gsd_settingsC | Configure workflow toggles and model profile |
| gsd_set_profileC | Switch model profile |
| gsd_runB | Run any GSD command directly (see gsd://help for full list) |
| gsd_validateC | Run GSD validation checks (consistency, health, agents) |
| gsd_roadmap_analyzeB | Full roadmap analysis with disk status for each phase |
| gsd_phase_completeB | Mark a phase as complete and update roadmap |
| gsd_config_getC | Read a GSD configuration value |
| gsd_config_setC | Write a GSD configuration value |
| gsd_commitB | Commit planning documents to git |
| gsd_scaffoldB | Create GSD document templates (context, uat, verification, phase-dir) |
| gsd_audit_uatA | Scan all phases for unresolved UAT/verification items |
| gsd_websearchB | Search the web via Brave API (requires GSD Brave config) |
| gsd_todo_completeB | Mark a todo as completed |
| gsd_workstreamsA | Manage parallel workspaces for concurrent milestones |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| state | Current GSD project state |
| project | Project definition and vision |
| roadmap | Phase roadmap with success criteria |
| requirements | Feature requirements traceable by ID |
| config | Project planning configuration |
| help | Full GSD command reference |
TDQS
Scored across 34 tools
Most tools target distinct workflow stages or resources, with clear names like gsd_add_phase, gsd_plan_phase, and gsd_verify_work. A few status-related tools (gsd_state, gsd_progress, gsd_roadmap_analyze) could be confused, but their descriptions clarify different focuses.
Tools consistently use the gsd_ prefix and snake_case, but verb/noun order varies (e.g., gsd_phase_complete vs. gsd_complete_milestone, gsd_todo_complete vs. gsd_check_todos). Some tools are bare nouns (gsd_state, gsd_settings) instead of verb_noun patterns, creating minor inconsistency.
With 34 tools, the server exceeds the 25+ threshold, feeling heavy even for a comprehensive GSD workflow. The count is justified by the broad scope, but it may overwhelm agents and increase the risk of misselection.
The tool set covers the full GSD lifecycle: project/milestone initialization, phase planning/execution/verification, todo management, config, git operations, shipping, debugging, and even web search. No obvious dead ends—gsd_run provides a fallback for any unexposed command.