github-ruleset-mcp
Related Servers
Alternatives to github-ruleset-mcp
No user-submitted related servers found.
Related Servers
- FlicenseBqualityDmaintenanceAn MCP server that allows Claude and other MCP-compatible LLMs to interact with the GitHub API, supporting features like creating issues, getting repository information, listing issues, and searching repositories.4-
- FlicenseBqualityDmaintenanceAn MCP server that enables Claude and other compatible LLMs to interact with the GitHub API, supporting features like creating issues, retrieving repository information, listing issues, and searching repositories.4-
- AlicenseAqualityCmaintenancePython MCP server for GitHub operations, providing native tool integration with Claude Code and other MCP clients. It enables managing issues, pull requests, CI status, milestones, and batch operations via natural language.15MIT
- AlicenseNot gradedqualityCmaintenanceA self-hosted MCP server that gives Claude access to your GitHub account — read files, browse repos, commit changes, and manage issues and pull requests, all from a conversation.391 npmISC
- AlicenseNot gradedqualityCmaintenanceAn MCP server that lets ChatGPT or any MCP client securely delegate coding tasks to a local Claude Code instance, with git checkpointing, approval gates, and structured results. Supports code review, test running, and rollback via simple tool calls.18 npmMIT
- AlicenseAqualityCmaintenanceA local MCP server that lets Claude Desktop access GitHub via a personal access token, with tools for repos, issues, PRs, code search, and more.9391 npmISC
TDQS
Scored across 5 tools
Each tool targets a distinct operation: applying a ruleset, checking protection status, listing rulesets, deleting a ruleset, and listing templates. The purposes are clearly separated and descriptions reinforce the differences. No two tools appear to perform the same function.
All tool names follow a consistent verb_noun snake_case pattern (apply_ruleset, check_protection, list_rulesets, delete_ruleset, list_templates). The verbs clearly indicate the action, and there are no stylistic deviations or mixed conventions.
With exactly 5 tools, the server is well-scoped for managing GitHub rulesets and branch protection. Each tool serves a distinct purpose without redundancy, and the count is neither too small nor too large for the domain.
The tool set covers the full lifecycle: apply (create/update), check (read status), list (read all), delete (remove), and list_templates (discover available templates). There are no obvious missing operations for the stated purpose, and agents can accomplish all core ruleset management tasks.