Implementing Streamable HTTP MCP Server with Browser-based OAuth

Created By
asibyla year ago
MCP Streamable HTTP Server with Standard Browser OAuth
Overview

What is MCP OAuth Server?

MCP OAuth Server is a streamable HTTP server that facilitates client authorization through GitHub's OAuth, allowing secure access to resources.

How to use MCP OAuth Server?

To use the MCP OAuth Server, clone the repository, install the dependencies, create an OAuth app on GitHub, set the required environment variables, and start the server.

Key features of MCP OAuth Server?

  • Streamable HTTP server implementation
  • Browser-based client authorization using GitHub OAuth
  • Secure handling of authorized client requests

Use cases of MCP OAuth Server?

  1. Enabling secure access to APIs for authorized clients.
  2. Integrating with GitHub for user authentication in applications.
  3. Supporting multiple client requests through a single server instance.

FAQ from MCP OAuth Server?

  • What is required to run the MCP OAuth Server?

You need to have Node.js installed and set up GitHub OAuth credentials.

  • Can I use this server for other OAuth providers?

Currently, it is designed for GitHub OAuth, but it can be adapted for other providers with modifications.

  • Is there any support for error handling?

Yes, the server includes error handling for expired or invalid access tokens.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
asibyl
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