Implementing Streamable HTTP MCP Server with Browser-based OAuth

@asibyl

Repository

Basic information

About Implementing Streamable HTTP MCP Server with Browser-based OAuth

MCP Streamable HTTP Server with Standard Browser OAuth

#mcp #oauth #http-server

Implementing Streamable HTTP MCP Server with Browser-based OAuth config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "streamable-http-oauth": {
      "command": "npx",
      "args": [
        "tsx",
        "server/index_streamable.ts"
      ],
      "env": {
        "GITHUB_CLIENT_ID": "",
        "GITHUB_CLIENT_SECRET": ""
      }
    }
  }
}

Implementing Streamable HTTP MCP Server with Browser-based OAuth tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

Fetch the live tool list by running this server in a temporary sandbox using the button above.

Overview

What is Implementing Streamable HTTP MCP Server with Browser-based OAuth?

An MCP server that uses Streamable HTTP transport and browser-based OAuth with GitHub. It handles client authorization requests through custom OAuth endpoints, verifying access tokens and managing session-based transport connections. Built for developers who need an MCP server that delegates authentication to GitHub’s OAuth flow.

How to use Implementing Streamable HTTP MCP Server with Browser-based OAuth?

Clone the repository, run npm install, set GITHUB_CLIENT_ID and GITHUB_CLIENT_SECRET environment variables, then start the server with npx tsx server/index.ts. Clients interact via POST to /mcp, /authorize, and /token endpoints.

Key features of Implementing Streamable HTTP MCP Server with Browser-based OAuth

Streamable HTTP server with /mcp endpoint
Browser-based GitHub OAuth authorization
Custom PKCE challenge and verifier generation
Access token verification and session management
OAuthServerProvider implementation for extensibility

Use cases of Implementing Streamable HTTP MCP Server with Browser-based OAuth

MCP clients that need delegated authorization via GitHub
Prototyping OAuth flows within the Model Context Protocol
Building secure MCP services with third-party authentication

Frequently asked questions

What is Streamable HTTP transport?

The server uses a single POST endpoint (`/mcp`) for all JSON-RPC messages instead of SSE or WebSocket, and manages sessions via a simple transport abstraction.

How does the OAuth flow work?

The client is redirected to GitHub’s authorization endpoint. After the user authorizes, GitHub returns an access token to the server, which stores it and issues a server‑owned access token to the client via `/token`.

What environment variables are required?

`GITHUB_CLIENT_ID` and `GITHUB_CLIENT_SECRET` must be set from a GitHub OAuth App created in your GitHub Developer Settings.

What are the runtime dependencies?

Node.js with npm. The server is started with `tsx` and depends on the packages installed via `npm install`.

Where are access tokens stored?

Access tokens are stored in memory on the server along with the client ID. No persistent storage is described.

Comments

More Developer Tools MCP servers

Termany

thinkany-ai

Agent-Native Terminal

174

Moxie Docs

Jackalope-Dev

Automated codebase documentation for GitHub: searchable docs, MCP context for AI agents, doc drift detection, and Friday Cleanup PRs.

LastPing

Know when your AI agents, cron jobs and CI pipelines fail, stall or go quiet. Your agent sets up monitors from a plain description, tells you what is broken and why, reads run history and traces, and writes notes on inci

Foremerge

naw103

Catch intent conflicts before code conflicts. The open-source coordination protocol for coding agents, built above Git.

LocalCan

Gives AI agents public URLs (tunnels) for localhost, live HTTP traffic inspection, snapshot publishing, and access control. Part of LocalCan, the ngrok alternative for Mac, Windows and Linux. Free plan.