AI DevSecOps Agent MCP Server
Fetches CI/CD pipeline runs from GitHub Actions to monitor build status and pipeline health.
Queries a vulnerability board in Jira and returns severity-ranked CVEs for vulnerability triage.
Click on "Install 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., "@AI DevSecOps Agent MCP ServerWhat's the status of the main CI pipeline and any critical vulnerabilities?"
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.
AI-Assisted DevSecOps Agent β MCP Server π€π
An MCP (Model Context Protocol) server exposing DevSecOps tooling to LLM clients β turning your AI copilot into a security-aware engineering partner.
The Problem
DevSecOps teams drown in context-switching: checking pipeline status in one tab, triaging vulnerabilities in another, searching logs in a third. Meanwhile, LLM coding assistants can write code but are blind to your operational reality β they can't see your failing builds, open CVEs, or production errors.
Related MCP server: Enterprise MCP Gateway and Tool Registry
The Solution
This MCP server bridges the gap by exposing four security-critical tools to any MCP-compatible LLM client (GitHub Copilot, Claude Desktop, Cursor, etc.):
Tool | What It Does |
| Fetches CI/CD pipeline runs from GitHub Actions |
| Queries a vulnerability board and returns severity-ranked CVEs |
| Searches application logs by service, severity, and time range |
| Analyzes a |
Why This Over the Obvious Alternative
Most "AI + DevOps" demos are chatbots with hardcoded responses. This project implements the Model Context Protocol (MCP) β the open standard for tool-use that GitHub Copilot, Claude, and other major LLM clients natively support. The tools return real, structured data that the LLM reasons over, not canned answers.
Architecture
βββββββββββββββββββ MCP (stdio/SSE) ββββββββββββββββββββββββ
β LLM Client βββββββββββββββββββββββββΊβ MCP Server β
β (Copilot, β β β
β Claude, etc.) β β ββββββββββββββββββ β
β β β β Pipeline Tool β β
β β β β Vuln Triage Toolβ β
β β β β Log Search Tool β β
β β β β Dep Scan Tool β β
β β β ββββββββββββββββββ β
βββββββββββββββββββ ββββββββββββββββββββββββ
β
βββββββββ΄ββββββββ
β Mock Data β
β (Simulated β
β APIs) β
βββββββββββββββββπ οΈ Tech Stack
Runtime: Node.js + TypeScript
Protocol: Model Context Protocol (MCP) SDK
Transport: stdio (local) and SSE (remote)
Containerization: Docker
π Getting Started
Local Development
npm install
npm run build
npm run startWith Docker
docker-compose up -d --buildConnecting to Claude Desktop
Add to your Claude Desktop MCP config (claude_desktop_config.json):
{
"mcpServers": {
"devsecops-agent": {
"command": "node",
"args": ["dist/index.js"]
}
}
}π Project Structure
src/
βββ index.ts # MCP Server entry point
βββ tools/
β βββ pipeline.tool.ts # GitHub Actions pipeline status
β βββ vulnerability.tool.ts # CVE triage from mock board
β βββ logs.tool.ts # Log search across services
β βββ dependency.tool.ts # Dependency vulnerability scanning
βββ data/
βββ mock-data.ts # Simulated API responsesDecision Log
Decision | Rationale |
MCP over REST API | MCP is the emerging standard for LLM tool-use; REST would require custom integration per client |
TypeScript over Python | Aligns with existing TypeScript expertise; MCP TS SDK is mature |
Mock data layer | Keeps the PoC self-contained without requiring real GitHub/Jira API keys |
stdio transport | Default for local MCP; SSE available for remote deployment |
π¨βπ» Author
Built to demonstrate AI-augmented DevSecOps workflows and close the gap between LLM assistants and operational tooling.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
FlicenseAqualityFmaintenanceEnables AI agents to orchestrate security research workflows by connecting to containerized security tools via MCP, allowing automated vulnerability analysis and pipeline execution.24803- Alicense-qualityCmaintenanceEnables AI agents to discover and execute tools via a secure MCP server with JWT authentication, RBAC, rate limiting, and audit logging.1MIT
- Flicense-qualityBmaintenanceEnables secure interaction between LLMs and MCP tools by applying zero-trust security controls, including sensitive data masking, file system protection, and policy enforcement.
- Flicense-qualityCmaintenanceEnables LLM-powered agents to securely communicate with and orchestrate downstream microservices via FastAPI endpoints exposed as MCP tools.
Related MCP Connectors
MCP Hub: AI service discovery, per-user OAuth, and multi-service workflow orchestration
Zero-config MCP security scanner for AI-generated apps. 25K+ vulnerability patterns.
Remote MCP for Copilot CLI switch gate MCP, structured receipts, audit logs, and reviewer-ready evid
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/SumitDalavi/ai-devsecops-agent-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server