DevSecOps MCP Server
by jmstar85
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ZAP_URL | No | URL of the OWASP ZAP server (required if using OWASP ZAP) | |
| MCP_PORT | No | Port for the MCP server | 3000 |
| NODE_ENV | No | Node environment (production/development) | production |
| LOG_LEVEL | No | Logging level (error/warn/info/debug) | info |
| TRIVY_PATH | No | Path to the Trivy executable | |
| ZAP_API_KEY | No | API key for OWASP ZAP | |
| SONARQUBE_URL | No | URL of the SonarQube server (required if using SonarQube) | |
| SONARQUBE_TOKEN | No | Authentication token for SonarQube | |
| TRIVY_CACHE_DIR | No | Cache directory for Trivy scans | |
| OSV_SCANNER_PATH | No | Path to the OSV scanner executable | |
| SECURITY_STRICT_MODE | No | Enable strict security mode | true |
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
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
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/jmstar85/DevSecOps-MCP'
If you have feedback or need assistance with the MCP directory API, please join our Discord server