Advertise
MCP.so
Sign In

Implementing Streamable HTTP MCP Server with Browser-based OAuth

@asibyl

Repository

Basic information

Category

Developer Tools

Transports

stdio

Author

asibyl

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

1

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.

2

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`.

3

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.

4

What are the runtime dependencies?

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

5

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

FARPY

mangomunchr

Verified distributed compute for humans, applications, and agents. Submit Blender, Octane, and video workloads, route them across qualified GPUs, track asynchronous execution, download finished artifacts, and verify FARP

1

Mcp-Warden

ermoluk

Local-first credential broker for MCP. AI coding agents (Claude Code, Cursor, Codex…) call APIs, SSH and databases through scoped presets; secrets stay in your OS keychain and never enter the agent's context.

4

JiCo for Jira & Confluence – PII-redacting MCP server with Human-in-the-Loop

drkv-com

JiCo for Jira & Confluence: local MCP server for Jira Data Center - redacts personal data before the AI model, holds every write for approval

MilliGate (x402 Crypto Paywall)

MilliGate Core

MilliGate is a developer-first remote MCP server that functions as a secure crypto paywall. By leveraging the HTTP 402 (Payment Required) protocol, it allows developers to monetize AI agents, APIs, and digital infrastruc

Yocoolab

Yocoolab

MCP server for AI Agents — exposes Yocoolab feedback threads and design selections as tools

1
Advertise