Enables OAuth authentication with GitHub, allowing users to authorize the application to access GitHub resources on their behalf
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Github-Oauth MCP Server authenticate me with GitHub to access my repositories"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
First, let’s install uv and set up our Python project and environment:
MacOS/Linux : curl -LsSf https://astral.sh/uv/install.sh | sh
Windows : powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"Make sure to restart your terminal afterwards to ensure that the uv command gets picked up.
Now, let’s create and set up our project:
Make sure you need to update claude_desktop_config.json to register tool
Related MCP server: GitHub Integration Hub
For Windows : code $env:AppData\Claude\claude_desktop_config.json
For Mac/Linux :code ~/Library/Application\ Support/Claude/claude_desktop_config.json{
"mcpServers": {
"Github-Oauth": {
"command": "C:\\Users\\Hp\\.local\\bin\\uv",
"args": [
"--directory",
"C:\\Users\\Hp\\Github-Oauth\\src\\github_oauth",
"run",
"server.py"
]
}
}
}Since MCP servers run over stdio, debugging can be challenging. For the best debugging experience, we strongly recommend using the MCP Inspector.
You can launch the MCP Inspector via npm with this command:
npx @modelcontextprotocol/inspector uv --directory C:\Users\Hp\Github-Oauth run github-oauthUpon launching, the Inspector will display a URL that you can access in your browser to begin debugging.
Generate GitHub authorization URL for user authorization.
Inputs: no named parameters.
Exchange authorization code for an access token.
Inputs: code (required).
Fetch the authenticated user's GitHub profile.
Inputs: no named parameters.
Fetch the repositories of the authenticated user.
Inputs: no named parameters.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Access the GitHub API, enabling file operations, repository management, search functionality, and…
Manage repositories, users, releases, and automate GitHub workflows
OAuth Multi-LLM Orchestrator
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
