Github-Oauth MCP Server
Related Servers
Alternatives to Github-Oauth MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to interact with GitHub through OAuth-authenticated operations including starting authorization flows, listing repositories, and creating issues using stored access tokens.1-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to access private GitHub repositories, organizations, issues, pull requests, and file contents via OAuth authentication.1 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables access to GitHub repositories and data through the GitHub API. Supports retrieving repositories, issues, pull requests, and searching code across GitHub with authentication via personal access tokens.-
- FlicenseNot gradedqualityCmaintenanceEnables claude.ai to connect to GitHub MCP using OAuth, providing full toolset for repository, issue, PR, Actions, and gist operations.-
- FlicenseNot gradedqualityDmaintenanceConnects Claude to GitHub via OAuth and proxies official GitHub MCP tools, allowing each end user to interact with GitHub as themselves.-
- AlicenseNot gradedqualityDmaintenanceEnables Claude to authenticate with GitHub OAuth and access tools for user information, calculations, and GitHub repositories.5MIT
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose in the OAuth flow and user data retrieval: authorize_github initiates the flow, get_access_token_from_code handles token exchange, get_user_profile fetches profile data, and get_user_repositories fetches repositories. There is no overlap or ambiguity between these operations.
All tools follow a consistent verb_noun pattern with snake_case (e.g., authorize_github, get_access_token_from_code). The naming is predictable and readable throughout the set.
With 4 tools, this server is well-scoped for its purpose of GitHub OAuth authentication and basic user data access. Each tool earns its place by covering essential steps in the OAuth flow and common user queries.
The tool set covers the core OAuth flow (authorization, token exchange) and basic user data (profile, repositories), with no dead ends. A minor gap exists in lacking tools for more advanced GitHub operations (e.g., repository management or issue handling), but this is reasonable given the server's focused scope.