Github-Oauth MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| authorize_githubB | Generate GitHub authorization URL for user authorization. |
| get_access_token_from_codeC | Exchange authorization code for an access token. |
| get_user_repositoriesB | Fetch the repositories of the authenticated user. |
| get_user_profileB | Fetch the authenticated user's GitHub profile. |
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 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.