sdlc-assist-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SUPABASE_URL | Yes | Supabase project URL | |
| VERTEXAI_LOCATION | No | GCP region for Vertex AI Gemini (defaults to us-central1) | |
| VERTEXAI_PROJECT_ID | No | GCP project name for Vertex AI Gemini (defaults to sdlc-assist) | |
| SUPABASE_SERVICE_ROLE_KEY | Yes | Supabase service role key |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sdlc_list_projectsA | List all SDLC Assist projects with their status and artifact completion. Returns a summary of every project including which artifacts have been generated (PRD, Architecture, Data Model, etc.) and how many UI screens exist. Use this to discover project IDs for other tools. Args: params (ListProjectsInput): Optional filters: - status_filter (Optional[str]): Filter by status ('DRAFT', 'ACTIVE', 'COMPLETED', 'ARCHIVED') Returns: str: Markdown-formatted list of projects with completion info. |
| sdlc_get_project_summaryA | Get a detailed summary of a single SDLC project. Returns the project name, status, tech stack preferences, which artifacts have been generated (and when), and the number of UI screens. Does NOT return artifact content — use sdlc_get_artifact for that. Args: params (GetProjectSummaryInput): Contains: - project_id (str): UUID of the project Returns: str: Markdown-formatted project summary with artifact status. |
| sdlc_get_artifactA | Fetch the full content of a specific artifact from a project. Retrieves artifacts like the PRD, Architecture Overview, Data Model, API Contract, Sequence Diagrams, Implementation Plan, CLAUDE.md, or Corporate Guidelines. Args: params (GetArtifactInput): Contains: - project_id (str): UUID of the project - artifact_type (ArtifactType): Which artifact to fetch. One of: 'prd', 'design_system', 'architecture', 'data_model', 'api_contract', 'sequence_diagrams', 'implementation_plan', 'claude_md', 'corporate_guidelines' Returns: str: The full artifact content (Markdown or JSON depending on type), or an error message if the artifact hasn't been generated yet. |
| sdlc_get_screensA | List all UI screens defined for a project with their metadata. Returns screen names, types, complexity, epic assignments, and design notes. Optionally includes the full HTML prototype content. Args: params (GetScreensInput): Contains: - project_id (str): UUID of the project - include_prototypes (bool): If true, include HTML content (default false — prototypes can be very large) Returns: str: Markdown-formatted screen inventory grouped by epic. |
| sdlc_get_tech_preferencesA | Fetch the technology stack preferences for a project. Returns the user's selected frontend, backend, database, deployment target, authentication method, and API style choices. Args: params (GetTechPreferencesInput): Contains: - project_id (str): UUID of the project Returns: str: Markdown-formatted tech stack summary, or a message indicating preferences haven't been set yet. |
| sdlc_generate_estimationA | Generate Traditional vs AI-Assisted cost estimates for a project. Produces two side-by-side estimates showing hours and costs for each SDLC phase (Requirements, Design, Develop, Test, Deploy, Data Cleansing, Transition to Run, Project Management), then highlights the savings from using SDLC-Assist + agentic development. Requires all upstream artifacts to be generated first (PRD, architecture, data model, API contract, screens, implementation plan). Args: project_id: The project UUID. Returns: str: JSON with traditionalEstimate, aiAssistedEstimate, savings, and assumptions. |
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 6 tools
Each tool targets a distinct resource/action: listing projects, getting a project summary, fetching a specific artifact, listing screens, getting tech preferences, and generating estimation. There is no overlap or ambiguity in their purposes.
All tools follow the consistent pattern sdlc_<verb>_<noun> with lower_snake_case: sdlc_list_projects, sdlc_get_project_summary, sdlc_get_artifact, sdlc_get_screens, sdlc_get_tech_preferences, sdlc_generate_estimation. This is uniform and predictable.
Six tools is an appropriate, well-scoped set for a read-and-estimate SDLC assist server. Each tool earns its place, and the count is within the ideal 3-15 range, making the server easy to navigate.
The tool surface covers the core read workflows: listing projects, retrieving any artifact, screen inventory, tech preferences, and generating estimates. Minor gaps exist, such as no tool to create or update projects/artifacts, but the stated purpose appears to be querying and estimation, so this is a reasonable limitation.