DevOps MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_REPO | Yes | The GitHub repository name containing the DevOps skills. | |
| GITHUB_OWNER | Yes | The GitHub owner or organization name. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_skillsA | Lists all available DevOps skills (SAP Fiori documentation templates, code standards, best practices). Use this tool BEFORE generating documentation or reading project content. |
| fetch_skillA | Fetches a DevOps skill from GitHub (documentation templates, code standards, best practices). Use when the user requests to generate documentation, apply standards, or use a template. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.