MCP SSDLC Security Toolkit
Generates CI/CD pipeline configurations for Bitbucket repositories, enabling automated builds and deployments.
Generates Dockerfile and docker-compose configurations for containerized deployment of the designed system.
Generates CI/CD pipeline configurations for GitHub Actions, enabling automated testing and deployment workflows.
Generates CI/CD pipeline configurations for GitLab CI, enabling automated builds and deployments.
Generates Kubernetes deployment manifests (e.g., Deployments, Services) for orchestrating containerized applications.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@MCP SSDLC Security Toolkit orchestrate SSDLC pipeline for HIPAA-compliant app"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP SSDLC Security Toolkit v2.0
An intelligent, domain-aware Security Software Development Life Cycle (SSDLC) toolkit powered by the Model Context Protocol (MCP). It helps Tech Leads, Security Engineers, and Developers orchestrate secure software design, generate pseudocode, and manage compliance.
π Key Features
Domain-Agnostic Core: Built-in support for Healthcare (HIPAA), Fintech (PCI-DSS), Blockchain, Secure Communications, and 12+ more domains. Easily extensible to ANY domain via YAML plugins.
Tech Lead Automation: Generates Pseudocode (Python, TS, Java, Go, C#, C++, Rust), Architecture Diagrams (Mermaid), DFD/ERD, and Module Breakdowns from user stories.
Full Pipeline Orchestration: One command to run BA β Tech Design β Threat Modeling β QA Strategy β CI/CD Planning β ADR Generation.
Multi-format Export: Output to JSON, YAML, Markdown, or professional SRS documents.
Related MCP server: Phantom MCP
π Table of Contents
π Getting Started
Prerequisites
Node.js v18+
pnpm (recommended) or npm
Installation
# Clone the repository
git clone https://github.com/vuongdat67/mcp_ssdlc
cd mcp-ssdlc-security-toolkit
# Install dependencies
pnpm install
# Build the project
pnpm buildπ» Configuration
Claude Desktop App
Add to your Claude Desktop configuration:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"ssdlc-toolkit": {
"command": "node",
"args": ["path/to/mcp-ssdlc-security-toolkit/dist/index.js"]
}
}
}VS Code
The project includes .vscode/mcp.json for automatic configuration.
Docker
# Build and run with Docker
docker build -t mcp-ssdlc-toolkit .
docker run -it mcp-ssdlc-toolkit
# Or use docker-compose
docker-compose up ssdlcπ οΈ Available Tools
Tool | Description |
| List all available domain plugins |
| Load a specific domain |
| Auto-detect domain from description |
| Generate user stories and security requirements |
| Generate technical design and pseudocode |
| Generate STRIDE threat model |
| Generate test strategy |
| Generate CI/CD pipeline |
| Run complete SSDLC pipeline |
π Domains
Built-in Domains
Domain | Compliance | Use Case |
| HIPAA | Patient records, telemedicine |
| PCI-DSS | Payments, banking |
| - | Smart contracts, DeFi |
| GDPR | E2EE messaging |
| OWASP | Security tooling |
| - | ML model security |
| - | Malware research |
And 10+ more... |
Custom Domains
Create custom domains by adding YAML files to domains/custom/:
# domains/custom/ecommerce/domain.yaml
name: "ecommerce"
keywords: ["shop", "cart", "checkout"]
stakeholders:
- name: "Shopper"
type: "end_user"
sensitiveData:
- type: "Payment Data"
level: "critical"π³ Docker
# Development mode
docker-compose up ssdlc-dev
# Production mode
docker-compose up ssdlc
# Run tests
docker-compose run testπ Documentation
Full documentation available in the docs/ directory:
π€ Contributing
We welcome contributions! See CONTRIBUTING.md for guidelines.
# Run tests
pnpm test
# Run with coverage
pnpm test:coverage
# Lint
pnpm lintπΊοΈ Roadmap
See ROADMAP.md for planned features:
v2.1: AI Integration, Interactive CLI, Domain Marketplace
v2.5: Real-time Collaboration, Version Control, Third-party Integrations
v3.0: Visual Domain Designer, SBOM, Threat Intelligence Feeds
π οΈ Tech Stack
Feature | Supported Options |
Pseudocode Language | Python, TypeScript, Java, Go, C#, C++, Rust |
Cloud Target | Kubernetes, AWS, Azure, GCP, Docker |
Repo Platform | GitHub, GitLab, Bitbucket |
Export Formats | JSON, YAML, Markdown, SRS |
π€ Orchestration Example
Ask your AI assistant:
"Design a secure E-wallet system for fintech. Use TypeScript and deploy to AWS. Run the full SSDLC pipeline."
The agent will call orchestrate_ssdlc_pipeline and generate:
User stories and security requirements
Technical design with pseudocode
STRIDE threat model
Test strategy
CI/CD pipeline
Architecture Decision Records (ADRs)
Project plan with cost estimation
π License
This project is licensed under the MIT License - see the LICENSE file for details.
Made with β€οΈ by the MCP SSDLC team
Available Tools
17 toolsanalyze_code_securityC
Analyze code for security issues and vulnerabilities
Inputs: code (required), language (required), domain.
ba_analyze_requirementsC
Generate user stories, security requirements, and abuse cases
Inputs: business_goals (required), project_description (required), domain_name.
detect_domainC
Auto-detect domain from project description
Inputs: project_description (required).
devops_design_cicdC
Generate CI/CD pipeline with security gates
Inputs: tech_stack, project_name, deployment_target, repository_platform.
get_coding_guidelinesC
Get coding guidelines and security rules for a domain
Inputs: domain (required), language (required).
get_last_known_goodC
Get last known good configuration that worked
Inputs: workspace_root (required).
get_secure_templateC
Get a secure code template for a feature type
Inputs: language (required), feature_type (required), domain.
list_domainsB
List all available domain plugins
Inputs: no named parameters.
load_domainC
Load a specific domain plugin
Inputs: domain_name (required).
orchestrate_ssdlc_pipelineC
Run complete SSDLC pipeline from project description
Inputs: tech_stack (required), business_goals (required), project_description (required), target_language, +2 more.
parse_error_logC
Parse error log to extract issues and suggestions
Inputs: log_content (required), log_type.
qa_design_test_strategyC
Generate test cases from features and threats
Inputs: threats, features, compliance_requirements.
run_diagnostic_playbookC
Run a diagnostic playbook to check/fix environment issues
Inputs: playbook (required), workspace_root (required).
run_environment_diagnosticsC
Run diagnostics to check development environment (Node, Git, build tools)
Inputs: workspace_root (required).
security_threat_modelC
Generate STRIDE threat model from modules
Inputs: modules, domain_name, project_name.
techlead_designC
Generate feature checklist, flows, modules, pseudocode, architecture diagram
Inputs: project_name, user_stories, export_format, target_language, +1 more.
workspace_snapshotA
Generate a snapshot of the workspace structure (file tree with .gitignore filtering)
Inputs: root_path (required), max_depth.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogβ¦
TDQS
Scored across 17 tools
Most tools have clearly distinct purposes, but there is minor overlap between run_diagnostic_playbook and run_environment_diagnostics, and between get_coding_guidelines and get_secure_template. Descriptions are clear enough to differentiate.
The majority of tools follow a consistent verb_noun pattern (e.g., analyze_code_security, list_domains). However, two tools (security_threat_model, workspace_snapshot) deviate by omitting a verb, creating a minor inconsistency.
With 17 tools, the server is well-scoped for a security toolkit covering requirements, design, threat modeling, code analysis, CI/CD, testing, diagnostics, and domain management. Each tool earns its place.
The toolset covers major SSDLC phases (requirements, design, implementation guidance, analysis, testing, CI/CD). Minor gaps exist, such as lack of deployment security scanning or compliance checks, but core workflows are supported.
Related MCP Connectors
Threat modeling, code/cloud/pipeline scanning, shadow-AI discovery, compliance checks and fixes.
Threat modeling, code, API & cloud security, shadow-AI & compliance governance.
Governance copilot for AI-assisted coding. 72 packs, 532 rules, proof bundles.
DORA OS Conductor β 16-tool meta-orchestrator for DORA compliance workflow automation.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceIntegrates SAST, DAST, IAST, and SCA security testing tools for AI-powered DevSecOps automation, enabling comprehensive security scanning and reporting through natural language interfaces.17MIT
- FlicenseNot gradedqualityDmaintenanceEnables authorized compliance verification and security auditing through natural language, bridging AI assistants with industry-standard security tools for enterprise audits.24-
- AlicenseNot gradedqualityDmaintenanceEnables AI-powered security scanning of codebases through conversational analysis, allowing users to assess, threat model, code review, DAST test, and generate security reports using natural language with Claude.MIT
- AlicenseNot gradedqualityDmaintenanceIntegrates authoritative security compliance frameworks (ISO 27001, NIST 800-53, OWASP ASVS, NIST SSDF) into AI-assisted development, offering control lookups, cross-framework mappings, build-time guardrails, and automated audit evidence generation.244 npm3MIT