gsd-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Features and capabilities supported by this server
| 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 |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/M0-AR/gsd-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server