F
licenseNot graded
qualityB
maintenanceEnables AI assistants to interact with GitHub issues, pull requests, and Actions workflows through MCP tools.
-
devops-mcp
by hjsvieira98
Related Servers
Alternatives to devops-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI clients such as Cursor to interact with GitHub repositories and perform issue listing, triage, health checks, prioritization, commenting, weekly digests, and release-note generation through purpose-built MCP tools.3 npmMIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to interact with GitHub repositories and issues through MCP tools, supporting listing repositories, listing and searching issues, and retrieving specific issues via the GitHub REST API.-
- AlicenseNot gradedqualityBmaintenanceEnables MCP-compatible AI clients to manage GitHub repositories and issues and trigger repository dispatch events via tools and a REST API.MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI assistants to interact with GitHub through the GitHub REST API, supporting repository, file, issue, pull request, branch, commit, search, and label operations with explicit confirmation for write operations.-
- AlicenseAqualityAmaintenanceEnables autonomous AI agents and developers to interact with the GitHub REST API for repositories, pull requests, issues, actions, releases, tags, and user/org data through MCP tools. It uses token-efficient response summaries and optional 3-tier read-only safeguards to keep interactions safe and context-window friendly.591 npm1MIT
TDQS
A3.9/5.0
Scored across 5 tools
Disambiguation4/5
Each tool maps to a distinct resource+action: listing open PRs with CI rollup, digesting one PR, listing issues, creating an issue, and a cross-resource activity feed. The only mild overlap is between list_open_pull_requests and get_repo_activity (which also surfaces updated PRs), but the descriptions make the boundary clear (CI-focused open list vs. time-windowed feed).
Naming Consistency5/5
All five names follow a strict snake_case verb_noun pattern: list_open_pull_requests, summarize_pull_request, list_issues, create_issue, get_repo_activity. Verbs (list/summarize/create/get) are used consistently with their implied semantics.
Tool Count4/5
Five focused tools sit comfortably in the reasonable range and each earns its place around the PR/issue workflow. It is slightly lean for a server branded "devops," which implies CI/CD and deployment operations beyond pull requests and issues.
Completeness3/5
Read paths are solid (PR list+digest, issue list, activity feed) but the write surface is a single create_issue. There is no create/merge/comment on pull requests and no update/close/comment on issues, so common follow-up actions become dead ends for an agent.
Maintenance
ActivityMaintained
ResponsivenessNo issues