Model Context Protocol (MCP) Server + Github OAuth

Created By
fredrikp999a year ago
Example MCP server with OAuth based on
Overview

What is the Model Context Protocol (MCP) Server + Github OAuth?

This project is an example of a Model Context Protocol (MCP) server that integrates Github OAuth for authentication, allowing users to connect to the server using their GitHub accounts.

How to use the MCP Server?

To use the MCP server, clone the repository and install the dependencies using npm install. You can also create a remote MCP server using a command line template. After setting up a GitHub OAuth app, deploy the server to your Cloudflare account.

Key features of the MCP Server?

  • Supports remote MCP connections with Github OAuth authentication.
  • Acts as both an OAuth server for MCP clients and an OAuth client to GitHub.
  • Provides tools for authenticated users to access functionalities like adding and retrieving user information.

Use cases of the MCP Server?

  1. Building applications that require user authentication via GitHub.
  2. Integrating with other OAuth providers for enhanced security.
  3. Developing tools that utilize the MCP protocol for various functionalities.

FAQ from the MCP Server?

  • Can I use other OAuth providers with this MCP server?

Yes, the server can be adapted to integrate with other OAuth providers using the provided library.

  • Is there a limit to the number of users that can authenticate?

No, as long as they have valid GitHub accounts, they can authenticate and use the server.

  • How do I deploy the MCP server?

Follow the instructions in the README to deploy it to your Cloudflare account after setting up your GitHub OAuth app.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
fredrikp999
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago