PyGithub MCP Server

Related Servers

Alternatives to PyGithub MCP Server

No user-submitted related servers found.

Related Servers

GitHub MCP Server
Version Control Developer Tools
vinkius-labs
F
license
Not graded
quality
D
maintenance
Enables AI agents to interact with GitHub repositories, issues, pull requests, code, and more through a comprehensive set of tools.
Updated 3 months ago (2026-06-20 05:40 UTC)
-
git-mcp
Version Control Developer Tools
rkjavait
F
license
B
quality
C
maintenance
Enables AI clients to interact with GitHub repositories, issues, pull requests, and code search through the GitHub REST API.
Updated 2 months ago (2026-07-28 16:01 UTC)
12
-
GitHub MCP Server
Version Control Developer Tools
asbloom-py
A
license
Not graded
quality
D
maintenance
Enables interaction with GitHub through the GitHub API, supporting file operations, repository management, advanced search, and issue tracking with comprehensive error handling and automatic branch creation.
Updated 2 years ago (2025-01-07 01:03 UTC)
379 npm
1
ISC
MCP GitHub Automation Server
Version Control CI/CD & DevOps
venugopalareddy46
F
license
Not graded
quality
B
maintenance
Enables AI applications to retrieve GitHub repository information, manage issues, and monitor workflow statuses through the GitHub REST API.
Updated a month ago (2026-08-29 15:45 UTC)
-
GitHub MCP Server
Version Control CI/CD & DevOps Developer Tools
BBsBrezz
A
license
C
quality
D
maintenance
Enables comprehensive interaction with the GitHub API for managing repositories, issues, pull requests, commits, and GitHub Actions workflows through natural language.
Updated 10 months ago (2025-11-19 03:35 UTC)
20
64 npm
MIT
GitHub MCP Server
Version Control Developer Tools
pipseedai
A
license
A
quality
Not graded
maintenance
Enables AI agents to interact with GitHub repositories through the GitHub REST API for managing files, issues, and repository metadata. It supports both read operations like searching code and write operations such as creating repositories and updating issue comments.
Updated 8 months ago (2026-02-06 10:47 UTC)
9
-

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.5/5.0

Scored 2026-04-18 11:35 across 19 tools

Disambiguation4/5

Most tools have distinct purposes targeting specific GitHub resources and actions, like issues, files, repositories, and branches. However, there is some overlap between 'create_or_update_file' and 'push_files' as both handle file modifications, which could cause confusion. All other tools are clearly separated by their target resources.

Naming Consistency5/5

All tool names follow a consistent snake_case pattern with clear verb_noun structures, such as 'create_issue', 'list_commits', and 'update_issue_comment'. The naming is uniform across all 19 tools, making them predictable and easy to understand for an agent.

Tool Count4/5

With 19 tools, the count is slightly high but reasonable for a comprehensive GitHub API server covering issues, repositories, files, and branches. It provides extensive functionality without being overwhelming, though it borders on being heavy compared to typical well-scoped servers.

Completeness5/5

The tool set offers complete CRUD and lifecycle coverage for key GitHub domains, including issues (create, get, update, delete, comment, label), repositories (create, get, fork, search), files (create/update, get, push), and branches (create). There are no obvious gaps, enabling agents to handle common workflows effectively.