DevOps MCP
# DevOps MCP
MCP (Model Context Protocol) server to fetch DevOps skills from GitHub (SAP Fiori documentation templates, code standards, best practices).
## Installation
### Quick installation
1. Install the package:
```bash
npm install -g @devops-vinci/mcp
```
2. Click this link to auto-configure VS Code (fully pre-configured):
**[š¦ Install DevOps MCP - Vinci Energies](vscode:mcp/install?%7B%22name%22%3A%22devops%22%2C%22command%22%3A%22npx%22%2C%22args%22%3A%5B%22%40devops-vinci%2Fmcp%22%5D%2C%22env%22%3A%7B%22GITHUB_OWNER%22%3A%22devops-vesi%22%2C%22GITHUB_REPO%22%3A%22devops-skills%22%7D%7D)**
ā
**That's it!** No further configuration needed.
---
### Manual configuration (alternative)
```bash
npm install -g @devops-vinci/mcp
```
Then add this configuration to `.cursor/mcp.json`:
```json
{
"mcpServers": {
"devops": {
"command": "npx",
"args": ["@devops-vinci/mcp"],
"env": {
"GITHUB_OWNER": "devops-vesi",
"GITHUB_REPO": "devops-skills"
}
}
}
}
```
## Available tools
### `list_skills`
Lists all available DevOps skills in your GitHub repository.
### `fetch_skill`
Fetches the content of a specific skill from GitHub.
## Usage examples
Just ask Copilot:
- "List available skills"
- "Fetch the documentation-templates skill"
- "Generate documentation for this Fiori project"
## License
MIT
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: 'fetch_skill' retrieves a specific skill for generating documentation or applying standards, while 'list_skills' enumerates all available skills to inform selection. There is no overlap or ambiguity between them.
Both tools follow a consistent verb_noun pattern ('fetch_skill', 'list_skills'), using snake_case throughout. The naming is predictable and aligns with common conventions for tool design.
With only 2 tools, the server feels thin for a 'DevOps MCP' scope, which typically involves broader operations like deployment, monitoring, or automation. This limited set may not adequately cover the expected domain.
The toolset is severely incomplete for DevOps, lacking essential operations such as managing deployments, configuring infrastructure, or handling CI/CD pipelines. It focuses narrowly on skills/templates, leaving significant gaps in core DevOps workflows.