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 |
Capabilities
Features and capabilities supported by this server
| 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 | |
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/ramseychad1/sdlc-assist-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server